Release 124 Notes

Updated Renew Benefit Plan Business Rule

The following updates were made to the Renew Benefit Plan business rule:

• Added the ability to clone (i.e., copy) the new Underwriting Group field value (used for Gradient AI) to the new benefit plan.

• Prior Renew Benefit Plan business rule logic is still applicable:

  • Values set to clone are copied when the Renew link is clicked in the Action Center Workflow section of the displayed Benefits Plan record.

  • The Renew link is only active when Benefit Plan status is Active and the Renewed From field is empty (indicating that the plan has never been renewed previously).

  • When the Renew link is clicked, a new plan is added in New status with all cloned values included in the new plan record.

• Updated the Description section on the Renew Benefit Plan Rule Details page to reflect the addition of Underwriting Group to the copied fields and reformatted the list items in this section for improved readability.

Removed the Employee Termination Tab from the Client Service Case and Inactivated COVID-19 Workflow Channel

The Employee Termination tab was added to the Client Service Case dataform to assist with offboarding workflow related to COVID-19 mass layoffs. Now that the Employee Termination tab is no longer widely used, it has been removed from the Client Service Case dataform. The form is still available as a Custom Link which is currently Inactive. Additionally, the COVID-19 workflow channel has been deactivated.

Note: In the referenced article below, "Offboarding Workflow", references to the Employee Termination tab attached to the Client Service Case dataform have been removed. However, there are still references to COVID-19 email templates. These templates will be deactivated in a future release of ClientSpace.

See Offboarding Workflow.

Modified Single User Client Service Case Type Assignment to Require Backup User Assignment

Client Service Case Type configuration has been enhanced to require a backup assignment specification. Previously, when Single User was selected as the Default Assignment on a Client Service Case Type record, there was no backup assignment function for when a Default Assignment became invalid (i.e., Blank, Inactive or Expired). Now, when Single User is selected as the Default Assignment on a Client Service Case Type record, two new required fields are available:  Backup Assignment and Backup Assigned To. You must select Single User or Client Role as a Backup Assignment type and then select the "assigned to" individual or role in the Backup Assigned To field.

• If the Backup Assignment is a Single User, the Backup Assigned To field selector allows you to select a Single User as shown in the example screen below:

• If the Backup Assignment is a Client Role, the Backup Assigned To field selector allows you to select a Client Role as shown in the example screen below:

Note: Case Type Assignments with a Single User Default Assignment that were configured prior to this release will not have Backup Assignment and Backup Assigned To values set. We recommend updating these Case Type Assignment records with backup assignment information. However, if you do not update these records, missing or blank values are accounted for in the validation logic as outlined below.

The validation process when adding a new Client Service Case works as follows when the backup assignment is a Single User or Client Role:

• Validation Step 1: If the Default Assignment on the Case Type Assignment record is Single User and that user is valid, the Assigned To user on the case displays the default assigned single user.

• Validation Step 2: If the Default Assignment on the Case Type Assignment is Single User and that user becomes invalid, the Assigned To user on the case displays the user or role from Backup Assigned To field.

• Validation Step 3: If the Backup Assigned To user or role is invalid, the Assigned To user on the case displays as the Manager of the responsible department from the Case Type category metadata associated with the case type. For example, if the Category field on the Case Type record for 401K is "Benefits", the system will check the Department Admin/Department Details record for "Benefits" and display the name shown in the Manager field as the Assigned To user on the case.

• Validation Step 4: If no valid default assignments can be found, the Assigned To field will be left blank, and the following error message displays when you click Apply or Save on the case record: "There is no Assigned To selected and the associated case type does not have a default user selected. Please either set a default user on the case type or select an Assigned To user. "

See Configuring Case Types.

Added Staffing Business Rule to Split the PrismHR Location Code into Two Fields

A new SplitStaffingLocationCode business rule has been added that splits the Location Code imported from PrismHR into two fields. The Location Code imported from the PrismHR API displays on the Client Location dataform in the "Location Information" fieldset of ClientSpace. For staffing clients, it is comprised of a Staffing Client ID and a Staffing Client Location or Department. When the business rule runs, the PrismHR Location Code is split into a Staffing Client ID and a Staffing Client Location and two, new corresponding fields located on the Client Location dataform ClientSpace in the "Staffing Location Information" fieldset are populated as shown in the example below:

Note: 

• The SplitStaffingLocationCode business rule is Inactive by default.

• The rule is only triggerable when the Contract Type on the Client Master is "Staffing".

• The "Staffing Location Information" fieldset is part of the Staffing Implementation Group. This means that the fieldset does not display unless ClientSpace is configured to use the Staffing module.

• The Location Code is split on a hyphen that must be found in the value imported. If this is not included, the value will not be split.

See Staffing Business Rule Methods.

Added Staffing Placement Fields to Server Data Proc 1 for Use in Workflow Conditions, Business Rules, and Email Templates on the Comp Claim Dataform

To support the need to generate worker's compensation workflows for the First Report of Injury (FROI) on staffing employees (plus various other use cases related to staffing employees), the following Staffing Placement form fields and related Comp Claim Claimant tab fields have been added to Server Data Proc 1 for use in building workflow condition expressions, retrieving "Replace" fields, creating email template conditions, and configuring business rules:

• Division Code

• Location Code

• Placement ID

• Position

• Start Date (i.e., placement start date)

• End Date (i.e., placement end date)

See Server Data Proc 1 for Workflow Channels, Email Template Tasks and Business Rules Triggered from Staffing Placement Dataform

Changed the Location Field Display Value and Lookup List Values to Include Location Code and Location Name for Staffing

When the Contract Type on the Client Master form is set to Staffing, the Location field display value and lookup list options show the Location Code with the Location Name next to it in parentheses. This display change affects the following dataforms:

• Comp Claim Claimant

• Staffing Placement

• Certificate Of Insurance

• Employment

The example image shows Location field display value and lookup list options on the Staffing Placement window:

If the Contract Type is not set to Staffing, the Location field display value and lookup list options only display the Location Name as in previous versions.

See Staffing Placement Dataform.