Release 162 Notes - April 2026

Updated Version 3.0 Organization POST Method to Return pkOrganizationID in the Response Body

The POST /api/organization/v3.0 method for creating a new organization has been updated to include the created pkOrganizationID in the Response Body. This will provide the information needed for future updates to the organization record.

Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Organization section and then expanding the POST /api/organization/v3.0 method.

Updated Handling of Inactive Benefit Groups

Previously, Inactive Benefit Groups containing Active Offered Benefit Plans (OBPs) appeared the same as Active benefit groups in BPM and also were included in Selection Summary/Signature page calculations. Now, the following changes have been made to allow BPM users to review historical benefit groups that are now Inactive without the Benefit Groups being editable or included in the renewal totals or Selection Summary/Signature page calculations:

On the Manage Benefits > Benefits Summary Page:

• Active Benefit Groups are listed alphabetically first. Inactive Benefit Groups are listed alphabetically after the list of Active Benefit Groups.

• For each Inactive Benefit Group, "(Non-Renewal)" is appended to its name, the Benefit Group is read-only with its name in black text, and no amounts from its associated OBPs are shown in the Renewal section or included in the Renewal Totals calculations.

  In the example below, the benefit group "Main" is Inactive and contains a single Active Health plan.

  

On the Manage Benefits > Benefits Summary > Group Summary >Plan Comparison Tab:

• Inactive benefit groups are not visible (as you cannot click the "read-only" Benefit Group name on the Manage Benefits > Benefits Summary Page to drill into the Plan Comparison.)

On the Selection Summary/Signature Page:

• No OBPs from Inactive Benefit Groups are listed.

• Upon finalization of the Benefits Batch in BPM, all OBPs in Inactive Benefit Groups are set to "Cancel" status and inactivated.

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

Updated BPM Selection Summary "Plan ID" Column to "Plan"

Previously, on the Selection Summary/Signature page of BPM, the Plan ID column in the grid displayed the Plan ID. Now, the column name has been changed to Plan and it displays the Plan Title (if available) up to 60 characters.

Note: 

• If no Plan Title is entered for the benefit plan, the Plan ID displays.

• If the Plan Title is greater than 60 characters, ellipses (...) display at the end of the Plan Title. You can hover your mouse pointer over the Plan Title to see the full value.

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

Corrected BPM "Plan Type" Display Inconsistency with "Suppress from Presentation" Options

Previously, when Suppress from Entire Presentation was selected on a Benefits Plan in a scenario where plan suppression resulted in no plans being left in the Plan Type category (such as when there was only one plan in the category and it is now suppressed), the plans as well as the Plan Type were able to be navigated to. Removing the Plan Type from the drop-down list on the Plan Comparison tab ( Manage Benefits > Benefits Summary > Group Summary >Plan Comparison) prevented the user from selecting a Plan Type containing no plans.

See BPM Benefit Plan Suppression.

Updated Pricing Console Surcharge Security Entities Related to Editing Surcharge Types

Previously Sales users could override the Surcharges bill rates, even though they didn't have access to the Surcharge Type.

Now, Pricing Console Surcharges security entities have been updated to work as follows:

• By default, Global Administrators (i.e., users with Admin rights) can edit secured pricing fields and surcharge types without requiring additional entity assignments. Additionally, even if the Admin user was assigned a surcharge type entity or individual pricing field entity with lesser rights, the gen_Surcharges entity with Admin access overrides entity assignments to specific fields or surcharge types.

• Other users without Admin access will require Edit access rights to a secured surcharge type or individual pricing field.

See:

• Standard Security Entities

• Configuring Pricing Console Security in ClientSpace PEO

Added Ability to Exclude Claim Deductible Bills from Prism Export

If you have Claim Deductible Bills that are billed outside of PrismHR, you can now prevent them from being included in the "Bill Pending" export to PrismHR (even if a Claim Deductible Bill is in "Ready to Bill" status). A new Exclude from Prism Export checkbox has been added to the Claim Deductible Bill form. When checked, the Claim Deductible bill is excluded from export to PrismHR.

Additionally, a new Mass Update feature has been added to the Claim Deductible dashboard (accessed from the Modules toolbar or from Modules Search by clicking your username and then selecting Modules in the upper right corner of ClientSpace). Mass Update allows you to set Exclude from Prism Export and Status field values on multiple Claim Deductible bill forms at once.

The dashboard also now displays an Exclude from Prism Export column and an Exclude from Prism Export search option has been added to the More search.

See:

• Using the Claim Deductible Bill Form

• Using Mass Update from the Claim Deductible Dashboard

Added Ability to Change Survey Question and Survey Description Text Color Independently

Previously, there was a single Text Color field located in the "Survey Theme" fieldset of the Survey Design page that controlled the color of both the survey question and survey description text. Now, you can set the survey question and survey description text independently using the following two fields:

• Description Text Color

• Question Text Color

Note: Question Text Color also sets the color of the Submit button text and the Rating Scale text.

See Configuring a Dataform Survey Email Template.

Added "Remote Location?" Checkbox to Client Location Dataform Set by PHRAPI Initial Import

A Remote Location? checkbox has been added to the Client Location dataform (System Admin > Advanced > Dataform Admin). This field will be initially set to the PrismHR value by the PHRAPI Initial Location import process (PHRAPI_initial_location*.csv) and maintained via the PHRAPI Ongoing Location import process (PHRAPI_location*.csv).

To support this process, a RemoteLocation Import Map Detail record has been added to both the PHRAPI_initial_location*.csv and PHRAPI_location*.csv Import Map Header configuration files (System Admin > Advanced > Configure Import).

Dataform Modules Did Not Respect Unchecked "Search on Load" Configuration Setting/Unlocked "Search on Load" for Singleforms

Previously, when a dataform was configured as a module (System Admin > Modules) and Search on Load in the dataform properties (System Admin > Advanced > Dataform Admin) was unchecked, the form still loaded with a populated grid. Now, when Search on Load is unchecked on a dataform configured as a module, the search dashboard grid correctly loads unpopulated with the "Please enter search criteria and click the search button to see results" message displayed in the unpopulated grid space.

In addition, the Search on Load dataform property has now been unlocked to work with single dataforms (i.e., singleforms). This includes workspace singleforms and singleforms configured as dataform modules.

Note: To use Search on Load with any multi-form or single dataform configured as a module, an administrator must configure grid columns in the Dataform Properties Multi Col column. If no columns are configured, when the search dashboard loads, the following error message displays: "Grid columns have not been configured for this search page".

See:

• Adding or Deleting a Dataform

• Configuring a Dataform to Open as a Module

Added Import Mapping Configuration Backup and Restore

Configuration backup and restore is now available on the Import Map Header Search dashboard (System Admin > Advanced > Configure Import). This feature can be used to copy and then restore import map header record configuration along with the related import map header detail file record configuration.

Note: 

• The restored configuration will overwrite the original backed up configuration if it still exists in the site.

• The restored map header record is flagged Inactive by default. Check the Active flag to enable it.

• Please contact your Professional Services team representative or log an extranet case if you are interested in this feature.

See Configuration Backup and Restore.

Previously, the following error sometimes displayed when clicking the Resync button on a ClientSpace calendar set up to integrate with an external Gmail calendar: 

"There was a problem connecting to your external calendar. Please review the help document - "Adding External Calendar Events" for information on how to resolve this issue. Cannot insert the value NULL into column 'Subject', table 'ClientSpace.dbo.tblExternalCalendarEvents'; column does not allow nulls. INSERT fails. The statement has been terminated."

This issue occurred when one or more Gmail calendar events had a blank title. Now, Gmail calendar events with no title import successfully.

Previously, the OBP Import performed a case-sensitive comparison of the PrismHR Plan ID and the ClientSpace Carrier Plan Code (which is located on the OBP's associated Benefit Plan record) to determine a match when updating OBPs. If the case was not the same, no match was found and therefore, no update occurred. Now, case-sensitivity is no longer required for determining a match of Plan ID and Carrier Plan Code.

When adding a new Field Display Rule on a dataform or configuring Custom Links, Email Templates and Workflows from a dataform via Dataform Admin, the dataform location (i.e., the dataform name of the associated dataform) no longer defaulted as it did in previous releases of ClientSpace. This issue has been corrected. The affected fields are listed in the table below:

Previously, if a dataform page header contained carat symbols (< >) and you clicked the Magnifying Glass in the Action Center to access the audit trail, "Sorry, an error has occurred" displayed. This was happening because ClientSpace uses the dataform header page header to create the Audit Trail page header and certain special characters are not accepted. Now, ClientSpace strips carat symbols (< >) from the dataform page header before building the Audit Trail page header.