Release 158 Notes

R158 Sprint: 11/3/2025 to 11/30/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 11/3/2025 to 11/30/2025

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 First Thursday of the month December 4, 2025
Group 2 Second Tuesday of the month December 9, 2025
Group 3 Third Tuesday of the month December 16, 2025

Announcements

Summary

Details
IMAP Deprecation: ClientSpace Email Integration Users

IMAP is being deprecated by Microsoft. Although there is no official cutoff date yet, we recommend switching to Microsoft Graph API, a supported and more secure authentication method.

Switch to Graph API, in six easy steps: 

  1. Open the mailbox record (System Admin > Email Integration).

  2. Select Office 365 - Graph API in the Type field.

  3. Click Apply .

  4. Click the Authorize button in the Action Center to re-authenticate.

  5. When prompted, enter your credentials.

  6. Finally, click Test Connection to test the new connection.

If you require assistance, please contact your ClientSpace representative or log an extranet case.
Report Center Coming Soon!

We are excited to let you know that we are preparing to roll out Report Center! To help ensure a smooth transition from Izenda to Report Center, please take a moment to archive any unused reports.

To get up to speed with Report Center, we encourage you to attend an upcoming Report Center Training Sessions/Conferences or watch the Sigma "Jump Start" Training videos.

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

72775

Related Companies Link No Longer Displays on Signature Page When No Related Companies are present on Welcome Page

Previously, when there were no related companies and therefore no related companies link (i.e., Click HERE to see the list) to display on the BPM Welcome page, an "Affiliated" section containing a Click HERE to see the list link still displayed on Signature/Selection Summary page. Now, when there are no related companies to display on the Welcome page, the "Affiliated" section and related companies link no longer display on the Signature/Selection Summary.

74502

Added a "Save" Warning to Cafeteria Contribution Amount and Waiting Period Fields

Previously, if you edited a Cafeteria Contribution Amount or Waiting Period field (Manage Benefits > Benefits Summary > Group Summary > Summary) without clicking the Save button in the section, you could navigate to another tab without being prompted to save your changes. Now, if you attempt to navigate away from Cafeteria Contribution Amount or Waiting Period without saving changes, the following message displays:

"You have unsaved changes in the Cafeteria Plan and/or Waiting Period sections. Do you want to continue?"

If you click Cancel, the message clears and you can click Save to apply changes. If you click Continue, you navigate to the selected tab and the pending changes are lost.
74787

External Users Can Navigate Between Multiple Clients in BPM

External users can now navigate between multiple clients in BPM. The user can log in as any client where they are added as a BPM Contact on the Benefits Batch (by using the credentials received in the BPM notification email for one of the client batches). Once logged in, they can click the drop-down list in BPM on the left pane of the Welcome Page and navigate between client batches.

Clicking a batch in the list refreshes the Welcome page and shows the Benefits Batch card for the selected client.

Note: 

  • The list includes all batches where the external user is added to the Benefits Batch as a BPM Contact. The batches do not have to be related (i.e., in a parent to child or child to parent relationship) to appear in the list.

  • Assigned access permissions (i.e., Edit or View Only rights) on the BPM Contact record are evaluated and respected for each client batch in the list.

  • The batches must be Active and in Client Review status to appear in the list.

  • Only users who log in with an external link can see the drop-down list on the left pane. Internal users who click the Internal BPM Access link on the Benefits Batch will not see it.

  • The list is only available on the BPM Welcome page.

See Adding and Editing BPM Additional Contacts and Multi-Client Access

 

Video

Also view the video Using BPM - Full Walkthrough.

75537

Added Benefits Batch Types Metadata to Allow BPM Login Method Configuration for Custom Batch Types

If you have custom batch types, you can now use the Benefits Batch Types Metadata dataform to specify a BPM Login Type of ID or Client Number for external users by Benefits Batch Type . Also, an additional change was made to allow you to use BPM Login Type as a condition on BPM email templates to specify the correct email template for custom batch types (i.e.,  BPM Prospect for the ID login method or BPMLoginEmail for the Client Number login method).

 

Note: If you do not have custom batch types, you do not need to configure Benefits Batch Types metadata.

See Configuring the BPM Login Method for Custom Batch Types and Customizing BPM Login Notification Email Templates

Other ClientSpace Premium

Case

Enhancement
73284

Expired, Cancelled, Inactive Plans No Longer Roll Over for Renewal

Previously, if Offered Benefit Plans (OBPs) within an Active Benefits Batch were cancelled, expired or made Inactive, upon batch renewal, new OBPs were created for these plans. Now, when triggering the Renew workflow on a Benefits Batch, any Expired, Cancelled and Inactive plans are excluded from the Pending (i.e., renewing) batch. Only valid Active plans are carried over with renewed batches.

SeeRenewing a Benefits Batch.

73566

Added Max Benefit Plans Management to ClientSpace and BPM

You can now manage the maximum number of benefit plans which can be marked Selected per benefit plan category on a plan in ClientSpace and BPM.

 

Note: This business rule method can be configured in both ClientSpace and (Benefit Plan Manager) BPM. If configuring a rule using this method for both BPM and ClientSpace, be certain to add BPM (Benefit Plan Manager) to the Execution Pipeline of the business rule configuration.

 

The following changes were made to support this enhancement:

  • Added Max Number of Plans field: A new Max Number of Plans field has been added to the Benefits Plan Category Metadata form.

     

    Note: This metadata form is attached to the Benefit Plan Category Lookup Group Details form (System Admin > Lookups > Manage Groups).

     

    Edit the Benefit Plan Category Lookup Details form for each benefit plan category (i.e., Health, Dental, Vision, etc.) where you want to specify a maximum of number of plans which can be added:

  • Added two new business rule methods: Two new business rule methods, HE_RequiredPlanMax and SE_RequiredPlanMax, were added to enforce the Max Number of Plans configurations. When the rule triggers and the Max Number of Plans is exceeded for a benefit plan category, the following message is displayed: 

    "You've exceeded the '[Benefit Plan Category]' limit (X allowed, X selected); please adjust your plans."

    As HE_RequiredPlanMax is a hard error message method, when it is triggered, a user cannot proceed with saving until they adjust the plans, unless the Override Max Plans field is set to Yes on the Benefits Batch. As SE_RequiredPlanMax is a soft error message method, the user can click Save Anyway to save the current plan configurations as shown in the ClientSpace example below:

  • Added Override Max Plans field: An Override Max Plans lookup field has been added to the Benefits Batch dataform.

    This allows you to override the Max Number of Plans setting(s) on a "per batch" basis when you are using the HE_RequiredPlanMax hard error message method. Valid lookup values are Yes, No or blank. When set to Yes, users can add unlimited plans per category. When set to No or blank, any Max Number of Plans values set for each benefit plan category are evaluated upon Apply or Save and the HE_RequiredPlanMax hard error message is triggered if any of the configured values are exceeded.

See Business Rule Methods and Adding a Benefits Batch.

73752

Added Support for HCM Client Import - Phase 1

Changes are underway to complete an HCM Client Import that will allow you to enter HCM client data and transfer the data to HCM to create a client record.

Note: This is a phased project which will be completed in a future release.

 

The following changes were made in ClientSpace R158:

  • Added three new dataforms to System Admin > Advanced > Dataform Admin:

    • HCM Implementation: Main form that contains the bulk of the HCM Client fields.

    • HCM Implementation - Invoice Line Items: Secondary form that links from the HCM Implementation form.

    • HCM Implementation - Workers Comp:  Secondary form that links from the HCM Implementation form.

  • Added multiple new lookups and fields to populate the dataforms.

  • Added two custom links on the HCM Implementation form to the HCM Implementation - Invoice Line Items and HCM Implementation - Workers Comp forms.

  • Added a field display rule that hides the Not HRO field when the CSA Type field is set to "HRO".

73753

Client Benefit Plans Export Now Uses "Stop Date" to Determine Terminated Plans

Previously, when an Offered Benefit Plan (OBP) was terminated in one Benefit Group but remained Active in other Benefit Groups, it was possible for plans that should have been Active to be incorrectly terminated. Although the Client Benefit Plans Export merge organizes OBPs by Benefit Group and includes the "TERM" (i.e., terminated) line for the OBP within the proper benefit group, the Prism import process does not process the OBPs by Benefit Group. It only reads the last line for each OBP and if the last line was "TERM", the same plan in other Benefit Groups could also be terminated.

 

To correct this issue, the following changes were made to the Client Benefit Plans Export Merge:

  • When multiple Benefit Groups are Active:

    • If at least one benefit group has the offered benefit plan marked as Active, include only the active rows from Column E.

    • Also, populate Column G [Stop.Date] with the current BenefitsBatch.ExpirationDate.

    • We are not sending Terminated statuses anymore but when these are terminated, we use the Prior Batch expiration date if available, else the current batch expiration date as [Stop.Date].

See Client Benefit Plans Export.
75498

Added Plan Setup Fields to OBP Mass Update

An Update Plan Setup Details option has been added to the OBP Mass Update feature. When clicked, it displays multiple fields from the Setup Details fieldset of the Offered Benefit Plan record, allowing you to update plan setup details on all selected OBPs.

See Using Mass Update from Benefits Batch OBPs Search

74720

Added Hard Error Business Rule to Prevent Data Entry of Employer Contribution Percentages over 100% on OBPs

A new hard error business rule named Amount over 100 Not allowed for EO, ES, EC, EF, EK has been added (System Admin > Advanced > Manage Business Rules). The rule uses the HE_DisallowPercentOver100 business rule method.

 

Note: This rule is preconfigured and Active by default for both ClientSpace and Benefit Plan Manager (BPM).

 

The rule prevents users from entering contribution percentages over 100% on an Offered Benefit Plan (OBP) in the EO%, ES%, EC%, EF%, EK% or Dependent Contrib% fields located in the Employer Contributions (%) fieldset. If you enter a value greater than 100% and click Apply or Save, the following error message displays similar to the ClientSpace example below for each incorrect entry :

Note: The message may vary from the example shown above if the Error Message Override field is used in the business rule configuration to change the default message text.

See Business Rule Methods.

Advanced Administration and System Administration

Case

Enhancement

71973

Added Ability to Schedule Surveys

You can now send scheduled surveys triggered from a dataform. To accomplish this, the following changes were made:

  • A "Survey" option has been added Type field Scheduled Email Templates configuration.

  • The Generate Scheduled Email Templates schedule process has been updated to include scheduled surveys.

Additionally, to improve searching for existing scheduled Email Templates and Workflow Channels, this case included an additional change to the Email Templates and Workflow Channels dashboards. "Scheduled" has been removed as an option from the Type filter in the More search. A new Timing filter has been added to More search which includes "Scheduled" and "Real Time" options.

 

See Configuring Scheduled Email Templates and Configuring a Dataform Survey Email Template.
74708

Improved Work Items Display of Workflow Items, Workflow Channels and Email Templates

The display of Work Items in the Work Center panel for Workflow Channels, Workflow Items, and Email Templates has been updated to match the window header details. This makes it easy to differentiate between multiple items, particularly saved items since the headers of saved records show identifiers such as the Workflow Channel ID, Workflow Item ID and Email Template ID as shown in the example below:

General User Enhancements

Case

Enhancement
69936

Stopped the Department Code, Expired Status or OOO from Displaying Next to UserID on Replace Fields

The Department Code, Out of Office status (OOO) or terminated status (Expired) will no longer display next to user datatype fields on Email Template and Workflow Channel replace fields.

Note: These details still display where useful throughout ClientSpace, such as in user datatype field drop-down lists.

74579

Added Case Discussions Module/Dashboard

A Case Discussions module has been added for managing Case Discussions. The Case Discussions module is a dashboard which auto-filters upon login to display discussions for cases assigned to you (i.e., the currently logged in user). You can remove the filter to see all case discussions.

 

Dashboard highlights:

  • The dashboard displays seven (7) columns by default: Workspace Name, Case#, Status, Body, From(email), To (email), and Date.

  • Clicking a Workspace link opens the workspace related to the case.

  • Click a Case# link opens the case.

  • Click Open on a line item in the grid to open the discussion thread of the most recent discussion message associated with the case.

  • Two additional hidden columns, Category and Type, can be displayed by clicking the vertical three dot menu (i.e., kebab) icon next to any displayed column, selecting Columns and then selecting the column.

  • Quick Search and More search options allow you to search and filter case discussions.

See Case Discussion Dashboard.

74854

Standardized Add and Edit Toolbar Buttons on Cases 2.0 Dashboard, Quick Case and Quick Task

The Cases 2.0 Dashboard, Quick Case and Quick Task Add and Edit toolbar buttons have been standardized to match the buttons for similar interfaces throughout the system:

  • On the Cases 2.0 dashboard, the image icons for Add and Edit have been replaced with text label buttons:

  • On the Quick Case and Quick Task forms, the Edit/Go to Full Form icon has been replaced with a standard "Jump/Open" icon:  

See:

75392

Updated PrismHR Favicon Icon for ClientSpace

The PrismHR Favicon icon used on ClientSpace browser tabs has been changed to a transparent icon. The previous icon had a white background.

Technical Enhancements

Case

Enhancement

75739

Updated HCM Integration "peo_hcmapi_case_search" Stored Procedure Parameter Name

Previously, the HCM integration "peo_hcmapi_case_search" stored procedure used an input parameter of @PEOID which was not the correct case. This caused HCM Support Center Cases to not show up in the user's Cases dashboard view after creating a new case (even though the case had been created successfully and showed up in ClientSpace.) To correct the issue of cases not being returned, the parameter name in the stored procedure has now been updated to @PeoId.

Fixes

Case

Issue summary

Resolution
73412

Edited Tasks Did Not Respect More Search Criteria in Task Manager

Previously, if you edited a task so that it no longer fit the current More Search settings, that task continued to display in the Task Manager grid. Now, when you edit a task, if the edit causes the task to no longer match the More Search criteria, the task does not display in the Task Manager.

75498

Corrected Global Search Input Field Focus Issue

Previously, if you used a special character in the Global Search field, the field would lose focus. The user had to click in the field to place the cursor back in the field. This issue has been corrected.

75426

SetClientPlanCode Business Rule Method Did Not Update OBP When Carrier Plan Code Changed

Previously, the SetClientPlanCode business rule method correctly set the Client Plan Code based on the parent Benefit Plan when adding a new Offered Benefit Plan (OBP). However, if the Client Plan Code was changed on the parent Benefit Plan, the SetClientPlanCode business rule method did not update the Client Plan Code of existing OBPs. Now, if the Client Plan Code is changed on the parent plan, it is also updated on the OBP by the SetClientPlanCode business rule method.

75650

Salesforce Integration: New Contacts Did Orphaned from Account ID(Organization)

Previously, when the Salesforce integration exported new ClientSpace contacts to Salesforce, the Account ID (i.e., ClientSpace Organization ID) was not being associated with the contact record which caused it to be orphaned. Now, when both the createnewsfcontact and createnewsfaccount Salesforce parameters are set to 1 in the Salesforce Integration's API Configuration, the new Salesforce contact record is correctly linked to an Account ID.

See Additional Salesforce Parameters.