Release 166 Notes - August 2026

Improved Benefit Group Management via PrismHR API

Two new date fields named Stop All Use On and Stop New Use On have been added to the PHRAPI_initial_codes_benefitgroup*.csv and PHRAPI_codes_benefitgroup*.csv import map header configuration records (System Admin > Advanced < Configure Import) for import from PrismHR. The same fields have been added to the Benefit Groups dataform (System Admin > Dataform Admin) so that the values from the corresponding imported PrismHR fields can populate the dataform. The ClientSpace system will use the imported date field values to skip importing Benefit Groups via the OBP Import process that have a stop date that is on or before the current day. The following message displays in the OBP Import processing window: "Benefit Group Code {code value} has a stop date that is on or before today. Skipped Processing." Also see related Case# 78003.

See Manually Adding a Benefit Group.

Benefits Export API: Updated ExportOfferedPlansToPrism Business Rule

The Benefits Export API now includes enhanced logic for exporting offered plans to PrismHR to reduce manual intervention. When One Month Prepay is selected on the Offered Benefit Plan (OBP), the system automatically adjusts the Pending Billing Rate Group Effective Date to one month prior to the OBP's Effective Date (i.e., OBP Effective Date minus one month). If One Month Prepay is not selected, the OBP Effective Date is used "as is". Additionally, new benefit plans will now use the OBP's Effective Date as the start date in PrismHR instead of the batch open enrollment start date.

See Configuring Benefit Plan API Business Rules.

Added Client Benefits Plan Export Merge Template Enhancements

The Client Benefit Plans Export Merge template has been updated as follows to improve the accuracy of Risk Factor and Rate Group data:

• Premium Risk Factors now export in up to 6 prioritized columns (PremRiskFactor1 through PremRiskFactor6), preserving historical data.

• Rate Groups export using a hierarchy to determine the value to export: 1. OBP Rate Group, 2. Benefits Batch Default Rate Group, or 3. "GLOBAL" if the Rate Group fields are blank. This matches PrismHR standard logic.

• Premium Risk Factor exports as 1.0000 for manual Rate Groups; otherwise, ClientSpace exports the Risk Factor percentage. Or, the Risk Factor remains blank if no Rate Group is entered.

• Risk Factor Dates export using the Benefits Batch Effective Date. However, if the PremRiskFactor value is blank, its corresponding Risk Factor Date field is also left blank.

• No duplicate plan rows are created for multiple risk factors.

IMPORTANT: The Client Benefits Plan Export merge will no longer receive updates after ClientSpace Release 166. To ensure access to future enhancements and ongoing support, we recommend using the Benefits Plan Export API which will continue to be the supported solution for exporting benefits plan data.

See Client Benefit Plans Export Merge.

OBP Import Benefit Group Name Mapping Update

When creating Benefit Groups via the OBP import, the system now correctly maps the group description from PrismHR to the Group Name field on the Benefit Groups record in ClientSpace. Previously, the import incorrectly placed the group code in both the Group Code and Group Name fields. Additionally, the system now honors the Stop All Use On and Stop New Use On dates referenced in Case# 67873.

The OBP Import process now skips importing Benefit Groups that have a PrismHR Stop All Use On or Stop New Use On date that is on or before the current day and displays the following message in the OPB Import processing window: "Benefit Group Code {code value} has a stop date that is on or before today. Skipped Processing." Also see related Case# 67873.

See Using the Benefits Batch Mass Update  Feature for OBP Import and Batch Renewal.

Added Support for Age Banded Benefit Plans

Benefits Administrators can now configure age banded plans for categories such as age, gender, and tobacco-use directly within a Benefit Plan to manage complex rate structures more accurately. This update introduces a new Banded dataform and lookup options, providing a structured foundation for future reporting and automated rate calculations. These enhancements eliminate manual workarounds and improve data integrity for plans requiring multiple rates under a single benefit plan.

See: 

• Configuring Age Banded Plan Setup

• Using Age Banded Plans

Added Ability to Set Code or Decode Values from a Lookup and Multi-Lookup Fields in a TargetField Using the _ModifyFieldValue Method

You can now set a Code or Decode value from a Lookup or Multi-Lookup field in a specified target field on any main form, child tab, singleform (in the same workspace) or related multi-form when using the _ModifyFieldFieldValue business rule method. This is achieved by entering a formula in the Value field of the _ModifyFieldValue "Method Parameters" section that includes either a .decode parameter to set a Decode value or a .code parameter to set a Code value after the specified lookup or multi-lookup Replace Field name.

In the example below, the following formula was added to the Value field which was then translated in the TargetField of the TargetForm (as shown in the image of the field below the formula):

Note: 

• A composite delimiter (!.!) is automatically used to separate multiple multi-lookup Code or Decode values in the TargetField.

• This rule method can only be configured by Developer users. If you are interested in configuring a rule using this method, please contact Professional Services or log an Extranet ticket.

• If you are a Global Administrator, you can view the business rule configuration of any rule using the _ModifyFieldValue business rule method but you cannot edit the rule.

See Business Rule Methods.

Added Custom Link Code Value Display in Business Rule Configuration

When configuring Business Rules using HdrAction as a trigger field (i.e., Primary Trigger Field or Secondary Trigger Field), the trigger value (i.e., Primary Trigger Value or Secondary Trigger Value) drop-down list now displays the value from the Code Value field of the Configure Links Detail form (.i.e, custom link configuration form) in parentheses to the right of the display value as shown in the image below:

Note: If the Code Value associated with the custom link is modified, the drop-down list values on the business rule configuration form are also updated.

Added I-9 Eligibility Data Import Mapping Enhancement to PrismHR API Ongoing Employee and Employment Imports

The PrismHR API Employee and Employment ongoing import mappings (PHRAPI_employee*.csv and PHRAPI_employment*.csv) have now been updated to include the following placeholder mappings:

• I9EligibilityDoc

• I9EligibilityDocExpDate

This update ensures that I-9 eligibility attributes are correctly mapped and imported rather than being skipped or added to the "Excludes" list in the PrismHR Employee subscription record.

Added Dataform Field Search Module

You can now search for fields across all dataforms using the new Dataform Field Search module in the Advanced Administration section of System Admin. This module includes comprehensive Quick Search and More search filtering options for field labels, names, and behaviors, along with saved search functionality. Additionally, a new magnifying glass icon on the Dataform Fields view of Dataform Properties allows users to jump directly to the search dashboard with the current dataform pre-filtered.

See Using Dataform Field Search.

Modified Assume User Functionality to Easily Revert to Original User

Global admin users can now quickly return to their original account after assuming another user by clicking a link in a new banner that displays on the ClientSpace main page under the modules bar.

The banner remains visible even when opening records in new tabs. This change eliminates the need to log out and log back in manually to switch back to the original admin account.

See Assuming a User Login.

Enhanced Document Search Module

The Document Search module has been enhanced to include additional searchable fields for Client Number, File Source, and Secondary ID. You can perform filtering and searching by the new fields as they have been added to More search. Additionally, the Date Uploaded column now includes a timestamp.

See Document Search

Added "Inactive Task" Field Restrictions

When a task is marked as Inactive, all fields on the Task form now become read-only, with the exception of the Active checkbox. Re-enabling the Active checkbox restores the fields to their previous editable state, ensuring consistency with other Inactive dataform functionality.

Added "Inactive Organization" Field Restrictions

When an Organization record is in "Completed" status or marked inactive, all fields now automatically become read-only, with the exception of th Active checkbox. This prevents further edits or comments from being added to completed or inactive records. If the Organization record is reactivated, the fields return to their previous editable state.

Previously, if an Email Integration incoming email message contained HTML style tags, there were intermittent issues of the style tags displaying in the mapped {EmailBody} Email Replace Field (i.e., field being filled with information from the received email) within ClientSpace.

Now, Email integration automatically strips style tags from incoming messages to prevent formatting artifacts from appearing in the email body. This update also removes excessive vertical white space to ensure a cleaner and more professional presentation of email content.

See Step 3: Field Mapping.

Resolved an issue where newly created lookup fields selected as a Primary Trigger Field or Secondary Trigger Field on a business rule would disappear from business rule after saving. These fields now remain set as both primary and secondary trigger selections upon saving the rule.