Release 168 Notes - October 2026

R168 Sprint: 9/1/2026 to 9/30/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 R168 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 9/1/2026 to 9/30/2026
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	October 6, 2026
Group 2	Second Tuesday of the month	October 13, 2026
Group 3	Third Tuesday of the month	October 20, 2026

Enhancements

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

ClientSpace Premium

ClientSpace API

Case	Enhancement
76771	Enhanced ClientSpace API version 3.0 POST, PUT, and PATCH methods in Dataform, Organization, and Task Sections to Support Bypassing "Save Anyway?" Previously, when you ran a ClientSpace API request and a "Save Anyway?" soft error warning was encountered, the Response Code displayed a 400 error and an error message similar to the following displayed in the Response Body: Now, you can set the SaveAnyway parameter on a POST, PUT, or PATCH method in the Dataform, Organization, and Task sections to True to bypass "Save Anyway?" soft errors directly within the request payload, eliminating the need for the Save Anyway URL when testing in Swagger. Use the following format in the values field of the Swagger "Parameters" section: "SaveAnyway: true. This is illustrated in the image below: Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding each method. See ClientSpace API Change Log.
76808	Enhanced ClientSpace API Version 3.0 Task Method to Support Recurring Task Management The following ClientSpace API Task method endpoints have been updated to provide better visibility into recurring tasks: GET /api/task/v3.0/find GET /api/task/v3.0/{id} These endpoints now include fields to identify if a task is a recurring task template (isPrimaryRecurringTaskTemplate), if it was triggered by a recurrence schedule (isRecurring), and the ID of its source task (RecurrenceSourceTask). Additionally, the task search endpoint, GET /api/task/v3.0/find, supports filtering by these recurring task criteria and includes Date Updated and Date Created timestamps in the response. Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding each method. See ClientSpace API Change Log.

Case

Enhancement

76771

Enhanced ClientSpace API version 3.0 POST, PUT, and PATCH methods in Dataform, Organization, and Task Sections to Support Bypassing "Save Anyway?"

Previously, when you ran a ClientSpace API request and a "Save Anyway?" soft error warning was encountered, the Response Code displayed a 400 error and an error message similar to the following displayed in the Response Body:

Now, you can set the SaveAnyway parameter on a POST, PUT, or PATCH method in the Dataform, Organization, and Task sections to True to bypass "Save Anyway?" soft errors directly within the request payload, eliminating the need for the Save Anyway URL when testing in Swagger. Use the following format in the values field of the Swagger "Parameters" section: "SaveAnyway: true. This is illustrated in the image below:

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

See ClientSpace API Change Log.

76808

Enhanced ClientSpace API Version 3.0 Task Method to Support Recurring Task Management

The following ClientSpace API Task method endpoints have been updated to provide better visibility into recurring tasks:

GET /api/task/v3.0/find
GET /api/task/v3.0/{id}

These endpoints now include fields to identify if a task is a recurring task template (isPrimaryRecurringTaskTemplate), if it was triggered by a recurrence schedule (isRecurring), and the ID of its source task (RecurrenceSourceTask). Additionally, the task search endpoint, GET /api/task/v3.0/find, supports filtering by these recurring task criteria and includes Date Updated and Date Created timestamps in the response.

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

See ClientSpace API Change Log.

Benefit Plan Manager (BPM)

Case	Enhancement
77253	Added "View Only On BPM" Setting for Waiting Period, HSA, FSA, and Commuter Plan A new  View Only On BPM multi-select lookup field has been added to the BPM Config dataform in the Admin Workspace. The new setting lets administrators make the Waiting Period, HSA Plan, HSA Contribution, FSA Plan, and Commuter Plan Offered options read-only for clients in the Benefit Plan Manager (BPM). Clients can view the selected items in BPM but cannot change them, and a message in each area indicates that it is read-only. In the example below Commuter, FSA and HSA are selected in the View Only on BPM field of the BPM Config form: As a result, the HSA Plan, HSA Contribution, FSA Plan, and Commuter Plan Offered areas are read-only for BPM Clients as shown in the excerpt of the panel below from the BPM Selection/Summary page: If all options in a panel are set to read-only, the Save button is hidden as shown in the example above. The Save button is available when at least one option in the panel is not read-only as shown in the panel excerpt from the Group Summary page below where Waiting Period is read-only but the editable Cafeteria Plan option is also present in the panel: The following additional changes were made: Previously, there was an existing setting on the BPM Config dataform named Waiting Period Is Read Only On BPM. This field has now been replaced by the View Only on BPM field and, with this update, existing settings are carried over. Where Waiting Period Is Read Only On BPM was set to "Yes", "Waiting Period" is now selected in View Only On BPM. An existing setting on the BPM Config dataform,  Do Not Show on BPM, allows you to hide HSA, FSA or Commuter options in BPM. If any of these options are selected in the field, they will not display in BPM at all, as this setting takes precedence over View Only on BPM. See: BPM Site Configuration BPM Option 1: Reviewing, Selecting, and Approving Benefits With Prior Batch History BPM Option 2: Reviewing, Selecting, and Approving Benefits - No Prior Batch History
78570	Updated BPM Internal BPM Access and Contact Management How BPM manages contacts and validates portal access has been updated to prevent duplicate contact records and improve support for contacts across different workspaces. Internal access: With this update, internal users can access BPM through the Internal BPM Access link without first assigning a Renewal Client Contact via their current user login. When BPM is accessed using your current user account, you will note some slight changes in the BPM display (outlined in the related article) due to there being no client details available. Client Access: Additionally, BPM client access validation is now managed through Additional BPM Contacts, improving support for contacts across different workspaces and providing a more consistent user experience. This means that once you add a Renewal Client Contact for client access and it is automatically added to the Additional BPM Contacts form, validation of the Renewal Client Contact and any other user you manually add to the form is occurring on the Additional BPM Contacts form only. Note: Be certain to add a Renewal Client Contact before sending BPM notifications to clients. When you do this, existing functionality ensures the contact is automatically added to (and maintained by the system) in Additional BPM Contacts as well as displayed throughout BPM as the client's Benefits Contact. The update also includes a script to clean up any duplicate contacts added to the Additional BPM contacts form. See Adding and Editing BPM Additional Contacts.
78773	Added Benefit Batch Cloning Logs for BPM Contacts When using the Clone to Child Batches action on a Benefit Batch, the system now generates an Update Log entry to track BPM Contact changes. This log provides visibility into the process by recording the specific contacts successfully cloned with their access levels, as well as any contacts that failed to clone.
78903	Fixed Age Band Display In BPM Resolved an issue in the Benefit Plan Manager (BPM) where age band records with a From Age but no To Age incorrectly displayed "null" in the plan detail pop-up. The From Age and To Age are now required fields. If either field is left empty upon save of a new record OR an existing record (created prior to this update), an error message displays indicating that the field is required. See: Using Age Banded Plans Viewing Age-Banded Rates

Other ClientSpace Premium

Case	Enhancement
77041	Added Survey Reminder Notifications You can now configure automated email reminders for survey recipients who have not yet completed their surveys by setting offset days in the Survey Reminder field on the Survey Design form. After the specified number of days passes, the Survey Reminder email template that you create triggers the notification. Note: You must create your own email template, separate from the original survey template, with a Type on Step 1: Initial of Survey Reminder and also configure the template to trigger from the Survey Reminder field on the Survey Design. The reminder is skipped if the recipient unsubscribes from this or all surveys or if they have already completed the survey. See: Creating and Using Surveys on Email Templates Email Template Configuration Step 1: Initial
77155	Added AI-Generated Case Discussion Responses Users can now use AI to draft responses in discussion threads from the email composition area of the interface. A new Generate Response button opens a modal window where users can customize the response tone, length, and language while selecting specific case and thread context for the AI tool to reference. Note: This feature is only available in the new Case Discussions user interface which was introduced in ClientSpace Release 165 Case# 77799 and further enhanced in Release 166 Case# 78428. Please contact your Professional Services team representative or log an extranet case if you are interested in this feature. See Using Generative AI to Create Case Discussion Responses.
77426	Added Survey Business Rule Methods Two new business rule methods were added to allow setting a field on a related form using primary survey results or "Additional Questions" survey results: SetSurveyResultFieldonTriggeringForm TableName: Must be set to Survey Results for the Method to be available. TargetForm: Must be set to the related form where you want to stamp the value from the Survey Results. Note: The system validates the related form (i.e., the form that triggered the survey) using the entity row GUID value to ensure that it is writing to the form that triggered the survey. If you enter the wrong form name in TargetForm, you will not receive an error, but no changes will be made. TargetField: Must be a field on the related form. It will hold the value from the Survey Results table. SourceField: The value on the Survey Results form that you want to copy to the TargetField on the related form. SetAdditionalSurveyResultFieldonTriggeringForm TableName: Must be set to Survey Question Answers (which is used to hold results from the "Additional Questions" section of the survey design) for the Method to be available. QuestionCodeValue: Identifies the specific question. Comes from the "Additional Questions" section of the Survey Design in the Question Code column. Important: If you are creating a rule where the Primary Trigger Field or Secondary Trigger field is a question from the "Additional Questions" section of a Survey Design, also make sure that the Trigger Business Logic checkbox is checked for that question in the Survey Design. See the Creating a Survey Designsection of the Creating and Using Surveys on Email Templates topic for more details. TargetForm: Must be set to the related form where you want to stamp the value from the Survey Question Answers. Note: The system validates the related form (i.e., the form that triggered the survey) using the entity row GUID value to ensure that it is writing to the form that triggered the survey. If you enter the wrong form name in TargetForm, you will not receive an error, but no changes will be made. TargetField: Must be a field on the related form. It will hold the value from the Survey Question Answers table. SourceField: The value on the Survey Question Answers form that you want to copy to the TargetField on the related form. See: Creating and Using Surveys on Email Templates Business Rule Methods
78544	Added Benefit Parent Company Sync Logic When saving a Benefits Batch, the system now automatically populates the Benefit Parent Company field with the corresponding value from the Client Master if the field on the Benefits Batch is empty. See Adding a Benefits Batch.
78652	Added Special PrismHR Process for Importing Group Benefit Plans Administrators can now import system-level (master) benefit plans from PrismHR into the ClientSpace Admin workspace without running the PrismHR Initial or Ongoing Import. To support this feature, the following changes were made: A new Special PrismHR Processes dataform was added to queue the import records. Each record identifies the PrismHR tenant and the plans to import, which you can filter by Plan ID, Carrier, Offer Type, or Insurance Class. Note: The Special PrismHR Process dataform will be used for multiple PrismHR processes. The Group Benefits API is the first process type available. The framework is designed to support more PrismHR import and export processes in future releases. A Special PrismHR Processes dashboard was added to manage Special PrismHR Processes queue records. A new PrismHR Special Processes scheduled process was added. The process runs hourly, picks up queued records, and inserts or updates the matching benefit plans from PrismHR. Access is controlled by the new AllowSpecialPrismHRProcesses security entity. Note: Please contact your Professional Services team representative or log an extranet case if you are interested in this feature. See: Group Benefits Import API Standard Security Entities
78724	Added "Renewal Assigned" to Benefits Batch Mass Update and New Child Security Entities You can now update the Renewal Assigned field for multiple Benefits Batch records simultaneously using the Benefits Batch Mass Update tool. This enhancement streamlines workload reassignments and reduces the need for manual, record-by-record updates. Additionally, four new child security entities were added to the existing parent security entity, biz_benefitsbatch_massupdate. Assignment of the parent entity is required. The following additional entities, secured at the Edit and Admin levels, can be used to control individual security access to the various Benefits Batch Mass Update features: biz_benefitsbatch_massupdate_fkRenewalAssignedUserID - Controls access to the Renewal Assigned mass update setting. biz_benefitsbatch_massupdate_MassOBPImport - Controls access to the Mass OBP Import setting. biz_benefitsbatch_massupdate_IncludeContributions - Controls access to the Include Contributions setting that is used in conjunction with the Mass OBP Import setting. biz_benefitsbatch_massupdate_Renew - Controls access to the Renew setting used to renew multiple Benefits Batches simultaneously. See: Using the Benefits Batch Mass Update Feature Standard Security Entities
78748	Updated Benefit Expirations Scheduled Process The Benefit Expirations scheduled process now automatically inactivates Benefit Batches and Benefit Plans with a status of "Cancelled" or "Cancel." This update ensures that cancelled records are removed from relevant selection lists and reports without requiring manual cleanup. See Scheduled Processes.
78895	Added Email Integration Case Discussion Linking A new Email Integration Discussion Linking feature is now available. When enabled, Email Integration can keep an email conversation together on a single case. After the initial case is created by the Email Integration feature, any additional reply emails in the thread are posted to that case's Case Discussions thread instead of creating a new case. The related HTML formatting is preserved and any email attachments are also added to the discussion message. Additionally, any replies sent from Case Discussions to the customer are also kept in the same email thread, so the conversation continues in both directions. If the original case is deleted, a reply creates a new case. Note: This feature is not enabled by default. Contact Professional Services or log an Extranet ticket if you are interested in enabling it. The feature cannot be applied retroactively to existing cases. It applies only to cases created after it is enabled. When the feature is enabled, you will notice a Sender address change if you use a "Noreply@" default sender. This is because Case Discussions notification emails for these cases are sent from the Email Integration mailbox address instead of the system's default sender address. This change was required so that customer replies return to the Email Integration mailbox to support linking reply emails to the initial case created. See Case Discussion Advanced Admin
79086	Added Tasks to "Round-Robin" Group Users Assignment and Other UI Enhancements Note: If you are interested in the Group Users Assignment feature, please contact the ClientSpace Professional Services team or log an Extranet ticket. Round-Robin Group Users Assignment now supports Tasks. Once a Group User is set in the Owner and/or Assigned To fields and a Save/Apply action is applied, the fields resolve to the next available user in the rotation. The Tasks functionality is available from following locations: Tasks Form UI: You can open a task (depending on your access permissions) from any location, including Task Manager and Quick Task, and select a Group User in the Owner and Assigned To fields. ClientSpace API: The ClientSpace API now supports creating or updating tasks via the ClientSpace API (v. 3.0) with the Owner and Assigned To fields. Both PATCH and POST operations support Group Users assignments. Note: In addition to the Help Center article, Setting a Group User from a Business Rule or from the ClientSpace API Task Endpoint, located in the referencedGroup Users Assignment section, documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding each method. Workflow Channels/Items: When setting up a workflow that triggers task creation when certain workflow conditions are met, you can now configure the Owner and Assigned to users to use a Group User on the Step 2: Content tab. Additionally, the following user interface changes were made: Flag Modified Rows and Fields: A change was made to display a yellow background on the affected row or field of Members grid on the Group Users configuration form to mark a row or field as "modified" when additions or edits are made. The entire grid is highlighted when an existing member is deleted. Changes activate the Save and Apply buttons on the form to ensure that warning error logic is triggered if you try to exit the form without saving the changes. Added User Info Popup Window: Added a user profile card popup in the Members grid on Group Users configuration (which is accessed by clicking the User icon next to a group member name). This allows quick access to user details such as name, email, phone, company, department, and address without leaving the current view. See Group Users Assignment. Also see: Video Learning how: ClientSpace Round Robin Assignment
79350	Improved Benefits Batch Renewal and Plan Cloning Resolved an issue where the Benefits Batch Renewal process was creating duplicate records during mass updates. Additionally, fixed a link error that occurred when a benefit plan renewed from a match could not be found, and improved the cloning process by excluding canceled plans and ensuring new plans are correctly activated and logged.
79457	Updated Gradient AI Risk API Version and Rejection Error Handling The Gradient AI Risk integration now uses version 2 of the Gradient AI policy rating API. Previously, submitting a Pricing Console batch with Submit To Gradient AI failed because Gradient AI had changed its API. The following additional changes were also made: When Gradient AI rejects a submission, no Gradient AI Risk Underwriting record is created. The error message appears on the Pricing Batch when you submit (as shown in the example error message below) and is also recorded in System Admin > Exception Log. Note: For accepted submissions, the Validation Results field on the Gradient AI Risk Underwriting record still shows any errors or warnings that Gradient AI returned after processing the submission. Loss History incurred amounts are now sent to Gradient AI rounded to two decimal places, which matches the format Gradient AI expects. See Gradient AI Risk.

Advanced Administration and System Administration

Case	Enhancement
73845	Modified _ModifyFieldValue Method Access Global Administrators can now configure rules using the _ModifyFieldValue business rule method, which was previously only configurable by Developer users and restricted to read-only access for Global Administrators. Important: Please thoroughly test each business rule you create using the _ModifyFieldValue business rule method to avoid unwanted data modifications. See Business Rule Methods.
74001	Enabled Read-Only _FieldCalculation Method Access Global Administrators can now view the business rule configuration of rules using the _FieldCalculation business rule method in a read-only format. This change allows for more effective troubleshooting and rule management without the risk of unauthorized modifications. See Business Rule Methods.
76059	Improved Global Search Index Update Frequency The Global Search indexing process has been enhanced to update more frequently using an index swapping process, ensuring search results reflect recent changes in near-real-time without a noticeable performance lag. The Populate Global Search scheduled process now runs every five minutes to synchronize the search index with updated records. See: Global Search Configuration Scheduled Processes
76065	Added Ability to Embed Widgets Within Dataforms Global Administrators can now embed Business Intelligence, Report Center (i.e., Sigma Reports), Image Display, and Query widget layouts within the body of a dataform, instead of only in the dataform header so that users can view related information without scrolling to the top of the form. The following changes were made: The Widget Layout Details form (System Admin > Widget Layouts) includes a new Available as a dataform checkbox field. When it is checked, the widget can only display embedded in the specified form identified in the Widget Layout Details form's Target Type field. Additionally, the widget library is filtered to only display Business Intelligence, Image Display, and Query Widget. Note: There can only be one widget per layout for embedded dataform widgets. You can add up to five embedded dataform widgets to a dataform. However, each must be the only widget on the widget layout record. Saving a layout that exceeds this limit displays the message: "For widget layouts that can be placed on dataforms you may have a maximum of one BI, Image, or Query widget." The loading behavior on embedded Business Intelligence and Query widgets is set by the system and is read-only to ensure proper page loading and performance. Dataform Admin (System Admin > Advanced > Dataform Admin > Fields) includes a new "Widget Layout" Element Type in the field properties. When this element type is selected, a new Widget Layout field displays. The field only lists published layouts where the Available as a dataform field is checked and where the Target Type on the layout is the current dataform. A dataform can contain a maximum of five widget layout fields as previously mentioned. The widget layout displays in a bordered container that spans both columns of the ClientSpace dataform's two-column format. Set the Row in the Dataform Admin field properties to control the vertical order of the field or fieldset containing the widget. The container respects the "Expanded" and "Collapsed" Field Set Default settings in Data Admin field properties if you choose to display the widget in a fieldset. The widget itself appears in its own frame (within the bordered container of the dataform) and is sized using the widget layout file like any other widget. The widget layout's own security and display conditions are ignored on layouts where the Available as a dataform field is checked . Instead, dataform field security and field display rules control the widget's field display and security conditions. See Embedding Widget Layouts in Dataforms.
76550	Added Anonymous Survey Support Global administrators can now create anonymous surveys by selecting the new Anonymous Survey checkbox in the survey design template (System Admin > Email Templates > Survey Design). When selected, survey results are recorded as "Anonymous," in the Completed By field, links to the triggering form are hidden in the user interface, and the entity row GUID of the triggering form is removed in the survey results table to ensure respondent privacy. Note: The Anonymous Survey setting cannot be changed after the initial save of a survey design. Accordingly, the setting cannot be applied to pre-existing survey designs since these are saved designs. See Creating and Using Surveys on Email Templates.
77917	Updated Email Admin Dashboard Data Retention Messaging A prominent message now displays at the top of the Email Admin dashboard to clarify that emails (which includes any associated attachments) are automatically deleted after 30 days. The related Help Center documentation was also updated. This ensures administrators are aware of the data retention policy. Note: You can take proactive steps, such as saving emails as activities or forwarding them to a separate mailbox, to preserve important records as outlined in the Help topic listed below. See Email Admin.
78707	Added Backup User Assignment For Workflow Channel or Item Tasks Administrators can now configure a Backup User for Workflow Channels or Workflow Channel Items where the Triggered Form on Step 1: Channel is set to Task and the Assigned To user or Owner selection on Step 2: Content is set to From a Field on a Form. This ensures that if the primary user on the Triggering Form is unpopulated, the task routes to a Current User or Specific User instead of defaulting to the channel owner. See: Adding a Workflow Channel - Step 2: Content Adding a Workflow Channel Item - Step 2: Content
78773	Updated Import Map Header and Detail Work Item Titles ClientSpace system administrators can now more easily distinguish between multiple open Import Map work items in the Work Center pane. The work item titles for Import Map Header and Import Map Detail records now dynamically display the specific Source File name for Import Map Header records and the File Column name for Import Map Detail records.

General User Enhancements

Case	Enhancement
78709	Updated Internal Notes Log Stamp The Internal Notes log stamp now includes the author's department code next to their name, providing immediate visibility into their department. This change applies globally to all sites using department codes and affects only new notes added after the update.
78723	Added Report Center peo_vwEEActiveCountPerClient Database View A new Report Center database view, peo_vwEEActiveCountPerClient, has been added to pre-calculate active employee counts per client. This change improves performance for the aging report by removing heavy employee-level joins, preventing report timeouts on large client sites. See PEO View Listing
78913	Updated Save State Behavior for Search Dashboards When you save your work items, a search dashboard's current search criteria are now preserved and restored when you select Resume Saved Work Items. Previously, if the dashboard included a pinned search under Saved Searches, the pinned search was restored instead of the search criteria that were active when the state was saved. See Work Center.
79219	Enhanced Case Discussion Reply Interface Updated the Case Discussion interface to integrate the Reply panel within the message thread. This change allows you to scroll through the entire discussion history while drafting a response without needing to hide the Reply panel to reference previous messages. See Replying to Case Discussions.

Technical Enhancements

Case	Enhancement
72954	Removed Document Service Dependency The legacy Document Service dependency has been removed from the Core Classic and Core Next environments. This internal cleanup ensures that all document-related functions now utilize the updated Azure Functions architecture, allowing for the eventual archiving of the old service.

Case

Enhancement

72954

Removed Document Service Dependency

The legacy Document Service dependency has been removed from the Core Classic and Core Next environments. This internal cleanup ensures that all document-related functions now utilize the updated Azure Functions architecture, allowing for the eventual archiving of the old service.

Fixes

Case	Issue summary	Resolution
79479	Fixed Document Search Module Error	Previously, the Document Search module sometimes displayed an error and did not return results when a search was run. This issue is resolved, and Document Search now returns results as expected.
79502	Fixed Quick Clone of Cases With Attachments	Previously, when a user Quick Cloned a case with attachments included, the clone failed with an error if any of the attachment files had been moved to file storage. Quick Clone now retrieves those attachments from file storage, and the case is cloned with its attachments as expected.