Page Comparison

he following items have been completed in this release:

Import EDV file ENHANCEMENT

The Employee Deduction Voucher (EDV) Plan Field Logic for Imports has been enhanced.

This import logic is now Similar to the "DeductionVoucher" import

• A new import class was created "ClientSpace.PEO.Import.EmployeeDeductionVoucher"
• A new import map created "EmployeeDeductionVoucher*.csv"
• The "Plan" column mapped to EDV.fkOfferedPlanID.  Import file column MUST contain the "UniquePlanCode" value, this will convert to the fkOfferedPlanID
• The "BenefitPlanEffDate" column (no dataform mapping) is used with UniquePlanCode and EmployeeID to locate the correct Offered Benefit Plan (OBP) in the EE's workspace
  • If a single OBP is located, that plan will be set on the EDV
  • If multiple OBP's are located, no plan will be set on the EDV (error message will appear in import log file)
  • If no OBP is located, no plan will be set on the EDV (error message will appear in import log file)

Offered Benefit Plan (OBP) selection:

•  Unique Plan Code (UPC) and Effective Date are used to locate Benefit Plan
•  EEID are used to locate the Workspace and the EE Benefit Classification ID (Employment.fkBenefitClassificationID)
•  Workspace, Benefit Plan and Benefit Classification ID are used to locate OBP

*Bug* Odd Behavior with Client Services Cases Widget

Resolved an issue with the My Cases - Client Service Cases Widget on the Home Page which caused the Case records that should have appeared in the Widget to be removed on load. Widget now properly displays current cases assigned to the logged in user.

PHRConversion - PEO Business Rules to Convert ImportIDs ENHANCEMENT

The system has been enhanced to allow client workspace conversions at the press of a button.  We have added several new business rules:

Client Master -

New Hard Error "HE_ValidateConvertPayrollSystem" - Warns you and stops the conversion process if Client Number, Import ID or New Client ID is missing.

New Biz logic rule "ConvertPayrollSystem"   - Takes in two parameters (ReadyToConvertStatus  & NewPayrollSystem) and sets the following fields and values

•  LegacyClientID - set to the workspace current ClientNumber
•  ClientNumber - set to the NewClientID value
•  ImportID - set to the NewClientID value

The system then kicks off the ImportID setting process to update all standard PEO forms whose ImportID contains the Client Number so that they use the new converted Client Number

New Link "Ready to Convert"  - Clicking this runs Client Master conversion process as well as converts Location ID information on the Client Location form and Employee ID's on the Employee form and associated forms.

Added a link condition for the Client Master - "luReadyToConvertIndicator" = ReadyToConvert (used to configure link visibility)

Also added was a security entity "gen_ClientMaster_ReadyToConvert"  which is used to secure the Ready to convert link.

PHRConversion - Benefit Classification Hard Error ENHANCEMENT

A new Hard Error has been added to the Benefits Classification form - HE_ClassificationCodeUnique.  This guarantees that the Classifcation code must be unique within the associated workspace and includes inactive records in that workspace.

PHRConversion - Employee Benefit Import Logic ENHANCEMENT

New import class ClientSpace.PEO.Import.PrismEmployeeBenefits, uses Unique Plan Code (UPC) and Effective Date to locate an Offered Plan in the EE's workspace
Must create new Import Maps using this import class:

• eebenefits_{plantype}*.csv where {plantype} is 'health', 'dental', etc.
• map must contain 'EffectiveDate' and {plantype} Plan fields (e.g. HealthPlan, DentalPlan, etc.). Column naming is not optional

PHRConversion - Carrier Invoice (MBR) Import Logic ENHANCEMENT

The plan and employee data is set on the MBR after the Import generates an MBR record and saves it.  A new rule has been created to validate against the new UniquePlanCode field rather than ClientPlanCode field.

The existing Import.CarrierMBR Import Class that is used to import MBRs has been modified including the following:

• Point to the new Benefit Classification field on the Employment to determine the Benefit Classification. Determined via the SSN in the file.
• Point the "Plan" column to the new Unique Plan Code field on the Benefit Plan
• Point the "EffectiveDate" column to the Effective Date field on the Benefit Plan

These three values together determine the Offered Plan which will be set in the Plan field ('fkPlanID') on the Master Benefit Record table.

A new hard error HE_DuplicateUniquePlanCode  has been added to verify that a SINGLE Offered Plan can be located for Employee, UPC, Effective Date and EEI Classification.  If no offered plans or more than one are found an error will be logged

PHRConversion - Rule to ensure Benefit Plan Are Unique ENHANCEMENT

A new Hard Error has been created for the Benefits Plan dataform -  "HE_BenefitPlanUnique"

This rule runs on change of Effective Date or Unique Plan Code fields requiring the combination of  Effective Date and Unique Plan Code to be distinct. 

Salesforce Integration, populate Org from Lead ENHANCEMENT

Lead processing in the Salesforce API has been enhanced to allow (via Import Map configuration) additional Org data such as Address, Assigned To, Phone, Website, EIN, Do Not Call and so on to be populated, instead of creating a simple shell Org as had previously been the case.

PEO Activity Widget Error 

Corrected an issue where the Activity widget, under certain circumstances could fail, throwing a SQL exception.

Case Field Cloning Defaults ENHANCEMENT

The following PEO Case fields have  been set as Workflow Cloneable by default:

• Category
• Type
• Subject
• Description
• Reported By
• Priority

Admin Workspace displaying Broker Widget Layout

Resolved an issue where the Workspace Landing Page for the Broker Portal workspace would inadvertently be shown on the Admin Workspace as well. The Broker Portal Workspace is now the only Workspace where this Landing page widget layout will appear.

New WC Rates Not Getting Set on Batch Cloning

Resolved an issue on cloning pricing which used an MCP policy where selecting the option during the Batch Clone process to use the new policy rates, would still produce pricing using the old policy rates amount for the pricing code manual rate. Pricing now uses the appropriate new rates for MCP Batch cloning.

SUBJECT ENHANCEMENT

CONTENT