Release 164 Notes - June 2026

R164 Sprint: 5/1/2026 to 5/31/2026. 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 5/1/2026 to 5/31/2026

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 First Tuesday of the month June 2, 2026
Group 2 Second Tuesday of the month June 9, 2026
Group 3 Third Tuesday of the month June 16, 2026

Enhancements

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
77211

Added the Ability to Make "Waiting Period" Field "Read Only"

A new field has been added to the BPM Config form (located in the Admin Workspace) named Waiting Period is Read Only on BPM.

When the field is set to Yes, the Waiting Period field located on Manage Benefits > Benefits Summary > Group Summary is "read only" and cannot be edited as shown in the example below:

When the field is set to No (the default setting), the Waiting Period field is editable.

See BPM Site Configuration.
77490

Modified "Related Companies" to Exclude Terminated and Inactive Clients or Clients With All Expired or Inactive Batches

Companies are now excluded from the Related Companies popup window when:

  • They have a Status of "Terminated" or the Active checkbox is unchecked on the related Client Master record.

  • All associated Benefits Batches have a Status of "Expired" or the Active checkbox on all associated Benefits Batches is unchecked.

See:

77498

Added Contributions Support for Plan Type = Other

You can now set up contributions for benefit plans with Plan Type = Other.

Previously, the Summary tab (Manage Benefits > Benefits Summary > Group Summary > Summary) was disabled (grayed out) for these plans.

 

With this update:

  • Contributions are now supported for Plan Type = Other.

  • The Summary tab has been renamed to Summary (Contributions).

  • The tab will become available based on how the plan is configured.

To support this enhancement:

  • A new value has been added to the Benefit Plan Suppression lookup group: "Suppress from Contributions Only"

How it works:

If "Suppress from Contributions Only" is selected in the Suppress from Presentation field on a Benefit Plan with a Plan Type of Other:

  • The Summary (Contributions) tab is disabled if all Offered Benefit Plans (OBPs) use this setting.

  • The tab is enabled if at least one OBP does not use this setting.

    • Additionally, only the OBPs where Suppress from Presentation is not set to "Suppress from Contributions Only" will be listed on the tab. All others will be hidden.

If "Suppress from Contributions Only" is not selected in the Suppress from Presentation field on a Benefit Plan with a Plan Type of Other:

  • The Summary (Contributions) tab will be available (unless another suppression setting or business rule hides it).

Note: For all existing plans with Plan Type = Other:

  • The system automatically sets "Suppress from Contributions Only" in Suppress from Presentation by default.

  • This keeps the same behavior as before (no contribution setup). You will not see any changes unless you update this setting.

See BPM Benefit Plan Suppression.

77299

Added Ability to Present Plans to Brokers Prior to the Client Review

You can now allow brokers to access and review Offered Benefit Plans (OBPs) in BPM prior to client access and review. To accomplish this, the following changes have been made:

  • The BPM Contacts form has a new field named BPM Contact Type.

    Note: The "BPM Contact Type" is Inactive by default. To use it, you must activate the field in the BPM Contacts dataform properties.

  • The BPM Contact Type field is associated with a new lookup group named BPM Contact Type. The lookup was added with values of "Client" and "Broker".

    Note: With this release, if the BPM Contact Type field is enabled on the BPM Contacts form, it is set to "Client" by default. The BPM Contact Type field of all new Additional BPM Contacts also defaults to "Client".

  • A new status named "Broker Review" has been added to the Benefits Batch Status lookup group. This status can be used to trigger the BPM email template invitation to be sent to BPM Broker contacts (i.e., where BPM Contact Type = Broker).

    Note: The "Broker Review" status is Inactive by default. To use it, you must activate the lookup value on the Lookup Details form.

  • The Email Template Address Source Procedure named peo_benefitsbatch_emailtemplate_recipient_v2_proc was also modified to add additional Address options:

    • AdditionalBPMContacts: This was an existing option. When selected, all Active additional BPM contacts (i.e., both brokers and client contacts) receive the invitation to review the plans in BPM.

    • ClientAdditionalBPMContacts: When selected, Active additional BPM Client contacts receive the invitation to review the plans in BPM.

    • BrokerAdditionalBPMContacts: When selected, Active additional BPM Broker contacts receive the invitation to review the plans in BPM.

      See the example below of the BPM Prospect Email Template configured to send the plan review invitation to additional BPM Broker contacts when the Benefits Batch Status = "Broker Review".

      Note: Since brokers will not have a Client Number to use for logging in, use the BPM Prospect Email Template for this configuration so that the broker can log in with a Benefits Batch ID.

Tip: To see the BPM Contact Type associated with a contact record on the BPM Contacts dashboard, go to BPM Contacts dataform field properties and add a value in the Multi Col field for BPM Contact Type.

See:

Other ClientSpace Premium

Case

Enhancement

77207

Modified "Combine EO and Dependent" Contribution Method When EE Premium = 0

Previously, the "Combine EO and Dependent" Contribution Method did not work properly in ClientSpace or BPM when the employee premium (EE Premium) was 0 and an "employee only" percentage (EO%) was entered. The percentage value entered in the EO% field was being reset to 0. Now, the value entered in the EO% field is held on the Offered Benefit Plan (OBP) and on the Summary (Contributions) tab of BPM.

See Setting Employer Contributions.

77679

Added Business Rule to Sync Benefit Parent Company from Client Master to Benefits Batch

A new business rule titled Sets and Syncs the Benefits Batch Parent Benefit Company Field has been added. The rule uses the SetBenefitsBatchParentCompany method. The rule is Active by default on all pipelines and is triggered when the Benefit Parent Company field is populated or updated on the Client Master. The Client Master field value is saved to all Active Benefits Batches.

Note: This includes updates to clear the Benefit Parent Company field. The field will also be cleared on affected Active Benefits Batches.

See Business Rule Methods.

77725

Updated Plan Maximum Business Rule Methods to Allow Enforcement by Group Within Category

A new method parameter named ApplyToCategoryIgnorePlanGroup has been added to the HE_RequirePlanMax and SE_RequirePlanMax business rule method configuration settings (System Admin > Advanced > Manage Business Rules) under "Method Parameters". The new setting allows you to choose between enforcing a single maximum across the entire benefit category OR across the benefit groups within the category.

 

Note: These method parameters can be configured for both ClientSpace and BPM.

 

IMPORTANT:  With this update, the default behavior of rules configured using the HE_RequirePlanMax and SE_RequirePlanMax business rule methods will change. The ApplyToCategoryIgnorePlanGroup parameter is unchecked by default allowing the plan maximum to be enforced across each benefit group separately within a benefit category. Previously, the default functionality enforced the plan maximum across the entire benefit category.

 

See:
77740

Added "Default Rate Group" as a Copied Field on Renewed Benefit Plans

The Default Rate Group value (if present) is now copied to the new plan that is generated when a Benefit Plan is renewed.

See Renewing a Master Benefits Plan .

Advanced Administration and System Administration

Case

Enhancement

72370

Updated Standalone Users Import to Update Template UserID Information

The standalone Users import (IMPORT_user*.csv) was updated to insert/update external users.

The standalone Users import was also updated to insert the following Template UserID information on internal and external users from the selected template user record:

  • Department

  • User Type

  • Company

  • Time Zone

  • Change Password Next Login

  • Enable Email for this Account

  • Send Escalation Email

  • Can Create Workspaces

  • Default Workspace

  • Saved searches

  • Existing search settings

  • Workspaces

  • Modules

  • Security

  • Licenses

Note:

  •  Default Workspace is a new addition as the field only applies to a User Type of "External" and IMPORT_user*.csv did not previously insert external users.

  • The ability to use the Template User for updates will be completed in a future development task. The current change allows for inserts only.

 

IMPORTANT: Should you wish to import External users, this enhancement requires you to configure an Import Map Detail record (i.e., mapped field) on the IMPORT_user*.csv Map Header Detail record named DefaultWorkspace exactly as indicated below. Note that for internal user imports, the DefaultWorkspace column is ignored and does not affect inserts or updates.

  • FileColumn = DefaultWorkspace

  • Dataform = Import_User

  • Default = Default Workspace (DefaultProjectID)

  • Data Type = Number

  • Required Column = Checked

  • Default Value = Current Form Value

 

Additional Notes:

  • When importing user records, be certain that the User Type (Internal or External) is correct before importing the records to avoid issues. For instance, if an Internal user record is incorrectly set to a User Type of "External" and a Default Workspace is also entered, once their user record is inserted/updated in ClientSpace, they will only be able to access the identified default workspace. Similarly, if an External user record is incorrectly set to a User Type of "Internal", access to all workspaces will be unlocked for them upon import.

  • For a new External user, if the import file column for Default Workspace is empty, the row will not be inserted/updated and the following error message is logged (System Admin > Import > Manage Import > open import record > View Log File): 

    "Business Logic Errors for data row {RowNumber} [{ImportID}]:   - Error saving User for ImportID {ImportID}: A Default Workspace must be provided for NEW External Users, ImportID {ImportID}".

  • For an existing External user, if the import file column for Default Workspace is empty, the previously entered Default Workspace value will be preserved.

See Configuring Users Import to Insert/Update External Users.

75813

Added "Configure Global Search Results" Validation

When you configure indexing on a dataform (by selecting the Index checkbox on one or more fields in Dataform Properties) without clicking the Configure Global Search Results button and entering, at minimum, a Title to display in the search results, the following warning message displays when you click Save on the Dataform Properties toolbar:

You can select OK to continue saving without making the recommended changes or you can click Cancel to abort the Save process and make the recommended changes.

Additionally, if you add a Subtitle, Title is required. Attempting to save the Configure Global Search Fields form with only a Subtitle value entered results in a "Title is required" error displaying.

See Global Search Configuration.

76378

Added Outlook Email Integration Quick Case Feature

A new Outlook Quick Case feature has been added that allows you to quickly generate a case from an email, importing the mapped field from the email into the new case record along with any email attachments.

Note: The Quick Case feature requires ClientSpace Release 164 or greater.

How this differs from the Post to ClientSpace feature:

With the Post to ClientSpace feature, you are presented with multiple options for importing the email details:

  • Create Activity

  • Attach to Record

  • Create Case

  • Create Task

With the Quick Case feature, a new case is created immediately upon clicking Quick Case.

 

To support this feature, an Outlook Quick Case Create module has been added for use inside the Outlook Email Integration add-in. It includes an Email Addin Configuration field for mapping the email fields used to create the case as well as a Default Workspace field to identify the workspace where ClientSpace will create the case if it cannot find a workspace containing a matching email address on an employee or contact record.

Note: If the module record is not configured with a Type of Outlook Quick Case, the Quick Case button will not display in the Outlook add-in interface.

See Configuring the Outlook Add-In Module for Post to ClientSpace and Quick Case.

77110

Added Ability to Generate Excel, Word and PDF Dataform Merge Procedures to Dataform Properties

The following merge procedure links have been added to the Action Center of the Dataform Properties page (System Admin > Advanced > Dataform Admin) of parent and standalone dataforms:

  • Generate Excel Merge Procedure

  • Generate Word Merge Procedure

  • Generate PDF Merge Procedure

Once you generate a dataform merge procedure, you can access it from Merge Admin (System Admin > Outputs > Merges) in the Procedure field drop-down list.

Note:

  • As previously mentioned, the links only display on standalone or parent dataforms. The links do not display on tab forms. However, when you generate a merge procedure on a parent form, the fields from the related tab forms are included in the merge procedure

  • The dataform must have fields added to it. If there are no fields, the links do not display.

  • If the dataform fields are later updated, you must regenerate the merge procedure to capture the changes.

See Generating and Working with a Dataform Merge Procedure.

77334

Updated PrismHR Initial and Ongoing Contact API to Support Importing Multiple "Contact Type" Values

In the April PrismHR release, the PrismHR Contact Type field (Client > Change > Contacts) was updated to allow users to enter multiple values. To support importing these values from PrismHR, the PrismHR Contact API (PHRAPI_initial_contact*.csv and PHRAPI_contact*.csv) was updated to support importing multiple values and the Contact Type field on the ClientSpace Contact Detail form (Contacts module > Other Info tab) was changed to a multi-lookup field to hold multiple values.

77547

Added Ability to Make Forms "API-Enabled" by Global Administrators

Global administrators with an Advanced System Admin license can access the Include in API checkbox to make a form "API-enabled" (i.e., available in the ClientSpace API). To accomplish this, the Include in API checkbox has now been moved from the "Developer Settings" fieldset (which is only visible to Developer users) of Dataform Properties into "Actions" fieldset of Dataform Properties (System Admin > Advanced > Dataform Admin).

See Adding, Editing or Deleting a Dataform or Dataform Properties.
77661

Added Global Search Configuration Access for Global Administrators

Global administrator users with an Advanced System Admin license can now configure Global Search index, Title and Subtitle values on dataforms and tables.

See Global Search Configuration.
77871

Added Ability to Prevent API Users from Logging into ClientSpace Via the UI

A new checkbox named Disallow UI Login has been added to the "Administrator Settings" fieldset of the User Details window (System Admin > Resources > Users). This field was added to allow Global Administrators or above to prevent API users from logging in from the ClientSpace login window.

Note: The setting is not enabled for API users by default. You must apply the setting to the desired users' profiles.

See Adding and Editing User Accounts.

77972

Updated PrismHR API Processing of Manual Payroll Batches

Previously, when a manual Payroll batch was processed using the Prism Import Payroll Batch Sync scheduled process, ClientSpace was incorrectly creating a billing voucher for each employee. Now, only one voucher per billing code is created.

General User Enhancements

Case

Enhancement

73924

Added Ability to Turn off "Revert to Original Value" Functionality at the User Level

Previously, "Revert to Original Value" functionality that allowed you to restore a previous value in an editable field could only be enabled or disabled at a system level. It was either on or off for all users. When turned on, if you made a change to a field, a popup displayed the original value so that you could choose to restore the previous value:

Now, if "Revert to Original Value" functionality is enabled at the system level, a Disable Original Value Popup checkbox displays on the User Details window. When the checkbox is checked, the "Revert to Original Value" functionality is disabled on the user profile. The User Details window can be accessed by a user (My Profile) or by a Global Administrator in System Admin (System Admin > Resources > Users).

For user steps, see Personalizing Your User Profile

For Global Administrator steps, see Adding and Editing User Accounts.

74747

Added Ability to View Dataform Field Information from the Action Center

A new field has been added to the Action Center More Options drop-down list named Dataform Fields.

When the option is selected, the Dataform Info window displays the Dataform Name, Reporting Table Name (if present), fkProjectId, and the dataform fields.

This feature allows users to obtain dataform and field information without accessing System Administration (System Admin > Advanced > Dataform Admin). Hidden fields and fields affected by field display settings are shown. Inactive fields and fields that the user does not have access to are not shown.

Note: 

  • Fieldsets are collapsed by default. Click the right chevron next to a fieldset to display the fields within it.

  • Only Global Administrators or above can see the "Administrative Fields" fieldset and fields. Even users who have Admin access to a dataform cannot view these fields.

  • Access to the Dataform Info window is controlled by a new security entity named FieldMapping_Access. A Global Administrator can assign View access or above to enable the feature.

See Viewing Dataform Fields from the Action Center.

76795

Added Time Tracker "Quick Time" and Custom Minutes Options

A Quick Time option has been added to the Time Tracking panel in the Action Center of time tracking-enabled dataforms:

This feature allows you to quickly add a completed Manual time entry record of time already spent by displaying a list of time chip options as 15, 30, and 60 minutes:

The list also contains a Custom option (at the bottom of the list). When you select Custom, a Quick Time popup window displays prompting you to add time spent in minutes.

See Adding and Managing Time Tracker Entries from a Dataform.

76812

Added "Billable" Flag to Time Tracker

A Billable checkbox has been added to Time Tracker.

Users with appropriate access to the new TimeTracker.Billable security entity can flag Time Tracker entries that should be billed by checking the Billable checkbox.

Security entity access options must be assigned by a Global Administrator and are as follows:

  • View - Users can view the Billable flag on their own Time Tracker records.

  • Add - Users can add new records where they can set the Billable flag on their own Time Tracker records.

  • Edit - Users can edit the Billable flag on their own Time Tracker records.

  • Admin - Users can edit the Billable flag on all users' Time Tracker records.

    Note: For a user to see other users' Billable checkboxes, the user must have Admin access to both the TimeTracker and TimeTimeTracker.Billable entities. (This does not apply to Global Administrators as they have Admin rights in Time Tracker by default and do not require security entity assignment.)

See:

76947

Added Time Tracker Interactive Stopwatch Icon

An interactive Time Tracker Stopwatch icon has been added to ClientSpace. The icon displays in the upper right corner of the ClientSpace menu bar when the Enable Time Tracking checkbox is enabled by a Global Administrator on the System Admin User Details window (System Admin > Resources > Users).

When the timer is started on a time tracking record, the Stopwatch icon changes from blue to red.

Note: Click Refresh on your browser to update the Stopwatch icon color.

When the Stopwatch icon is red, you can click it to view a list of the last ten time tracking records associated with your user name. The first record in the list is the record with the active, running timer on it. Click on an item to open the record associated with the time tracking record. From there, you can view time tracking record in the Action Center where you can stop/start a timer or open the time tracking record and make additional changes.

Note: 

  • There can only be one time tracking record with an active, running timer at a time in ClientSpace and it always appears at the top of the list.

  • Starting a timer on a different record will stop the currently running timer.

See Time Tracker Stopwatch

Performance

Case

Enhancement

77439

Improved Workspace Loading Times Related to Cases Widgets

Previously, before a workspace containing a Cases widget (i.e., Client Service Cases, Client Service Cases - Last 30 Days and My Cases) could load, the employees list used to populate the Quick Case Employee , Reporting Employee, and Reporting Contact fields were pre-loaded in the background.

 

Note: Although the My Cases widget does not display a Quick Case icon, it was also affected because it uses the same underlying functionality as the other Cases widgets.

 

If the workspace had a large number of employees, pre-loading the employees list could result in delayed workspace loading. Now, the employees list is no longer pre-loaded. Additionally, the Employee , Reporting Employee, and Reporting Contact fields on the Quick Case window are now typeahead fields that query for the data as you type the first few letters of the employee name.

Technical Enhancements

Case

Enhancement

77563

Refactored Client Module Procedure

The Client module procedure has been refactored to use Dynamic SQL. Additionally, the Decode value instead of the Code value is now used in the Contract Type, Contract, and Sales Region columns of the Client module search dashboard.

Fixes

Case

Issue summary

Resolution

77413

WC Claims Dashboard Displayed Duplicate Rows After Inactivating a Comp Claim Injury Record

Previously, in a scenario where two Comp Claim Injury records got added to the same Comp Claim record and one of them was inactivated, WC Claims Dashboard still showed both rows. They appeared on the dashboard as duplicate record (though they did have different Comp Claim Injure ID numbers). Now, when there are multiple Comp Claim Injury records associated with the same Comp Claim Injury and one is inactivated, the inactivated record no longer displays on the dashboard.
77997

Announcement Body Text Not Displaying

Corrected an issue that occurred in ClientSpace Release 163 that caused the body text of Announcement module announcements to be blank when you clicked on the link in the Action Center to display it.