Release 161 Notes

R161 Sprint: 2/2/2026 to 2/27/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.

Click to view the R161 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 2/2/2026 to 2/27/2026
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	Second Tuesday of the month	March 10, 2026
Group 2	Third Tuesday of the month	March 17, 2026
Group 3	Fourth Tuesday of the month	March 24, 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
75478	Added Ability to Send Emails to "Additional BPM Contacts" When Benefits Batch is the Triggering Form The peo_benefitsbatch_emailtemplate_recipient_v2_proc Address Stored Procedure has been updated to support sending Email Template emails to all active BPM contacts listed on the Benefits Batch > Additional BPM Contacts dataform when the Email Template Initial tab Triggering Form is set to Benefits Batch. Define recipients on the Email Template Addresses tab using Address Source Procedure under Source and AdditionalBPMContacts under Address. See Adding and Editing BPM Additional Contacts.
75529	Added HE_PreventBPMDuplicate Business Rule on Benefits Batch to Prevent Duplicate BPM Contacts A business rule (System Admin > Advanced > Manage Business Rules) using the new _HE_PreventBPMDuplicate business rule method has been added on the BPM Contacts table. The rule, named Prevent BPM Duplicate Records From Add BPM, prevents duplicate BPM contact records from being added to the Renewal Client Contact field or Additional BPM Contacts window of the Benefits Batch. It searches all Active and Inactive contact records for the PKID, Email or Mobile number of the record being added or updated. If one or more duplicate values exist, the following error message displays: "A BPM Contact record already exists for this user. Please locate and update the existing BPM Contact record instead." Note: The rule is Active by default. See Configuring BPM Business Rules.
75667	Removed the Ability to Edit the Renewal Client Contact on the Additional BPM Contacts Form Previously, you could change the BPM Contact field on the Additional BPM Contacts form for the Renewal Client Contact. This caused there to no longer be a corresponding BPM Contact record for the Renewal Client Contact and resulted in the Renewal Client Contact losing access to the renewal batch in BPM. Now, if a contact is specified as the Renewal Client Contact on the Benefits Batch, the BPM Contact field on the Additional BPM Contacts form cannot be edited. It appears dimmed or "grayed out". Note: If you want to change the Renewal Client Contact, please pick a new contact in the Renewal Client Contact field and allow ClientSpace to make the appropriate updates to the Additional BPM Contacts form, such as: Adding a new Additional BPM Contacts record for the new Renewal Client Contact and granting default Edit access. Or, if the new Renewal Client Contact was previously added to the Additional BPM Contacts form with View Only access, updating the existing record to Edit access. See Adding and Editing BPM Additional Contacts and Adding a Benefits Batch.
75679	Added Renewal Client Contact Email Validation on the Benefits Batch for BPM Previously, you could select a Renewal Client Contact record on the Benefits Batch where the contact record had no email address. Now, the email address is required when selecting the Renewal Client Contact. A new business rule on the Benefits Batch dataform, Renewal Contact Has Email, has been added which uses the HE_RenewalContactEmail. If you attempt to select a contact record with no email address, the rule triggers the following hard error message: "A required email address for the Renewal Client Contact is missing. You must add an email before continuing." Note: Although either an email address or mobile phone number can be used to log in to BPM, an email address is required to receive the initial BPM email notification. The rule is Active by default for organizations configured to use BPM and InActive for everyone else. The default execution for the rule is 40. It must be configured to execute before the Validate Contact Has Phone Or Email rule used to validate Additional BPM Contacts. See Configuring BPM Business Rules and Adding a Benefits Batch.
76731	Added Ability to Hide or Rename "Domestic Partner" Column on BPM Selection Summary/Signature Page In the prior release (ClientSpace Release 160), the Domestic Partner (EK) coverage level was added to Benefit Plan Manager (BPM). The Domestic Partner column always displayed on the BPM Selection Summary/Signature page in the "Selection Summary" section. Now, settings have been added to the BPM Config dataform to allow you to hide the column on the Selection Summary/Signature page by setting Do Not Show EK to Yes. Or, if you are using EK for a coverage level other than Domestic Partner, there is now a BPM Rename EK setting on the BPM Config dataform that allows you rename the column to match the name you gave to the coverage level on the Benefits Plan. Note: If you hide or rename the Domestic Partner coverage level on the Benefits Plan (from either the Admin Workspace or the client workspace), this only affects (BPM) Group Summary and Plan Comparison grids. (See Configuring the Benefits Plan Prism Coverage Levels Fieldset.) If you want to hide or rename the Domestic Partner column on the BPM Selection Summary/Signature page, you must also edit the BPM Config dataform as indicated in this release note. See BPM Site Configuration.

Other ClientSpace Premium

Case	Enhancement
74011	Added Ability to Suppress Benefit Plans from Benefit Plan Export API and Benefit Rules Export Merge If you want to prevent an Offered Benefits Plan (OBP) from inclusion in a Benefit Plan export or Benefit Rules export, you can now select the Suppress from Entire Presentation option in the Suppress from Presentation field of the associated Benefit Plan record to keep the plan from being included. Note: Prior Suppress from Entire Presentation functionality still works. The option still excludes plan from all locations in the Benefit Plan Manager (BPM) and from the Benefits Renewal Workbook merge. A suppressed plan will still be listed as an associated OBP on the Benefits Batch when you click the Associated OBPs link in the Action Center of the Benefits Batch. The plan is suppressed even if the associated OBP on the Benefits Batch is marked "Selected". See Selecting, Rejecting or Suppressing Benefit Plans to Export and Benefit Batch Billing Rules Export.
75736	Updated Apply Plan Group "All Classes" to "All Benefit Groups" The name of the All Classes field on the Apply Plan Group window has been changed to All Benefit Groups. See Setting Up and Using the "Apply Plan Group" Function.
75802	Added "Exempt Take on EEs" Field to OBP and Updated "Mass Update OBPs" and "Billing Rules Export" Functions to Support the New Field An Exempt Take on EEs checkbox has been added to the Offered Benefits Plan (OBP) dataform in the Setup Details fieldset. The ClientSpace Exempt Take on EEs field value is now exportable to PrismHR using the Billing Rules Export function on the Benefits Batch. The field corresponds to a PrismHR field of the same name. When checked, it is used to indicate that "take on" employees (i.e., employees who are being added to the system as part of a migration to PEO management and who are not "new" employees) enrolling in this plan are exempt from any waiting period requirements identified on the plan's Benefit Group record. The Mass Update OBPs feature can now be used to set the Exempt Take on EEs field on multiple selected OBPs at once. To apply the setting, on the OBP Mass Update window, first select Update Plan Setup Details to display fields in the Setup Details fieldset and then select Exempt Take On Employees. See Manually Adding an Offered Benefit Plan and Using Mass Update from Benefits Batch OBPs Search
75815	Added _HE_DateComparison Business Rules on Benefits Batch and Benefits Plan to Compare Expiration Date and Effective Date Two new business rules (System Admin > Advanced > Manage Business Rules) using the _HE_DateComparison business rule method have been added on the Benefits Batch and Benefits plan tables. The rules, both named Expiration Date Must Follow Effective Date, compare the Expiration Date and Effective Date fields to ensure that the Expiration Date is not before the Effective Date. Note: Both rules are Active by default. See Business Rule Methods.
75852	Updated SetImportID Business Rules on Benefits-Related Forms to Apply to All Pipelines and Added SetImportID Rule for Benefit Plan Group Detail A new SetImportID business rule has been added to set the Import ID value on the Benefit Plan Group Detail dataform. It is configured to apply to all pipelines. Additionally, previously created benefits-related rules that use the SetImportID business rule method on the following dataforms have also been configured to apply to all pipelines for new ClientSpace Benefits module implementations: Benefit Groups Detail Benefit Batch Detail Benefit Plan Detail Rate Group Detail Note: The change to update existing benefits-related SetImportID business rules to apply to all pipelines does not impact existing Benefits module users. See Business Rule Methods.
76448	Updated OBP Risk Factor Field and OBP Mass Update Process to Accommodate Risk Factor Values of 12 Digits After Decimal Previously, the Offered Benefit Plan (OBP) Risk Factor field allowed up to 4 digits after the decimal. Now, up to 12 digits after the decimal are allowed in the Risk Factor field. Additionally, the OBP Mass Update process for import to PrismHR has been updated to support the new Risk Factor character limit. See Using Mass Update from Benefits Batch OBPs Search and Manually Adding an Offered Benefit Plan.

Advanced Administration and System Administration

Case	Enhancement
66407	Added Exception Error Logging for DocuSign "Unable to Download Document" Previously, when the DocuSign signature process was complete and an "Unable to Download Document" error occurred when attempting to retrieve the signed document, exception error details were not recorded to provide troubleshooting assistance. Now, when an "Unable to Download Document" error occurs, details are recorded in the Exception Log (System Admin > Exception Log). Note: The level of exception detail recorded is controlled by the DocuSign API configuration Logging Level parameter. We recommend a Logging Level of Level 2 (Verbose) for DocuSign. See Viewing DocuSign Exception Errors.
68221	Added a Note Column to the Watch Widget A Note column has been added to the Watch Widget: Use it to enter the reason for placing the dataform under watch. Populate the field by opening a pinned item and editing the Notes field on the Modify Watch Item window: See Widget: Watch.
74428	Saved/Pinned Searches No Longer Override Field Display Rule Search Previously, if you pinned a saved search on the Field Display Rule Search page in System Admin > Advanced > Manage Field Display, the saved filter settings overrode the dataform location filter settings when the Field Display Rule Search page was accessed from a dataform. Note: There are two ways to access the Field Display Rule Search page from a dataform: From System Admin > Advanced > Dataform Admin or from a dataform via a workspace (by clicking Dataform Properties in the Action Center of the dataform on the workspace and then clicking Field Display Rules in the Action Center of the Dataform Properties page.) Now, when you access Field Display Rule Search page from a dataform, the page auto-filters by dataform location to only display rules associated with the selected dataform:
75404	Added Ability to Generate Import Mapping Template Files for Import Map Header and Import Map Detail Records You can now generate import template files containing import map header column names only or detailed import mapping information containing import header column names and field mapping details. The following import template file links have been added to the Import Map Header Detail record Action Center (System Admin > Advanced > Configure Import > Open Import Map Header file): Generate detailed Excel import mapping: This link generates a two-page Excel workbook containing import map headers on the Headers tab (Page 1) and import map detail record field descriptions on the Field Descriptions tab (Page 2). Headers tab (Page 1) Example: Field Descriptions tab (Page 2) Example: Generate CSV import headers: This link generates a .CSV file containing import map headers. When opened in Excel, the file contains a single tab. The name of the tab is the same as the associated Import Map Header Detail Source File name. Headers CSV Example: How this can help: When requesting assistance from ClientSpace support staff with import mapping, you can ensure that you are providing your import mapping information to them in a ClientSpace-supported format that they can use for troubleshooting. This eliminates time spent getting the file into a supported format which may result in shorter resolution times. See Generating Import Mapping Templates.
75406	Added Generative AI Tool for Creating Email Template Body Text Email Template functionality has been enhanced to include a Generative AI tool for creating body text with or without Replace Fields: Note: Please contact your Professional Services team representative or log an extranet case if you are interested in this feature. AI-generated responses are not moderated, reviewed, or endorsed by ClientSpace. Content may be inaccurate or incomplete and should be independently verified prior to use. SeeStep 2: Content and Using Generative AI to Create Email Template Body Text.
75676	Added WFC "Reload" Button to Improve Issues Stemming from Improper Loading of Secondary Conditions Grids When Server Is Busy Previously, when opening a Workflow Channel (WFC) containing numerous complex secondary conditions (i.e., typically more than 50) during a time when ClientSpace server resources were low, conditions on the Conditions tab sometimes loaded improperly with portions of the condition statement, such as the Operator value, displayed as "Empty". Additionally, the WFC could be accidentally saved in this state, resulting in unintentional loss of the original Conditions tab configuration values. Now, a Reload button has been added to the WFC Conditions tab (above the secondary conditions grid). It is used to restore all secondary conditions to the original state they were in when the page was first opened. Note: If you applied any additions, edits or deletions to the secondary conditions grid, they will be discarded upon Reload. The goal of using Reload is to revert the grid to the orginal state it was in so that none of the secondary conditions are overwritten with empty values stemming from the current improper loading of the grid. Therefore, any changes that you made to the secondary conditions grid while it was in the improperly loaded state cannot be retained. See Step 4: Conditions.
75693	Added Ability to Include or Exclude CORE Form Data in Global Search Index An Include in Global Search setting in the table metadata (System Admin > Advanced > Tables) of the following CORE (i.e., CRM) forms allows developer users to include the form in or exclude the form from the Global Search index: Activities (tblContactMgmtNotes) Task (Incident) Contact (tblContact) Organization (tblOrganization) Workspace (Projects) Data from excluded forms will not display in Global Search results. Note: By default, the Include in Global Search checkboxes in the Activities (tblContactMgmtNotes) and Organization (tblOrganization) table metadata are unchecked and will not be included in Global Search indexing unless a developer user re-enables the setting. Global search indexing changes take effect after the Populate Search Index scheduled process runs. See Global Search Configuration.
76313	Improved Graph API Email Integration Error Messages and Exception Error Logging Previously, Graph API email integration error and exception error logging that occurred during authentication failures lacked sufficient details or was not clear enough to support troubleshooting efforts. Now, error messages and error log entries are clearer and more detailed. For example, the following error message displays on the mailbox configuration record (System Admin > Email Integration) when the access token is invalid: "Unable to connect Please check your connection settings and try again. The access token is invalid. Please use the cloud icon in the Action Center to reauthenticate your email mailbox." In the Exception log (System Admin > Exception Log), additional details are recorded in the "Error Stack" section of the Exception Details record: Graph API Connection Test error: This is the corresponding exception error that is recorded when the previously mentioned "access token is invalid" error occurs on the mailbox configuration form. Graph API Integration error: This exception error is logged when the Process Email Integration scheduled process runs and the access token is invalid. See Switching to Graph API from IMAP.
76588	Added Backup and Restore Configuration Cloning Backup and Restore configuration cloning is now available from the following dashboards: Email Templates Workflow Channels Widget Layouts API Configuration How this can help: If you have a test installation of ClientSpace, you can set up and test new email templates, workflows, widgets and APIs. Then, once the test configuration is working as desired, you can clone the configuration from the test environment to a backup file and restore it in the production environment (thereby alleviating the task of manually reconfiguring the settings in production.) You can also use Backup and Restore to back up a production configuration file before you make changes so that you can easily roll back to the original version if needed. Note: Please contact your Professional Services team representative or log an extranet case if you are interested in this feature. See Backup and Restore Configuration Cloning.
76595	Added Salesforce Attachments Import Attachments from Salesforce Account or Opportunity records can now be imported to ClientSpace. Salesforce Account records are added to the ClientSpace Organization Attachments pane in the Action Center. Salesforce Opportunity records are added on the associated Client Master Attachments pane in the Action Center. Once properly configured, when the Salesforce scheduled process (Salesforce Sync Rest API) runs, Salesforce work queue records with the Completed flag unchecked and the File Download Only flag checked are processed for import of file attachments into ClientSpace. Note: When the File Download Only flag is checked, only file attachments on the Salesforce Account or Opportunity record will import into ClientSpace. When File Download Only is unchecked, only Salesforce Account or Opportunity record updates will import. Record updates and file downloads are not included in the same work queue record. Each file download is also evaluated to ensure its file extension matches a supported file extension in ClientSpace. If it does not, the file download is skipped. A determination is also made as to whether the file is a new attachment to be added or an existing attachment to be overwritten. (Note that there is no file versioning. Existing files are always overwritten.) See Configuring the Salesforce Attachments Import.
76827	Added Ability to Connect Multiple Salesforce Instances via the Salesforce API to a Single ClientSpace Installation The Salesforce integration in ClientSpace has been updated to support importing and exporting data to and from multiple Salesforce instances connected to a single ClientSpace installation. Note: This enhancement does not impact existing ClientSpace Salesforce API configurations. See Connecting Multiple Salesforce API Instances to a Single ClientSpace Installation.

General User Enhancements

Case	Enhancement
73043	Disabled COI Report The Certificate of Insurance (COI) report has been disabled and is no longer supported as it is an unused report. Note: If you are interested in running this report, please log an extranet case.
75585	Global Search Results Start at the Top For New Searches Previously, if you were reviewing Global Search results, cleared the search bar and then entered new search criteria, the new search results displayed but the focus remained where you were when you were viewing the previous search results. Now, when you enter new search criteria, the focus shifts to the top of the new search results.
76923	Added Document Previewer Toolbar Enhancements Plus Bug Fix Multiple enhancements were made to the Document Previewer toolbar. In addition, a bug that allowed the Document Previewer to be opened multiple times when pressing Enter has been fixed. Toolbar enhancement highlights include the following: A separator line now appears between tool groups (i.e., page selection, zoom, and download) so that related tools are easily distinguished. The zoom function has been updated: You can zoom in or out by using the magnifier tools: Zoom In to increase the zoom level, Zoom Out to decrease the zoom level. You can also manually type a zoom value into the data entry field located next to the magnifier tools and press Enter to increase or decrease the zoom level. For image-based previews, such as Word, Excel, or PDF files, the value is entered as a percentage: Minimum zoom = 25%, Maximum zoom = 300%. For text-based previews, such as text or XML files, the zoom value must be entered as a font point-size value: Minimum point size = 8pt, Maximum point size= 48pt. For image-based previews, intelligent zoom (also referred to as contextual zoom or focus zoom) maintains your relative position as you zoom in or out instead of zooming from a fixed center point. For instance, if you scroll to the center of the page and zoom in or out, the focus remains approximately at the center of the page you are viewing. For image-based previews, if you zoom in to a level where the entire page no longer fits on the screen, hold down left mouse button so that the grab hand becomes a "closed fist" (i.e., a "pan and drag" tool) that you can use to move an area of the document into view without changing the zoom level: Note: For the complete list of all new zoom functionality plus a new "hot keys and shortcuts" section, refer to the "Using the Document Previewer" section of the referenced document below. See Document Previewer

Case

Enhancement

73043

Disabled COI Report

The Certificate of Insurance (COI) report has been disabled and is no longer supported as it is an unused report.

Note: If you are interested in running this report, please log an extranet case.

75585

Global Search Results Start at the Top For New Searches

Previously, if you were reviewing Global Search results, cleared the search bar and then entered new search criteria, the new search results displayed but the focus remained where you were when you were viewing the previous search results. Now, when you enter new search criteria, the focus shifts to the top of the new search results.

76923

Added Document Previewer Toolbar Enhancements Plus Bug Fix

Multiple enhancements were made to the Document Previewer toolbar. In addition, a bug that allowed the Document Previewer to be opened multiple times when pressing Enter has been fixed.

Toolbar enhancement highlights include the following:

A separator line now appears between tool groups (i.e., page selection, zoom, and download) so that related tools are easily distinguished.
The zoom function has been updated:
- You can zoom in or out by using the magnifier tools: Zoom In to increase the zoom level, Zoom Out to decrease the zoom level.
- You can also manually type a zoom value into the data entry field located next to the magnifier tools and press Enter to increase or decrease the zoom level. For image-based previews, such as Word, Excel, or PDF files, the value is entered as a percentage: Minimum zoom = 25%, Maximum zoom = 300%. For text-based previews, such as text or XML files, the zoom value must be entered as a font point-size value: Minimum point size = 8pt, Maximum point size= 48pt.
- For image-based previews, intelligent zoom (also referred to as contextual zoom or focus zoom) maintains your relative position as you zoom in or out instead of zooming from a fixed center point. For instance, if you scroll to the center of the page and zoom in or out, the focus remains approximately at the center of the page you are viewing.
- For image-based previews, if you zoom in to a level where the entire page no longer fits on the screen, hold down left mouse button so that the grab hand becomes a "closed fist" (i.e., a "pan and drag" tool) that you can use to move an area of the document into view without changing the zoom level:
Note: For the complete list of all new zoom functionality plus a new "hot keys and shortcuts" section, refer to the "Using the Document Previewer" section of the referenced document below.

See Document Previewer

Performance

Case	Enhancement
72852	Improved Performance of "Generate Recurring Tasks" Scheduled Process The following performance improvement changes were made to the "Generate Recurring Tasks" scheduled process (System Admin > Advanced > Scheduled Processes): Previously, if an exception error occurred during processing of recurring tasks, all task generation ceased. Now, the exception is logged for the failed task and the processing of remaining tasks continues. Previously, if either of the Task Manager > Configure Recurrence date offset setting (Start Date Offset or Due Date Offset) was a very large number, an exception error occurred during processing of recurring tasks. Now, date offsets cannot be longer than 3 years (1095 days). If you enter a Start Date Offset or Due Date Offset of greater than 1095 days, the following error message displays on the "Select a Recurrence Pattern" configuration window: "Date offsets cannot be longer than 3 years (1095 days)." You must enter a value less than 1095 days before you can save the configuration. See Scheduled Processes and Configuring Recurring Tasks.

Case

Enhancement

72852

Improved Performance of "Generate Recurring Tasks" Scheduled Process

The following performance improvement changes were made to the "Generate Recurring Tasks" scheduled process (System Admin > Advanced > Scheduled Processes):

Previously, if an exception error occurred during processing of recurring tasks, all task generation ceased. Now, the exception is logged for the failed task and the processing of remaining tasks continues.
Previously, if either of the Task Manager > Configure Recurrence date offset setting (Start Date Offset or Due Date Offset) was a very large number, an exception error occurred during processing of recurring tasks. Now, date offsets cannot be longer than 3 years (1095 days). If you enter a Start Date Offset or Due Date Offset of greater than 1095 days, the following error message displays on the "Select a Recurrence Pattern" configuration window: "Date offsets cannot be longer than 3 years (1095 days)." You must enter a value less than 1095 days before you can save the configuration.

See Scheduled Processes and Configuring Recurring Tasks.

Fixes

Case	Issue summary	Resolution
74457	Corrected Issue with Subscribers Continuing to Be Notified on Tasks After Being Removed as a Subscriber	Previously, when a subscriber was removed from a task, they continued to receive task notifications. Now, former task subscribers are no longer notified unless they are added to the task subscribers list again.
76410	Corrected Issue with PrismHR API Not Updating the Employee Count on the Completed ClientSpace Payroll Batch Record	Previously, after the PrismHR Import Payroll Batch Sync scheduled process ran to process a payroll batch, if you opened the completed Payroll Batch record in the associated ClientSpace workspace, the Employee Count field on the record was 0. This issue has been corrected. The Employee Count field of the completed ClientSpace Payroll Batch record now reflects the number of employees processed in the batch.
76718	Corrected Issue with PrismHR Ongoing API Not Generating Import Queue Records for the Employee Benefits Detail Import Map When the Employee Benefits Import Map Was Also Active	The PrismHR Ongoing API (Employee Benefit Detail PHRAPI_ee_benefits_detail.csv) was not generating import queue records if the Emp Benefits PHRAPI_emp_benefits.csv import map was also Active. Now, two import queue records are created for each import map when both are Active. One is created for PHRAPI_emp_benefits.csv and another for PHRAPI_ee_benefits_detail.csv.