Release 159 Notes

R159 Sprint: 12/1/2025 to 12/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.

Click to view the R159 release schedule.

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 12/1/2025 to 12/31/2025
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	January 13, 2026
Group 2	Second Tuesday of the month	January 20, 2026
Group 3	Third Tuesday of the month	January 27, 2026

Announcements

Summary	Details
IMAP Deprecation: ClientSpace Email Integration Users	Microsoft is no longer supporting the IMAP integration. Please move all Email Integrations to use Microsoft Graph API going forward. It is a supported, more secure authentication method. Switch to Graph API, in six easy steps: Open the mailbox record (System Admin > Email Integration). Select Office 365 - Graph API in the Type field. Click Apply . Click the Authorize button in the Action Center to re-authenticate. When prompted, enter your credentials. Finally, click Test Connection to test the new connection. If you require assistance, please contact your ClientSpace representative or log an extranet case.

Summary

Details

IMAP Deprecation: ClientSpace Email Integration Users

Microsoft is no longer supporting the IMAP integration. Please move all Email Integrations to use Microsoft Graph API going forward. It is a supported, more secure authentication method.

Switch to Graph API, in six easy steps:

Open the mailbox record (System Admin > Email Integration).
Select Office 365 - Graph API in the Type field.
Click Apply .
Click the Authorize button in the Action Center to re-authenticate.
When prompted, enter your credentials.
Finally, click Test Connection to test the new connection.

If you require assistance, please contact your ClientSpace representative or log an extranet case.

Enhancements

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

ClientSpace Premium

ClientSpace API

Case	Enhancement
53548	Added Organization GET, PATCH, and POST Methods to Version 3.0 of the ClientSpace API The following new Organization methods have been added to the ClientSpace API: GET /api/organization/v3.0/search - Searches for Organizations records. GET /api/organization/v3.0/{id} - Gets Organization data for a specified Organization ID. PATCH /api/organization/v3.0/{id} - Updates an Organization. POST /api/organization/v3.0 - Creates a new Organization. The POST method also includes a hdraction parameter that can be configured to create a new workspace. Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Organization section and then expanding each method.

Case

Enhancement

53548

Added Organization GET, PATCH, and POST Methods to Version 3.0 of the ClientSpace API

The following new Organization methods have been added to the ClientSpace API:

GET /api/organization/v3.0/search - Searches for Organizations records.
GET /api/organization/v3.0/{id} - Gets Organization data for a specified Organization ID.
PATCH /api/organization/v3.0/{id} - Updates an Organization.
POST /api/organization/v3.0 - Creates a new Organization. The POST method also includes a hdraction parameter that can be configured to create a new workspace.

Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Organization section and then expanding each method.

Benefit Plan Manager (BPM)

Case	Enhancement
75841	Improved BPM Batch Card Title Behavior The following changes have been made to the BPM Batch Title behavior in BPM: Previously, when a batch was finalized and approved in BPM, the Benefits Batch card on the BPM Welcome page displayed "Finalized" and a finalized date. Now, the tile displays "Approved" and an approval date. Additionally, when the BPM Batch Title field was left blank on the ClientSpace Benefits Batch dataform, once the batch was finalized and approved in BPM, the Benefits Batch card on the BPM Welcome page displayed "Default Title". Now, if the BPM Batch Title is blank, the tile displays "Approved" and an approval date. See: BPM Option 1: Reviewing, Selecting, and Approving Benefits With Prior Batch History BPM Option 2: Reviewing, Selecting, and Approving Benefits - No Prior Batch History
75108	Improved Plan Filtering on Benefits Summary Previously, the Benefit Plan Manager (BPM) Benefits Summary tab "Filters" section contained an Include New Plans drop-down field which defaulted to No. When set to No, only plans in "Selected" status were included in the Benefits Summary tab calculations on the Base and Supplemental tab grids. When set to Yes, plans in "New" status displayed and they were included in the grid calculations and totals. This created the following issues for users: When all base plans were in "New" status, the Base tab was hidden. You had to set Include New Plans to Yes to see the plans. When all supplemental plans were in "New" status, the Supplemental tab was hidden. You had to set Include New Plans to Yes to see the plans. Now, the following changes have been made: The Include New Plans drop-down field has been removed. All Base plans in "Selected" or "New" status are visible on the Base tab by default. All Supplemental plans in "Selected" or "New" status are visible on the Supplemental tab by default. If a plan is in "New" status, dashes display in place of calculations in the Base or Supplemental tab grid. Plans in "New" status are also not reflected in the Totals calculations. Note: Once a plan is placed in "Selected" status, it is automatically added to grid calculations and totals. The following additional changes were made: Previously, "Current (Yearly)" and "Renewal (Yearly)" sections displayed on the Supplemental tab for RFP or Prospect batches. Now, a single "Benefits Batch" header displays on the Supplemental tab for RFP or Prospect batches. Previously, the Group drop-down list in the Benefits Summary tab only included the group when there was at least one plan in "Selected" status within that group. If all plans within a group were in "New" status, the group was not included in the drop-down list. Now, all groups with a plan in "New" or "Selected" status are included in the list. See BPM Option 1: Reviewing, Selecting, and Approving Benefits With Prior Batch History BPM Option 2: Reviewing, Selecting, and Approving Benefits - No Prior Batch History
75728	Updated "BPM Access Information" Field to Display Newest Entries First Previously, the BPM Access Information field on located on the Benefits Batch form in ClientSpace displayed the oldest entries first. Now, the entries are ordered from the most recent entries to the oldest entries based on the login time stamp.

Case

Enhancement

75841

Improved BPM Batch Card Title Behavior

The following changes have been made to the BPM Batch Title behavior in BPM:

Previously, when a batch was finalized and approved in BPM, the Benefits Batch card on the BPM Welcome page displayed "Finalized" and a finalized date. Now, the tile displays "Approved" and an approval date.
Additionally, when the BPM Batch Title field was left blank on the ClientSpace Benefits Batch dataform, once the batch was finalized and approved in BPM, the Benefits Batch card on the BPM Welcome page displayed "Default Title". Now, if the BPM Batch Title is blank, the tile displays "Approved" and an approval date.

See:

75108

Improved Plan Filtering on Benefits Summary

Previously, the Benefit Plan Manager (BPM) Benefits Summary tab "Filters" section contained an Include New Plans drop-down field which defaulted to No. When set to No, only plans in "Selected" status were included in the Benefits Summary tab calculations on the Base and Supplemental tab grids. When set to Yes, plans in "New" status displayed and they were included in the grid calculations and totals.

This created the following issues for users:

When all base plans were in "New" status, the Base tab was hidden. You had to set Include New Plans to Yes to see the plans.
When all supplemental plans were in "New" status, the Supplemental tab was hidden. You had to set Include New Plans to Yes to see the plans.

Now, the following changes have been made:

The Include New Plans drop-down field has been removed.
All Base plans in "Selected" or "New" status are visible on the Base tab by default.
All Supplemental plans in "Selected" or "New" status are visible on the Supplemental tab by default.
If a plan is in "New" status, dashes display in place of calculations in the Base or Supplemental tab grid. Plans in "New" status are also not reflected in the Totals calculations.

Note: Once a plan is placed in "Selected" status, it is automatically added to grid calculations and totals.

The following additional changes were made:

Previously, "Current (Yearly)" and "Renewal (Yearly)" sections displayed on the Supplemental tab for RFP or Prospect batches. Now, a single "Benefits Batch" header displays on the Supplemental tab for RFP or Prospect batches.
Previously, the Group drop-down list in the Benefits Summary tab only included the group when there was at least one plan in "Selected" status within that group. If all plans within a group were in "New" status, the group was not included in the drop-down list. Now, all groups with a plan in "New" or "Selected" status are included in the list.

See

75728

Updated "BPM Access Information" Field to Display Newest Entries First

Previously, the BPM Access Information field on located on the Benefits Batch form in ClientSpace displayed the oldest entries first. Now, the entries are ordered from the most recent entries to the oldest entries based on the login time stamp.

Other ClientSpace Premium

Case	Enhancement
75208	Benefit Export API: Premium Risk Factors Export to Prism Regardless of Rate Group Type The ExportOfferedPlansToPrism business rule has been enhanced to now export premium risk factors regardless of Rate Group Type. The following changes were made: If the Rate Group assigned to the Offered Benefit Plan (OBP) is a percentage, the Risk Factor is sent to PrismHR as a percentage. If the Rate Group assigned to the OBP is set to Manual and a risk factor is set on the OBP, the Risk Factor is sent to PrismHR as a number. Note: All other previous logic remains in effect. The risk factor is still calculated the same and the Premium Risk Factor Date is still sent to PrismHR as the Benefit Plan Effective Date. See Configuring Benefit Plan API Business Rules.
75285	Completed HCM Client Import Merge Template Previously in ClientSpace Release 158, we completed Phase 1 of the HCM Client Import project by adding three HCM Implementation dataforms to hold client implementation details for transfer to HCM. (See Case # 73752.) Now, the final phase of the project is complete. You can run an Excel merge to export client implementation details from ClientSpace to import into HCM and create client records (System Admin > Outputs > Merges). A link to run the merge has also been added to the HCM Implementation dataform under Action Center > Reports. The link is named HCM Client Export. Clicking it generates the merge (also named HCM Client Export) and deposits it in the Windows Downloads folder. Note: The HCM Implementation dataforms are in the Implementation group of the workspace. Currently, we can only include one worker's compensation form and one invoice per HCM implementation record in the merge. The most recent invoice and worker's compensation records for the client are used. See HCM Client Import Merge.

Case

Enhancement

75208

Benefit Export API: Premium Risk Factors Export to Prism Regardless of Rate Group Type

The ExportOfferedPlansToPrism business rule has been enhanced to now export premium risk factors regardless of Rate Group Type. The following changes were made:

If the Rate Group assigned to the Offered Benefit Plan (OBP) is a percentage, the Risk Factor is sent to PrismHR as a percentage.
If the Rate Group assigned to the OBP is set to Manual and a risk factor is set on the OBP, the Risk Factor is sent to PrismHR as a number.

Note: All other previous logic remains in effect. The risk factor is still calculated the same and the Premium Risk Factor Date is still sent to PrismHR as the Benefit Plan Effective Date.

See Configuring Benefit Plan API Business Rules.

75285

Completed HCM Client Import Merge Template

Previously in ClientSpace Release 158, we completed Phase 1 of the HCM Client Import project by adding three HCM Implementation dataforms to hold client implementation details for transfer to HCM. (See Case # 73752.)

Now, the final phase of the project is complete. You can run an Excel merge to export client implementation details from ClientSpace to import into HCM and create client records (System Admin > Outputs > Merges).

A link to run the merge has also been added to the HCM Implementation dataform under Action Center > Reports. The link is named HCM Client Export. Clicking it generates the merge (also named HCM Client Export) and deposits it in the Windows Downloads folder.

Note:

The HCM Implementation dataforms are in the Implementation group of the workspace.
Currently, we can only include one worker's compensation form and one invoice per HCM implementation record in the merge. The most recent invoice and worker's compensation records for the client are used.

See HCM Client Import Merge.

Advanced Administration and System Administration

Case	Enhancement
74672	Added Global Search Configuration Note: This feature is currently in a beta test period. To request this feature, please contact your ClientSpace representative or log an extranet case. The following configuration options for the Global Search feature (see related Case# 74942) have been added for Developer users: Add indexed fields: For each dataform you want to include in the Global Search, flag the dataform fields you want to make searchable by including them in the Global Search index. This is done by clicking the Index checkbox next to the fields you want to include in Global Search (System Admin > Advanced > Dataform Admin > Open Dataform > Action Center > Fields). Note: If a field cannot be indexed, the Index checkbox appears dimmed (i.e., "grayed out"). The index changes take effect after the Populate Search Index scheduled process runs. Important - Only Active records are indexed. Configure Global Search Results: For each dataform you want to include in the Global Search, also specify the data elements to display in the Global Search results on system table forms or PEO layer dataforms beginning with "gen_". (See ClientSpace Layers and Naming Conventions for more information on ClientSpace Layers and a list of common PEO Layer dataforms.) Note: Global Search Results configuration of CORE layer forms such as Tasks, Activities, and Organizations is pre-configured for you. Global Search Results Configuration for PEO forms uses Replace Fields to pull the data values from the record and display them in the search results. See Global Search Configuration.
75436	Added Survey "Unsubscribe" Feature and Made Survey Template Selection Required Survey recipients are now allowed to either unsubscribe from the current survey or from all surveys by clicking a link in the survey body which is automatically appended to the end of the survey email similar to the following: When the link is clicked a "Manage Your Survey Preferences" window displays which allows the user to unsubscribe from the current survey or from all ClientSpace surveys: To track unsubscribed users, two new recipient tables have been created: Unsubscribe by Design: This table stores "unsubscribe" details when users unsubscribe from a specific survey. The survey from which they are unsubscribing is listed in the table by the Survey Design value configured on the associated survey email template. Other details stored in the table include the recipient email, whether the recipient completed the survey, the last time the survey was sent to the recipient and "unsubscribe" status as Y. Note: Future plans are underway to add a ClientSpace dashboard listing the unsubscribed users by email and the survey design(s) from which they are unsubscribed. Unsubscribe All: This table stores "unsubscribe" details when users unsubscribe from all surveys. It stores the "unsubscribe from all" status as Y, the recipient email and the date/time they unsubscribed. Note: Future plans are underway to add a ClientSpace dashboard listing the users by email who have unsubscribed from all ClientSpace surveys. An additional change was made to make the Survey Design field on the Step 2: Content tab of the survey email template (System Admin > Email Templates) required when the email template Type is set to survey. See Configuring a Dataform Survey Email Template.
76018	Updated Reporting Profile Configuration to Allow Specifying a Sigma "Report Center Administrator" In preparation for the Business Intelligence model's transition from the Izenda reporting system to the Sigma Report Center reporting system, we have added a new Report Center Administrator profile and a new Report Center Administrator checkbox to the Reporting Profile configuration window (System Admin > Security > Reporting Profile). The Report Center Administrator checkbox is checked by default on the Report Center Administrator profile as shown in the example below: The Report Center Administrator checkbox is unchecked by default on all other pre-existing Reporting Profiles. This gives a user with Developer access the flexibility of assigning Report Center administrator access to an existing profile. Note: The Report Center Administrator field is visible but dimmed and inaccessible (i.e., grayed) if you are not logged in as a Developer user. When Report Center Administrator is checked on a profile, any existing Tables and Views (on the Action Center of the Reporting Profile record) are copied from the existing Administrator Reporting Profile to this profile. Additional changes include: A Report Center Admin column was also added to the Reporting Profile search dashboard. "Izenda" now appears in parentheses next to the pre-existing Allow Report Creation and Allow All Forms and Views checkboxes to clearly denote that these fields are for Izenda Reporting Profile configuration only. See Configuring Security in Business Intelligence Reporting.

Case

Enhancement

74672

Added Global Search Configuration

Note: This feature is currently in a beta test period. To request this feature, please contact your ClientSpace representative or log an extranet case.

The following configuration options for the Global Search feature (see related Case# 74942) have been added for Developer users:

Add indexed fields: For each dataform you want to include in the Global Search, flag the dataform fields you want to make searchable by including them in the Global Search index. This is done by clicking the Index checkbox next to the fields you want to include in Global Search (System Admin > Advanced > Dataform Admin > Open Dataform > Action Center > Fields).

Note:
- If a field cannot be indexed, the Index checkbox appears dimmed (i.e., "grayed out").
- The index changes take effect after the Populate Search Index scheduled process runs.
- Important - Only Active records are indexed.
Configure Global Search Results: For each dataform you want to include in the Global Search, also specify the data elements to display in the Global Search results on system table forms or PEO layer dataforms beginning with "gen_". (See ClientSpace Layers and Naming Conventions for more information on ClientSpace Layers and a list of common PEO Layer dataforms.)

Note: Global Search Results configuration of CORE layer forms such as Tasks, Activities, and Organizations is pre-configured for you. Global Search Results Configuration for PEO forms uses Replace Fields to pull the data values from the record and display them in the search results.

See Global Search Configuration.

75436

Added Survey "Unsubscribe" Feature and Made Survey Template Selection Required

Survey recipients are now allowed to either unsubscribe from the current survey or from all surveys by clicking a link in the survey body which is automatically appended to the end of the survey email similar to the following:

When the link is clicked a "Manage Your Survey Preferences" window displays which allows the user to unsubscribe from the current survey or from all ClientSpace surveys:

To track unsubscribed users, two new recipient tables have been created:

Unsubscribe by Design: This table stores "unsubscribe" details when users unsubscribe from a specific survey. The survey from which they are unsubscribing is listed in the table by the Survey Design value configured on the associated survey email template. Other details stored in the table include the recipient email, whether the recipient completed the survey, the last time the survey was sent to the recipient and "unsubscribe" status as Y.

Note: Future plans are underway to add a ClientSpace dashboard listing the unsubscribed users by email and the survey design(s) from which they are unsubscribed.
Unsubscribe All: This table stores "unsubscribe" details when users unsubscribe from all surveys. It stores the "unsubscribe from all" status as Y, the recipient email and the date/time they unsubscribed.

Note: Future plans are underway to add a ClientSpace dashboard listing the users by email who have unsubscribed from all ClientSpace surveys.

An additional change was made to make the Survey Design field on the Step 2: Content tab of the survey email template (System Admin > Email Templates) required when the email template Type is set to survey.

See Configuring a Dataform Survey Email Template.

76018

Updated Reporting Profile Configuration to Allow Specifying a Sigma "Report Center Administrator"

In preparation for the Business Intelligence model's transition from the Izenda reporting system to the Sigma Report Center reporting system, we have added a new Report Center Administrator profile and a new Report Center Administrator checkbox to the Reporting Profile configuration window (System Admin > Security > Reporting Profile).

The Report Center Administrator checkbox is checked by default on the Report Center Administrator profile as shown in the example below:

The Report Center Administrator checkbox is unchecked by default on all other pre-existing Reporting Profiles. This gives a user with Developer access the flexibility of assigning Report Center administrator access to an existing profile.

Note: The Report Center Administrator field is visible but dimmed and inaccessible (i.e., grayed) if you are not logged in as a Developer user.

When Report Center Administrator is checked on a profile, any existing Tables and Views (on the Action Center of the Reporting Profile record) are copied from the existing Administrator Reporting Profile to this profile.

Additional changes include:

A Report Center Admin column was also added to the Reporting Profile search dashboard.
"Izenda" now appears in parentheses next to the pre-existing Allow Report Creation and Allow All Forms and Views checkboxes to clearly denote that these fields are for Izenda Reporting Profile configuration only.

See Configuring Security in Business Intelligence Reporting.

General User Enhancements

Case

Enhancement

74942

Added Global Search Bar

Note: The Global Search feature is currently in a beta test period. To request this feature, please contact your ClientSpace representative or log an extranet case.

When the Global Search bar is enabled, it appears on the Modules bar:

Once configured, it is always visible, allowing you to search the ClientSpace system by keyword or phrase from one location for related cases, tasks, activities, attachments and more. If results are found, they display in a drop-down list:

Click an item in the list to open the associated record.

See Searching in ClientSpaceand Global Search.

Also see related Case# 74672 (Global Search Configuration).

75740

Global Search Results Now Include Prepended CRM Form Type Abbreviation

Note: The Global Search feature is currently in a beta test period. To request this feature, please contact your ClientSpace representative or log an extranet case.

A form type abbreviation is now being prepended to Global Search results for CORE (i.e., CRM) forms to help users identify results.

The following values are prepended:

CRM Form Type	Prepended Abbreviation
Organizations	Org
Activities	Act
Contact	Cont
Workspace	WS

Note: CORE forms, also referred to as CRM forms, are system-level forms that comprise the foundation of ClientSpace basic Customer Relationship Management (CRM) functionality. Unlike PEO dataforms, they cannot be modified by a System administrator. CORE forms include: Activities, Organization, Contact, Tasks, Calendar Event, Workspace and Users.

See Global Search

Fixes

Case	Issue summary	Resolution
75621	BPM PDF External Report Links Were Not Displaying in BPM	Previously, PDF custom merge (i.e., external report) links did not display in BPM due to BPM requiring a type of "Merge" instead of "PdfMerge". This issue has been corrected. PDF custom merge link types of "Merge" or "PdfMerge" are now accepted and will be displayed in the Links section of BPM.
76062	GraphAPI Email Integration Was Not Ignoring ClientSpace Emails	Previously, the GraphAPI Email Integration processed emails sourced from ClientSpace (i.e., emails with the IsFromClientSpace flag set in the email header). These emails should not be processed as they could result in case generation looping. Now, the GraphAPI email integration honors the IsFromClientSpace flag. If the flag is set, the email is marked as "Read" and not processed.