Release 136 Notes

R136 Sprint: 1/1/2024 to 1/31/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 1/1/2024 to 1/31/2024

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 First Tuesday of the month February 13, 2024
Group 2 Second Tuesday of the month February 20, 2024
Group 3 Third Tuesday of the month February 27, 2024

Enhancement

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

Advanced Administration

Case

Enhancement
65341

Updated Query Widget

The Query Widget configuration's GUID is now available as a parameter in the XSLT file, making each Query Widget unique even if they share the same XSLT library type.
66042

Updated Employee Benefits Detail Form (Configuration)

The following changes have been made on the Employee Benefits Detail form:

  • The Plan Type field was using an incorrect Lookup Group. Plan Type now uses the Benefit Plan Category lookup group.

  • Added B - Bond to the Benefit Plan Category lookup group.

  • Updated Benefit Plan Category lookup group Import IDs as follows:

    • M - Medical/Health

    • N - Dental

    • V - Vision

    • L - Life Insurance

    • O - Other

    • B - Bond

  • Updated the Employee Benefits Detail Status lookup group Import IDs as follows:

    • C - COBRA

    • E - Eligible

    • A - Active

    • T - Terminated

    • W - Waived

  • Also added decode values to the following Employee Benefits Detail Status lookup group Import IDs:

    • C - COBRA

    • E - Eligible

    • T - Terminated

    • W - Waived

  • Deactivated the following Employee Benefits Detail Status lookup group values:

    • Pending

    • Expired

  • Validated that mapping to Plan Type and the Status fields use the appropriate PrismHR paths and are configured as lookups.

  • Added a Plan ID column to the Employee Benefits Detail grid view.

  • Changed the Plan Tier field label to Rate Group.

66045

Updated Employee Benefits Detail Form (Coverage Levels)

The Descriptions and Import IDs of Benefit Coverage lookup group values have been updated as follows:

  • EO

    • Import ID: |EO|EE|1EE|AutoEE|

    • Description: Employee Only

  • ES

    • Import ID: |ES|3ES|E+S|

    • Description: Employee + Spouse

  • EC

    • Import ID: |EC|2EC|AutoEC|

    • Description: Employee + Child

  • EK

    • Import ID: DP

    • Description: Domestic Partner

  • EF

    • Import ID: |FAM|5FAM|AutoFAM|

    • Description: Employee + Family

66046

Added Benefit Group PrismHR API Mapping/Importing and Benefit Classification Update

This enhancement adds the ability to:

  • Import Benefit Groups from PrismHR.

  • Update the Benefit Classification field on ClientSpace Employment records using imported PrismHR Benefit Classifications.

 

Note: 

  • The configuration for this enhancement requires the assistance of ClientSpace Professional Services. The representative will help you verify your general import configuration settings and ensure that your Client Master records are set to Sync with PrismHR(Import). The representative may also verify and assist with other configuration requirements such as adding the Client Benefit Group Class to the Client Schema PrismHR subscription record and verifying the configuration of the Employee Schema PrismHR subscription record. (Subscriptions establish the type of information that must be monitored for change. See PrismHR Subscription Dataforms.)

  • Multi-tenancy is supported.

 

Key changes include:

  • Two new Import Map Header files, HRPAPI_initial_codes_benefitgroup*.csv and HRPAPI_codes_benefitgroup*.csv , were added to System Admin > Advanced > Configure Import for the Benefit Groups initial and ongoing imports.

  • Both Import Map Header files are set up to import the following two fields:  BenefitGroupCode and BenefitGroupDescription.

  • The BenefitClassificationCode field on the HRPAPI_initial_employment*.csv and HRPAPI_employment*.csv Map Header files has been set to Active. This imports the PrismHR Benefit Classification.

  • Now, when the PrismHR API runs, the following occurs:

    • Benefit Groups from PrismHR are created in ClientSpace.

    • The Benefit Classification field on the ClientSpace Employment record is updated to match PrismHR.

66047

Added Business Rule to Set the OBP on the Employee Benefits Detail Form

A new business rule, Set OBP, has been added (System Admin > Advanced > Manage Rules). The rule sets the Offered Benefits Plan field on the Employee Benefits Details form. The rule triggers when you create and save a new Employee Benefit Details record or the Offered Benefit Plan field on an existing Employee Benefit Details record is empty (i.e., blank) and you save the record.

For the Offered Benefit Plan to be set by the business rule, the following criteria must be met:

  • The Employee Benefits Detail form Plan ID, Effective Date, and Benefit Classification fields must be completed prior to saving.

  • The Employee Benefits Detail form Plan ID must match the parent benefit plan's Carrier Plan Code.

  • The Employee Benefits Detail form Effective Date must be greater than the Offered Benefit Plan Effective Date.

  • The Employee Benefits Detail form Effective Date must fall between the Offered Benefit Plan Effective Date and Expiration Date.

    Note: A blank Expiration Date on Employee Benefits Detail form is acceptable.

  • The employee must be part of the Benefit Group for the Offered Benefit plan.

66197

Updated PrismHR Bi-directional Contacts Sync to Support Multi-tenancy

Previously, the Bi-directional Contacts Sync scheduled process used to sync Contacts between PrismHR and ClientSpace did not create ImportIDs containing a PEOID for multi-tenancy environments. Now, the Bi-directional Contacts Sync scheduled process has been modified to use the PEOID (if present) to match Contacts between ClientSpace and Prism, and to set the ImportID of the Contact to PEOID::ClientNumber::PrismContactID or ClientNumber-PrismContactID depending on whether the Client Master record contains a PEOID value.

Performance

Case

Enhancement

65812

Refactored Client Service Grid Quick Search

Refactored the Client Service grid's Quick Search feature to improve performance.

65984

Refactored Link Badge Count Process

Refactored the system process responsible for returning badge counts on links to improve performance.

Fixes

Case

Issue summary

Resolution
66007

Cancel Button Would Not Close Workflow Item Opened with Visualizer

Previously, if a user opened the Visualizer, clicked Sort, canceled the Sort without making a change and then opened a Workflow item in the Visualizer, clicking the Cancel button to close the Workflow item did not work. Now, the issue with Sort and Cancel have been resolved and clicking Cancel closes the workflow in the Visualizer.

66219

JoinRowGuid Column Became Null After Survey Submission

Previously, the JoinRowGuid column (an identifier column) on the Survey Results form became null after the survey taker submitted the survey. Now, the JoinRowGUID is preserved and does not become null.