Release 138 Notes

R138 Sprint: 3/4/2024 to 3/29/2024. To learn about product features that you may not recognize, contact ClientSpace Professional Services.

Release Schedule

Release updates are implemented by the group, as indicated in the following table.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for ClientSpace Professional Services.

Sprint 3/4/2024 to 3/29/2024

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 Third Thursday of the month April 16, 2024
Group 2 Fourth Tuesday of the month April 23, 2024
Group 3 Fifth Tuesday of the month April 30, 2024

Enhancement

Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, General, and Staffing.

ClientSpace Premium

Case

Enhancement
66065

Added Ability to Set Coverage Level Labels on Benefits Plans

In preparation for implementing an upcoming feature to import Benefit Plans from PrismHR to ClientSpace, we have added Prism Coverage Level fields. These fields act as import mapping from the Prism Benefit Plan rules to ClientSpace Offered Plan Employee Contributions. A new fieldset named PrismHR Coverage Labels has been added to the Benefits Plan dataform near the bottom of the form. You can add up to five (5) labels as shown in the example below:

Benefits Plan Prism Coverag Levels

Note:

If you leave these fields blank, ClientSpace uses the following default PrismHR values:

  • EE for CoverageLevel1

  • ES for CoverageLevel2

  • EC for CoverageLevel3

  • EF for CoverageLevel4

  • EK for CoverageLevel5

These default values will not populate the PrismHR Coverage Labels fieldset. Only your entries are displayed in the fieldset. The default values are the typical values defined in PrismHR as the Plan Type. If your Plan Type values differ from the default values, you should map the fields in the PrismHR Coverage Labels fieldset as shown in the example image above.

For more information, please contact your Professional Services representative.

66794

Added and Updated Fields and Rules Related to Offered Benefits Plan, Benefits Batch, and Benefit Group Dataforms

In ClientSpace Release 137 (R137) we added and updated multiple fields and rules related to the Offered Benefits Plan, Benefit Group and Benefits Batch dataforms. Since that time, we have learned that some fields added to the Benefits Batch and Benefit Group dataforms also needed to be on the Offered Benefits Plan dataform and some additional new fields needed to be added to the Offered Benefits Plan dataform.

 

To eliminate the need for duplicate data entry, business rules were added to copy field values from the Benefits Batch and Benefits Group dataforms to the matching fields on the Offered Benefits Plan dataform (if the fields on the Offered Benefits Plan dataform are empty.)

Note: All fields are Active by default and all field sets are expanded by default.

 

Benefits Batch Dataform Changes:

  • Added Default Values OBP fieldset and moved Eligibility Type and Eligibility Status fields into the new fieldset.

Benefit Group Dataform Changes:

  • Added Default Values OBP fieldset and moved Days from Eligibility Status, Eligibility Days From, and Benefit Eligibility Date Used into the new fieldset.

Offered Benefits Plan Dataform Changes:

  • Added the following new fields to the Setup Details fieldset: Eligibility Status, Eligibility Type, Minimum Age, Days From Eligibility Status, Eligibility Days From, and Benefit Eligibility Date Used.

New Business Rules:

Added three (3) business rules.

Rule Title

Method

Description
Set OBP Defaults from BB and BG SetOBPDefaultsfromBBandBG Pulls the defaults from the Benefits Batch fields (Eligibility Status and Eligibility Type) and the Benefit Group form fields (Days From Eligibility Status, Eligibility Days From, Benefit Eligibility Date Used) onto the Offered Benefits Plan if the Offered Benefits Plan fields are empty.
BB Set Default Fields BBPushFields

Pushes the Eligibility Status and Eligibility Type fields from the Benefits Batch on to the Offered Benefits Plan if the Offered Benefits Plan fields are empty.

BG Set Default Fields

BGPushFields

Pushes the Days from Eligibility Status, Eligibility Days From, and Eligibility Date Used fields from the Benefit Groups on to the Offered Benefits Plan if the Offered Benefits Plan fields are empty.
66935

Added Benefit Parent Company Field to Benefits Batch

In ClientSpace Release 135 (R135), we added the ability to clone Offered Benefit Plans from a parent company's Benefits Batch record to a child Benefits Batch in a related workspace. In R135, the parent company was identified using the Parent Company field on the Client Master record in the child workspace.

 

Since that time, we have learned that the Parent Company field on the Client Master record is mapped to the Control Group in PrismHR where adherence to a specific parent company naming convention is required for federal tax reporting purposes. To ensure no functionality conflicts, the parent company for the "clone Offered Benefit Plans" functionality is now identified using a separate Benefit Parent Company field. This field has been added to the Benefits Batch dataform as an organization lookup field. The field only lists values for organizations that have a workspace. Set the parent company in the Benefit Parent Company field of the child Benefits Batch record by selecting a valid value from the lookup list of organizations.

 

Note: Setting the parent company on the child Benefits Batch also simplifies the procedure of cloning OBPs as you no longer need to set or verify the parent company on the Client Master and then open the child Benefits Batch record. All steps can be completed from the child Benefits Batch.

See Cloning Offered Benefit Plans.

Advanced Administration

Case

Enhancement

66736

Removed Legacy "#IsDirtyAndIsEmpty" and "#IsDirtyAndIsNotEmpty" Logic from Business Rules

In ClientSpace Release 137 (R137) we added the following new dataform rule trigger operators:

  • Is Dirty And Is Empty: Executes if the Primary/Secondary Trigger Field on the form has changed and is now empty.
  • Is Dirty And Is Not Empty: Executes if the Primary/Secondary Trigger Fields on the form has changed and now contains a value.

The new trigger operators replace old legacy special trigger values of #IsDirtyAndIsEmpty and #IsDirtyAndNotEmpty.

With this update, any of your existing business rules that use the legacy trigger values will be updated to now use the new dataform rule trigger operators. Any new rule configurations created to trigger from field change operations should be configured using these new operators.
66752

Field Deletion/Inactivation Validation Messages Updated to Include Dataform Name

Previously, when you attempted to delete or inactivate a dataform field in Dataform Admin (System Admin > Advanced > Dataform Admin) and that field was being used as a parameter by one or more business rules, the validation message that displayed only listed the affected business rule(s) and associated method(s)/parameter(s).

Now, the validation message has been enhanced to also include the dataform name where the field is being used. Both soft error validation messages and hard error validation messages have been updated as shown in the examples below:

Note: 

  • Whether a hard error or soft error displays is determined by the Rule Type defined in the custom logic rule settings (System Admin > Manage Rules).

  • The bulleted list items shown in the message are links that take you directly to the related custom logic rule.

See Deleting or Inactivating Dataform Fields.

67613 /66814

Added Advanced Client Info Setting to Org Type Ahead Datatype

An Advanced Client Info setting has been added to the Org Type Ahead field datatype (i.e., Element Type) in (System Admin > Advanced > Dataform Admin). Org Type Ahead fields are used to populate pick lists such as the Parent Company lookup field located on the Client Master dataform. When Advanced Client Info is selected, lookup values include workspace-specific information such as PEOID , Client Number and DBA , if entered. This additional information can help users make the correct company selection when companies are similarly named.

See Adding Dataform Fields.

General Enhancements

Case

Enhancement
66583

Added Badge Counter to Associated OBPs Link on Benefits Batch Dataform

Previously, in ClientSpace Release 135 (R135) we added an Associated OBPs link to the Action Center of the Benefits Batch dataform. Clicking the link opens the Offered Benefits Plan search dashboard if there is more than one associated Offered Benefit Plan. If there is only one associated Offered Benefit Plan, clicking the link opens the Offered Benefits Plan form with plan details displayed.

 

In the current Release R138, we have added a badge counter to the Associated OBPs link to indicate the number of Active OBP records associated with the batch. If an asterisk (*) displays next to the counter, Inactive OBP records are also present.

Benefits Batch Action Center Associated OBPs Link

Fixes

Case

Issue summary

Resolution
67712

Corrected Rounding Issue

Corrected an issue related to rounding NULL money and decimal values.