Release 155 Notes

R155 Sprint: 8/1/2025 to 8/31/2025. 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 8/1/2025 to 8/31/2025

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 Second Thursday of the month September 11, 2025
Group 2 Third Tuesday of the month September 16, 2025
Group 3 Fourth Tuesday of the month September 23, 2025

Enhancement

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

ClientSpace Premium

Benefit Plan Manager (BPM)

Case

Enhancement

72651

Added Support for Cafeteria Contributions in BPM

You can now add cafeteria plan contributions in the Benefit Plan Manager (BPM) which are then updated on the Benefit Group in ClientSpace.

The following changes were made in ClientSpace made to support this feature:

  • Once you click the Cafe Eligible flag in the "All Plan Types" section of the Offered Benefits Plan (OBP) dataform, you can now select a Contribution method of cafeteria plan. Cafe Eligible is a required field for cafeteria plans.

  • A Cafeteria Plan Contribution Method lookup value has been added to the Benefit Plan Contribution lookup group on the OPB. Set the value as shown in the example below:

    Note: When Cafeteria Plan is selected as the Contribution Method, all Employee Contribution fields are set to 0.0000.

  • A hard error (using business rule method HE_RequiredCafeEligForCafeCont) has been added. This error is triggered if you select a Contribution Method of Cafeteria Plan on the OBP without checking the Cafe Eligible flag and then click Apply or Save. The default error message text is: "This plan does not support the 'Cafeteria Plan' contribution method. To use this option, the plan must first be marked as Cafeteria Eligible."

The following changes were made in BPM to support this feature:

  • A Cafeteria Contribution Amount field and section have been added to the top of the Group Summary > Summary tab in BPM. This section only displays if there is at least one cafeteria plan identified in the Benefits Group. This reflects the yearly employer contribution that employees can use toward cafeteria plans. The employee pays the remaining premiums using pretax dollars up to the IRS contribution limits. Your client must click Save in the section to apply the change. Note also that cafeteria plans are identified in the Group Summary > Summary grid by a coffee cup icon.

    Note: Once your customer clicks Save in the Cafeteria Contribution Amount section of BPM, the amount is saved on the ClientSpace Benefits Group record associated with the OBP.

  • On the BPM Selection Summary/Signature page, any Cafeteria Contribution Amount(s) entered are listed for review. They are sorted by Benefit Group:

See:
73226

BPM Signature Image Is Now Stored on Benefits Batch

The last signature captured on the Benefit Plan Manager (BPM) on the BPM Selection Summary/Signature page is now stored in the BPM Signature file upload field on the associated Benefits Batch as an image file.

SeeAdding a Benefits Batch.
73728

Added BPM Waiting Period Field

Previously, plan eligibility waiting period details were only set in ClientSpace. Now, a Waiting Period field has been added to BPM on the Group Summary tab:

The following changes were made in ClientSpace to support this feature:

  • Updated the Waiting Period Metadata dataform:

    • The Of Service field has been renamed Eligibility Days From.

    • The Minimum field has been inactivated.

  • Updated the Benefit Groups dataform:

    • A Waiting Period lookup field has been added.

    • Eligibility Days From, Days from Eligibility Status, and Benefit Eligibility Date Used fields display in the "Default Values OPB" section.

      • Added a field display rule to lock the fields in the "Default Values OBP" section when a value is selected in the Waiting Period field. The field backgrounds turn gray and the populated field values cannot be edited.

      • When you select a Waiting Period, the fields auto-fill and cannot be edited.

      • If you clear the Waiting Period field, the "Default Values OBP" fields allow manual data entry.

  • Added three (3) new business rules on the Benefits Groups dataform. All rules use the _SetFieldFromLookupMetadata business rule method:

    • Days From Eligibility Status: Uses the metadata from the Waiting Period lookup to populate the Days From Eligibility Status field on the Benefit Groups dataform.

    • Eligibility Days From: Uses the metadata from the Waiting Period lookup to populate the Eligibility Days From field on the Benefit Groups dataform.

    • Benefit Eligibility Date Used: Uses the metadata from the Waiting Period lookup to populate the Benefit Eligibility Date Used field on the Benefit Groups dataform.

  • Updated the Benefits Waiting Period Lookup group to add four (4) new values and inactivate three (3) unused values. This list is used to populate the Waiting Period lookup on the Benefit Groups form and in BPM on the Group Summary tab. Valid options are:

    • 1st of this month, following 30 days after Status Date

    • 1st of this month, following 60 days after Status Date

    • 1st of this month, following 90 days after Status Date

    • 90 days following Date of Hire

    • 1st of month after, following 0 days after Date of Hire

    • 1st of month after, following 30 days after Date of Hire

    • 1st of month after, following 60 days after Date of Hire

    • Date of Hire

    • Status Date

    Note: All waiting periods options are flagged as System values on the associated Lookup Details records. This means that they cannot be edited. If changes are required, they must be requested through your ClientSpace Professional Services representative.

The following changes were made in BPM to support this feature:

  • Added a Waiting Period field to BPM on the Group Summary tab which displays in a tile at the top of the tab.

    IMPORTANT: For Benefit Groups that existed prior to this enhancement, the BPM Waiting Period value defaults as 1st Month after, following 0 days after the Date of Hire (which is the first value in the list) and the ClientSpace Waiting Period field is blank. You must manually edit your Benefit Groups records in ClientSpace and save the changes if you want the Waiting Period field in ClientSpace to be populated and you want a different value than 1st Month after, following 0 days after the Date of Hire to display in BPM.

     

    Once you receive this enhancement, any new Benefit Groups records you add to ClientSpace will have a default Waiting Period of Date of Hire. Note that this default has been set for you on the Benefits Waiting Period Lookup Details record and cannot be changed without the assistance of a ClientSpace Professional Services representative:

  • The Waiting Period field may appear by itself or display under the Cafeteria Contribution Amount field (if the offered plan includes one or more cafeteria plans).

  • When a BPM end user updates the Waiting Period field, they must click the Save button to apply the change. The associated Benefit Groups record in ClientSpace is also updated upon Save.

See:

74241

Added Ability to Generate and Store Signed and Approved Benefits Selections on the Benefits Batch

You can now generate and store signed and approved benefits selections on the Benefits Batch by clicking the DocuSign Benefits Renewal link in the Action Center after the batch is finalized in BPM. The signature image and approval date on the Benefits Batch in the BPM Signature and Date of Approval fields are displayed on the Benefits Renewal DocuSign Approval report as shown below:

Note: 

  • If you permit a change request after the Benefits Batch is finalized and uncheck the BPM Renewal Approval (HasBPMRenewalApproval)checkbox, this sets the Benefits Batch tile in BPM back to "Ready to Review" so that your customer can review the changes and sign off on them again on the BPM Signature/Selection Summary page. This also clears the BPM Signature and Date of Approval fields on the Benefits Batch and regenerates the Benefits Renewal DocuSign Approval report without a signature and approval date and adds it to the Renewal Approval field. It contains a blank signature line and placeholder for the approval date. Generate the report again once the changed Benefits Batch is finalized to add the newly signed version of the report to the Renewal Approval field.

  • To use this feature, the Merge Admin Detail (System Admin > Outputs > Merges) Template File field must be set to Benefit Renewal DocuSign Merge Template_2025 and the Output Type must be set to PDF as shown in the example below.

See Storing Signed and Approved Benefits Selections and Benefits Renewal Merge.

Other ClientSpace Premium

Case

Enhancement

72910

Updated the Benefits Export API to Export Supplemental OBPs from ClientSpace to PrismHR

Previously, the Benefits Export API only exported Offered Benefit Plans (OBPs) and related plan details for Health, Dental and Vision plan categories. Now, the Benefits Export API can also export supplemental plans. Any active OBP in Selected status for any plan category can be exported.

 

To support this enhancement, the following changes have been made:

  • The ExportBenefitRulestoPrism business rule method was updated to evaluate all PrismHR insurance classes: M (Medical), N (Dental), V (Vision) , D (Long-Term Disability), S (Short-Term Disability), L (Life), B (Bond), and O (Other).

  • When the PrismHR insurance class is M (Medical), N (Dental), or V (Vision), there are no changes. The pre-existing processes for updating the benefit rules remain in place.

  • When the PrismHR insurance class is L (Life), B (Bond), D (Long-Term Disability), S (Short-Term Disability. or O (Other) the following values are updated in PrismHR from the ClientSpace OBP on the PrismHR  Benefit Plan Maintenance /Group Benefit Plans (Client)/Benefit Rules page under "Contribution Rules":

    • Contribution Method defaults to Percent.

    • Contribution Amount uses the percentage value from the ClientSpace OBP  EO% Coverage Level field.

    • DEP Contribution Amount uses the percentage value from the ClientSpace OBP Dependent Contrib% field.

      Note: If the value is blank in ClientSpace, the value is passed as blank (i.e., empty) to PrismHR as well. It will not default to 0 when blank. 0 will display only if a user enters it.

  • When the PrismHR Insurance class is L (Life), the following additional fields are updated from the ClientSpace OBP  to the corresponding fields on the PrismHR Benefit Rules page under "Coverage Rules" : Multiplier Pay Basis, Pay Multiplier, Rounding Method, Round Timing, Coverage Amount and Coverage Maximum.

  • When the PrismHR Insurance class is B (Bond), D (Long-Term Disability), or S (Short-Term Disability, the following additional fields are updated from the ClientSpace OBP to corresponding fields on the PrismHR Benefit Rules page under "Disability Coverage Rules" : Percent of Base, Rounding Method, Benefit Amount, and Alternate Base Calculation.

  • Export errors display on the affected OPB record in the Export Log field.

See Exporting Benefit Plans to PrismHR.
73016

Updated Benefit Plan Export API to Set Health, Dental and Vision Contribution Percentages

Previously, when you exported Offered Benefit Plans to PrismHR, the ClientSpace Benefit Plan Export API only set PrismHR benefit rule contribution values as fixed amounts. Now, the Benefit Plan Export API sets the PrismHR benefit rule contribution values as percentages for each coverage level where the following is true:

The plan Category is Health, Dental or Vision and the Employer Contributions (%) Contribution Method is Manually Set Percentages , Absorb Increase, Contribute EO Premium, Match EO Contribution, Combine EO and Dependent, or Cafeteria Plan.

How this can help: Percentages are the most used contribution method in the PrismHR Benefits Administration module as they allow you to set variable premium rates. This change provides a more seamless user experience between ClientSpace and PrismHR.

The applicable percentages are set in the Contribution EE Bill and Contribution DEP Bill fields of PrismHR Benefits Administration on the Benefit Plan Maintenance /Group Benefit Plans (Client)/Benefit Rules page under "Contribution Rules" as shown in the image below:

The system logic for updating the fields is as follows for each affected Contribution Method:

Contribution Method Contribution EE Bill Contribution DEP Bill
Manually Set Percentages Uses percentage values from the ClientSpace OBP Coverage Levels fields of EO%, ES%, EC%, and EF% for all associated PrismHR Plan Types (EX: EE, ES, EC, FAM). Sets the field to 0.00 for the EE/EO plan type since there are no dependents. Uses percentage values from the ClientSpace OBP  Coverage Levels of ES%, EC%, and EF% fields for all associated PrismHR Plan Types (EX: ES, EC, FAM).
Absorb Increases Uses percentage values from ClientSpace OBP  Coverage Levels of EO%, ES%, EC%, and EF% fields for all associated PrismHR Plan Types (EX: EE, ES, EC, FAM). Sets the EE/EO plan type to 0.00 since there are no dependents. Uses percentage values from ClientSpace OBP  ES%, EC%, and EF% fields for all associated PrismHR Plan Types (EX: ES, EC, FAM).

Contribute EO Premium

Set to 100.00.

Set to 0.00.

Match EO Contribution

Uses percentage value from the ClientSpace OBP EO% Coverage Level field.

Uses percentage value from the ClientSpace OBP Dependent Contrib% field.

Cafeteria Plan

Set to 0.00.

Set to 0.00.

Note: 

  • There have been no changes to the system logic for updating Contribution EE Bill and Contribution DEP Bill in PrismHR when the ClientSpace Contribution Method is Manually Set Dollars or any other Contribution Method not listed in the above table. Fixed dollar amounts are still exported for the Manually Set Dollars contribution method.

  • In PrismHR Benefits Administration on the Benefit Plan Maintenance /Group Benefit Plans (Client)/Benefit Rules page under "Benefit Rules", the Contribution rule amounts made by Company or Employee field is automatically set to "Company" when the Benefits API sets the contribution rule amounts.

See Exporting Benefit Plans to PrismHR.
73203

Updated Benefits Plan Export API Field Mappings

Several Benefits Plan Export API field mappings have been added or updated. The Benefit Plan API Export Field Mapping Excel file attachment has been updated in Attachments and Templates to the reflect these changes.

See Benefit Plan API or Attachments and Templates.

Advanced Administration and System Administration

Case

Enhancement

70555

Added "Default to Current User" to User Datatypes in Dataform Admin Field Properties

Previously, the Default to Current User checkbox was not available for all user datatypes on the Dataform Admin (System Admin > Advanced > Dataform Admin) Field Properties form. Now, the Default to Current User checkbox is present for the following user datatypes:

  • Project User

  • Project User Type Ahead

  • User

  • User Filtered by Entity

  • User Filtered by Entity Type Ahead

  • User Type Ahead

72074

Added a "CC" Type for DocuSign Email Templates

You can now specify a carbon copy (CC) type on DocuSign email templates in the Type field of the Step 3: Addresses tab. CC recipients can only view documents. They cannot make changes to documents.

SeeStep 3: Addresses.

72308

PrismHR Initial and Ongoing Imports Upgraded to Align with New prismhr-api

We have completed a multiphase project to upgrade our PrismHR integration over the past several releases from API 1.30 to prismhr-api. This will allow us to connect with more fields and processes in PrismHR going forward. These changes include updated "prismhr-api to ClientSpace" field mapping.

See Attachments and Templates

74158

Added Discrete User Admin Module and "Immediate__Supervisor" Role

A discrete User Admin module (Modules > User Admin) has been added to allow supervisors to manage user records in a separate module so they do not require access to any part of the System Admin module.

 

Note: 

  • A Global Admin or above must assign the supervisor the new Immediate_Supervisor role (System Admin > Security > Roles). The necessary security entities have been added to the Immediate_Supervisor role with no permissions granted.

  • A Global Admin or above must grant permissions to the one or more security entities shown below to allow supervisors to access the User Admin module and manage user records

Security Entities Definitions

  • SysAdmin_User_Module: Security entity that controls access to the User Admin module.

    Note: Without this entity, a user has no access to view the module.

  • SysAdmin_User_AdministratorSettings: Security entity that controls access to the "Administrative Fields" fieldset.

  • SysAdmin_User_UserSettings: Security entity that controls access to the "User Settings" fieldset.

  • SysAdmin_User_OutOfOffice: Security entity that controls access to the "Out of Office" fieldset.

  • SysAdmin_User_General: Security entity that controls access to the "General" fieldset.

Access Rights Definitions

Note: With Add access or above, View rights are implied. For instance, setting View + Add or Add only provides the same access permissions.

  • View only:  Users can view records but can make no changes. Fields are locked.

  • View + Add (OR  Add only): Use rs can view and add records. They can edit fields while in "Add" mode (i.e., while Record ID = 0). Once the record is saved, they can no longer edit the record.

  • View + Edit (OR Edit only): Users can view and edit existing records. They cannot add new records.

  • View + Add + Edit (OR Add + Edit only) OR Admin: Users can view records, add new records, and edit existing records.

How this can help: Immediate Supervisor users can quickly perform basic user account management functions that previously required assistance from a Global Admin, such as:

  • Editing user record fields to add the Immediate Supervisor on Inactive records with no supervisor assigned. (Requires Edit access or above to SysAdmin_User_Module and SysAdmin_User_General.)

  • Enabling the "out of office" and backup user settings for a user who is unable to do it themselves due to an emergency or sudden illness. (Requires Edit access or above to SysAdmin_User_Module and SysAdmin_User_OutOfOffice.)

  • Setting the Change Password Next Login field to require a report to update their password. (Requires Edit access or above to SysAdmin_User_Module and SysAdmin_User_AdministratorSettings.)

  • Viewing and selecting modules that the user can access.

  • Viewing role and module licenses.

Here are some examples of tasks Immediate Supervisor users can perform with View + Edit access to all User Admin entities:

  • Access the User Admin module.

  • View and edit the user account records of all their Active direct reports and all levels of indirect reports beneath them.

  • View and edit the user account records of all Inactive users where the Immediate Supervisor field is blank or where "Current User" is specified in the Immediate Supervisor field of the user record.

Note: 

  • Global Admin user, Developer user, Template user and System user records are excluded from the User Admin module. Immediate Supervisor users cannot view these records.

  • Once an Immediate Supervisor user selects a value in the Immediate Supervisor field of an Inactive user record and checks the Active checkbox to make the record active, the Immediate Supervisor field as well as the Active checkbox become locked and can no longer be edited except by a Global Admin or above.

See Adding or Editing User Accounts from the User Admin Module

Also, be sure check out the Video link at the end of the referenced article above.
74159

Added Dynamic Field Display Across Tabs

Dynamic field display functionality (System Admin > Advanced > Manage Field Display) has been enhanced to allow you to create a field display rules across tabbed dataform relationships. This includes the following scenarios:

  • A field on a parent form triggers the display of a field on a tabbed child form.

  • A field on a tabbed child form triggers the display of a field on a parent form.

  • A field on a tabbed child form triggers the display of a field on another tabbed child form.

When you select a Location form of a parent or child dataform, this determines the fields available in the this item drop down list. When you select a Field Source of Form Data (i.e., the Location form), a parent form related to the Location form, or another child form related to the Location form, this determines the fields available for selection in the When this field drop-down list. Your ability to configure field display rules involving parent to tabbed child, tabbed child to parent or tabbed child to another tabbed child form depends on the selections in these fields.

 

Note: Tab: <DataformName> selections are only available in the Field Source drop-down list if the Location form has tabs. Selecting a tabbed form allows you to use a field from a tabbed child form as the triggering field.

 

In the example below, the Send Survey field selected in When this field is located on the parent form. The Customer Data field selected in this item is on a tabbed child form. When the Send Survey field is True (i.e., the checkbox is checked) on the parent form, the Customer Data field on the child tabbed form will display.

See Configuring Dynamic Field Display.

General User Enhancements

Case

Enhancement

71739

Improved Action Center "My Tasks" Functionality - Part 1

The following improvements were made to the Action Center "My Tasks" pane to increase the functionality and generally improve the user interface:

  • Updated Task Status to display only the Lookup Decode instead of the Code and Decode: Previously, the Task Status displayed the Code and Decode from the Lookup Details separated by a hyphen. Now only the Decode value displays.

     

    Note: The Code is a typically shorter and not as descriptive "behind the scenes" value while the Decode is the more descriptive display value.

     

    Old:

    New:

  • Moved the Task Status closer to the Task Number: The Task Number and Task Status are now closer together.

    Old:

    New:

See Workspace Action Center.

73032

Improved Action Center "My Tasks" Functionality - Part 2

The following improvements were made to the Action Center "My Tasks" pane to increase the functionality and generally improve the user interface:

  • Removed "Add Task" label text from Add Task button: Previously, the Add Task button was indicated by "Add Task" label text and a plus symbol. The label text has been removed and the Add Task button is indicated by the plus symbol only.

  • Added Quick Task Button: When the Quick Task button is clicked, an abbreviated form for creating a new task displays.

    The current user defaults in the Assigned To field. The Priority defaults to the configured Task Priority lookup default value, and the cursor is active in Subject field.

    See the referenced article below for completion steps and toolbar button definitions.

  • Added Complete Task Button: You can quickly complete and archive a task by clicking the Complete Task button next to the task in the Action Center.

    The Completed field on the Task form auto-fills with the completed date and time. The Completed By field auto-fills with your user name.

See Adding a Quick Task.
73084

Changed "PEO ID" Field Labels to "Secondary ID" on the Client Master and Multiple Dashboards

The "PEO ID" field label has been changed to "Secondary ID" on the Client Master dataform. The More Search and the column header labels have also been changed from "PEO ID" to "Secondary ID" on the following ClientSpace dashboards:

  • Benefits Batch

  • Cases

  • Clients

  • Employees

  • WC Claims

  • UI Claims

See Client Master Breakdown andMulti-tenant Environments in ClientSpace.

74470

Enhanced Merge Functionality to Include Images in Excel, Word, and PDF Merge Document Output

Dataform image attachments referenced in merge file stored procedures are now included in Excel, Word, and PDF merge document output. For instance, print a Benefits Batch Renewal spreadsheet containing the signature image stored in the BPM Signature file upload field on the associated Benefits Batch.

Note: The only exception when image file cannot be added to merge output is when the value in the Template File field of the Merge Admin Details record (System Admin > Outputs > Merges) points to a PDF. The Type and Output fields can be a PDF file, but not the Template File.

Image files in a merge file stored procedure are designated by an IMG prefix. This feature works by taking any saved image file associated with a corresponding image field in the merge procedure (having an IMG prefix) and placing it in the generated output within a named range (i.e., placeholder area for displaying the image).

This functionality works when the merge is triggered by any method, including:

  • By clicking a dataform link

  • By a dataform save

  • From an email template merge

The following image types are supported: .png, .tif/.tiff, .jpg/.jpeg, .gif, and .bmp.

See Merges.

Technical Enhancements

Case

Enhancement

71331

Changed Manage Import Log File Formatting to UTF-8

Previously, in Manage Import (System Admin > Imports > Manage Import) when viewing the import file on a Manage Import Details record (Links > View Import File), the log contained unreadable characters on Windows 11 operating systems. Now, the import log file uses UTF-8 character encoding, a Unicode standard, to force appropriate formatting of the text with Windows 11.

Fixes

Case

Issue summary

Resolution
73861

Corrected the Issue of Being Able to Select "Date Created" or "Date Updated" on a Scheduled Email or Scheduled Workflow Channel Trigger Condition with a Server Data Proc as the Source

Previously, on Step 4: Conditions of Scheduled Workflow Channel or Scheduled Email Template configuration, you could create an invalid condition using Server Data Proc 1 or Server Data Proc 2 as the Source and a Field of Date Created or Date Updated. Now, the Date Created or Date Updated fields only appear in the Field list when the identified Source is a dataform where Administrative fields such as Date Created or Date Updated are present. These dataform tables are prefaced by "gen_".

74541

Corrected Issue of Pricing Console FEIN Field Not Respecting  CRM Entity

Previously, in ClientSpace release 154, changes were made to improve Organization field security in the Pricing Console and on the Client Master. These changes caused the FEIN field in the Pricing Console to become locked and unable to be managed by the CRM entity. Now, the FEIN field respects the CRM entity.