Release 169 Notes - November 2026

Added Benefit Plan Condition for BPM Links and Disclaimers

BPM links and disclaimers can now display only for the benefit plans they apply to. When you configure a custom link on the Benefits Batch in System Admin > Advanced > Custom Links, a new BenefitPlanCarrierPlanCode field is available in Header Proc 1. For each plan you want to associate with the link, add a condition on this field with the Contains operator and the plan's Carrier Plan Code. The link or disclaimer then displays only when the Benefits Batch includes one of those plans.

See Configuring Links Displayed in BPM.

Updated Code Summary FUTA Calculation

Previously, the FUTA rate in the Pricing Console's Code Summary grid subtracted the state's FUTA Credit Reduction from the FUTA rate. The grid now adds the FUTA Credit Reduction to the FUTA rate, so it matches the FUTA used in the Effective Payroll Load calculation and elsewhere in the Pricing Console.

Note: This changes only the FUTA value displayed in the Code Summary grid. Billing rates and Effective Payroll Load calculations already used this formula and aren't affected.

Updated Export Plans to Prism Link Display Condition

The Export Plans to Prism link in the Benefits Batch Action Center now displays when the batch Status is "Prism Setup", the status of a batch that is ready to export. Previously, the link displayed only when the batch Status was "Active".

Note: The link's display condition was updated only where it was still set to "Active". If your site uses a different condition for this link, it is not changed.

See:

• Exporting Benefit Plans to PrismHR

• Configuring the Benefit Plan API Custom Link

Updated Default Policy on Workers' Comp Claims

When a Workers' Comp claim with a Date of Injury is saved with an empty Policy, or with a changed Jurisdiction State, the system fills in the policy from the Pricing Batch that covers the Date of Injury. To keep outdated Pricing Batch data from assigning the wrong policy, the system now checks that this policy is active and covers the Date of Injury. If it does not, the system checks the policy's renewal chain for the active policy that does.

• If no valid policy is found, the Policy field is left unchanged so you can select a policy.

• A policy you select is not replaced by the default on the same save, even if you also change the Jurisdiction State.

Note: This applies when the Set Default Policy business rule is active for Workers' Comp claims. The rule is active by default but may have been inactivated on your site.

See Administering a Workers' Comp Claim.

Added Benefits Batch Age-Banded Rates Merge

A new Excel merge exports a renewal Benefits Batch to a spreadsheet that includes the age-banded rates of each offered benefit plan that uses age bands. Benefits managers can use it to check a batch before clients review it in BPM. A Banded Rates tab lists the age bands by plan type, with their age ranges and the rate for each coverage level. The RenewalPlans tab also shows the HSA contribution amount and whether the batch includes an accepted Supplemental plan.

Note: The merge record and its Benefits Batch link are not created by default. To use the merge, add both. The stored procedure is included in ClientSpace, but the age-banded Excel template is not. To get the template, log an extranet case or contact Professional Services.

See Benefits Batch Age-Banded Rates Merge.

Added Customer Sentiment to Case Discussion Messages

When a case discussion message is sent with Send Reply, ClientSpace now uses AI to analyze the message text and records the result in the new read-only Customer Sentiment field on the Discussion Message dataform. The value is "Very Negative", "Negative", "Neutral", "Positive", or "Very Positive", from the new Discussion Message Sentiment lookup group. Replies received through Email Integration are not analyzed.

Note: 

• The Customer Sentiment field value displays only on the dataform, not in the Discussions widget or in the discussions opened from a client service case.

• A Sentiment Confidence field, which shows how certain the AI model is about the assigned value, is also added and is inactive by default. To use it, a Global Admin can activate the field from System Admin > Advanced > Dataform Admin > Open Discussion Message > Fields.

See Case Discussions.

Added "Age" Band Type Default for Age Banded Plans

Previously, when Band Type was left blank on an age band, the auto-generated Band Name and Import ID contained extra dashes (for example, "-18-30"), which made bands hard to read. The following changes were made:

• A new "Age" value is available in the Benefits Band Type lookup group. When Band Type is left blank, it now defaults to "Age" on save, so the band name reads "Age-18-30". In BPM, these bands display in their own section when clients view age-banded rates.

• A From Age or To Age of 0 is now included in the band name and Import ID (for example, "Male-0-25").

Note: With this update, a one-time script will run that sets Band Type to "Age" on existing age bands where it is blank and regenerates their band names and Import IDs. No action is required.

See:

• Using Age Banded Plans

• Configuring Age Banded Plan Setup

Updated Group User Assignment on Client Service Case Types

The Default Assignment and Backup Assignment fields on Client Service Case Type records (Admin Workspace > Client Service > Client Service Case Type) now include a "Group User" option for Group Users Assignment (round-robin). Previously, a group user was selected with the "Single User" option, and the Assigned To User list showed group users and individual users together. This made it hard to tell whether a case type assigned cases to one person or to a round-robin rotation. A separate option makes the assignment type clear and lists only the matching users. The following changes were made:

• When "Group User" is selected, the Assigned To User or Backup Assigned To field lists only group users. When "Single User" is selected, group users are not listed.

• When the Default Assignment is "Group User", the Backup Assignment and Backup Assigned To fields are hidden and cleared. A group user can still be selected as the backup for other default assignments.

Note: Existing case types with a "Single User" assignment set to a group user are updated to "Group User" automatically. No action is required.

See:

• Configuring Automatic Assignment of Client Service Cases Using a Group User

• Configuring Case Types

Updated Benefits Import Map Fields

Four benefits import maps that run with the nightly imports are updated so that import files need fewer manual adjustments. The following changes were made:

• Benefits_Batch*.csv: The Batch Type, Effective Date, and Status columns are now required in the import file, and each row must have a value for them.

• Benefits_RateGroup_Tiers*.csv: The Data Type of TierTitle is now "Text" instead of "Checkbox", and each row must have a value for it.

• Benefits_Plan_Base*.csv: The GroupNumber and Product columns are removed from the import map.

• Benefits_Plan_Vision*.csv: The leading space is removed from the import map's source file name, so it matches import files with this name.

Note: If a required value is blank in the import file and no default value is configured, the system issues a validation error. If you have questions about using these import maps, please contact Professional Services.

See Configuring the Import Map Detail.

Added Date Created and Date Updated Columns to Benefits Batch and Benefits Plan Dashboards

The Benefits Batch and Benefits Plan dashboards now display Date Created and Date Updated columns at the end of the grid. Sort by either column to quickly find a batch or plan you recently renewed or changed. The Benefits Batch dashboard also has new Date Created and Date Updated range filters in More Search, matching the Benefits Plan dashboard.

See:

• Benefits Batch Dashboard

• Benefits Plans Dashboard

Updated Employee Benefits Detail Form Date Fields

To support enrollment counts for offered benefit plans in Benefits Batches, the Employee Benefits Detail form now tracks the most recent change to each benefit plan enrollment imported from PrismHR. The following changes were made:

• The Effective Date and Expiration Date fields are renamed Coverage Start and Coverage End on the form and in the Employee Benefits Detail grid.

• A new Recent Effective Date field shows the latest plan detail effective date from PrismHR, including future-dated changes. It updates when premiums, coverage level, or elections change, while Coverage Start keeps the original enrollment date.

• For medical, dental, and vision plans, Coverage Level now reflects the plan detail with the latest effective date.

Note: The PHRAPI_ee_benefits_detail*.csv and PHRAPI_initial_ee_benefits_detail*.csv import maps are updated automatically. No action is required.

See Employee Benefits PHRAPI Import Mappings.

Also see related Case# 79299 and Case# 79300.

Added Rules to Calculate Offered Benefit Plan Enrollment Counts

You can now calculate the coverage counts on Offered Benefit Plans (OBPs) from Employee Benefits Detail records instead of entering or importing them. To update every OBP in a Benefits Batch, click Set OBP Enrollment Counts in the Action Center of a Benefits Batch with an "Active" Status. To update a single OBP, click Set Enrollment Counts in the Action Center of an OBP with an "Active" Status. Each count is the number of active Employee Benefits Detail records linked to the OBP at that coverage level. Records with no coverage level are counted in EOCount.

Note: Each run replaces the values in all five coverage count fields, including counts that were entered manually or imported. A coverage level with no matching records is set to 0.

See:

• Adding a Benefits Batch

• Manually Adding an Offered Benefit Plan

Also see related Case# 79206 and Case# 79299.

Updated DocuSign Email Template Addresses Step

When you configure an email template with the Type of DocuSign on Step 1 (Initial) of DocuSign Email Template configuration, Step 3 (Addresses) now shows only the fields that apply to DocuSign. Since DocuSign sends every request for signature from the DocuSign account's email address and name, the From Address cannot be changed and the Address Source Procedure is not relevant. Therefore, the following fields are now hidden:

• Address Source Procedure

• From Address

Note: When you change the Type of an email template to DocuSign, any existing values in these fields are cleared.

See:

• DocuSign Email Template Configuration Step 3: Addresses

• Configuring the DocuSign email template for In Person Signing

Updated Workflow Task Due Date to Remain Blank When the Source Field Is Blank

When a Workflow Channel or Workflow Channel Item creates a task and the Due Date Source is set to From a Field on a Form, the task due date can now remain blank when the source field is blank. Previously, when the source field was blank, the due date was set to the current date. A blank due date lets you report on tasks that do not have one. This behavior is controlled by the new Allow Empty checkbox in the Due Date Source Options dialog box.

Note:

• Allow Empty is selected by default for new date configurations. Existing date configurations continue to set the current date until you select Allow Empty.

• The task start date is still set to the current date when the source field is blank. Allow Empty is not available for Start Date Source.

See:

• Adding a Workflow Channel - Step 2: Content

• Adding a Workflow Channel Item - Step 2: Content

Added _SetFieldFromRelatedFormFile Business Rule Method

A new business rule method, _SetFieldFromRelatedFormFile, is available in System Admin > Advanced > Manage Business Rules. It copies a file from a File Upload field on a related dataform, regardless of workspace, to a File Upload field on the current record. Previously, _SetFieldFromRelatedForm was used to copy File Upload files, but it sometimes copied a file from a record in a different workspace. Use _SetFieldFromRelatedFormFile for File Upload fields instead. The new method has the same parameters as _SetFieldFromRelatedForm, plus a CopyPinnedFileOnly checkbox:

• When checked, only the pinned file is copied as a new file with its own version history.

• When unchecked, the target field is linked to the source file and all of its versions.

Note: The TargetField and SourceField must both have an element type (i.e., datatype) of "File Upload Manager - Database". Otherwise, the rule cannot be saved.

See Business Rule Methods.

Added Date Created, Updated By, and Date Updated Columns to Admin Dashboards

Global Administrators can now see when a record was created, when it was last updated, and who last updated it on the following dashboards:

• Email Templates (System Admin > Email Templates)

• Custom Links (System Admin > Advanced > Custom Links)

• Business Rules (System Admin > Advanced > Manage Business Rules)

• Field Display Rules (System Admin > Advanced > Manage Field Display, or Field Display Rules in a dataform's Action Center)

Note: The Date Created, Updated By, and Date Updated columns are hidden by default. Add them from the Columns list on any column heading.

See:

• Viewing and publishing email templates

• Searching Custom Links

• Configuring Rules and Business Logic

• Configuring Dynamic Field Display

Updated Set Date and Set Tab Date Business Rule Methods to Support Business Days

The following Set Date and Set Tab Date business rule methods now accept a "b" (business days) date shortcut:

• _SetDateFieldValue

• _SetDateTimeFieldValue

• _SetDateFieldValueFromSourceField

• _SetDateTimeFieldValueFromSourceField

• _SetTabDateFieldValue

• _SetTabDateTimeFieldValue

For example, "5b" sets a date 5 business days later, and "-3b" sets it 3 business days earlier. Business days skip days outside your business week and holidays entered in System Admin > Advanced > Company Holiday. Previously, date offsets counted only calendar time, but did not take business days into consideration.

Note:

• Enter the shortcut in the sFieldValue parameter, or in the OffsetInterval parameter for the FromSourceField methods.

• The business week is set by the Business Week Begin Day and Business Week End Day settings specified in your ClientSpace install. If the business week is not configured, the date is not changed by the business days shortcut. If you have questions about these settings, please log an extranet case or contact Professional Services for assistance.

See Business Rule Methods.

Added Soft Error Date Comparison and Date Between Business Rule Methods

Two new business rule methods, _SE_DateComparison and _SE_DateBetween, are available in System Admin > Advanced > Manage Business Rules. They use the same parameters as the existing _HE_DateComparison and _HE_DateBetween methods, but display a soft error instead of a hard error, so users can click Save Anyway to continue saving the record.

Note: The default messages for the hard error and soft error Date Comparison methods, and the empty-field messages for the Date Between methods, now use "Should" instead of "must" (for example, '[SourceField]' Should have a date that is greater than '[TargetField]'.).

See Business Rule Methods.

Added Allow Empty Option for Workflow Date Fields

When a Workflow Channel or Workflow Channel Item clones a dataform and a date or date/time field is set to From a Field on a Form, the field on the cloned dataform can now remain empty when the source field is empty. Previously, the field was set to the current date. To leave the field empty, select the new Allow Empty checkbox in the field's options dialog box (for example, Date Time (DateTime) Options).

Note:

• Allow Empty is selected by default for new date configurations. Existing date configurations continue to set the current date until you select Allow Empty.

• Allow Empty is also available for the Due Date Source of tasks created by a workflow, but not for the Start Date Source.

See:

• Adding a Workflow Channel - Step 2: Content

• Adding a Workflow Channel Item - Step 2: Content

Updated API Field Configuration with Multi-Selector

Global Administrators can now add and remove multiple API-enabled fields for a pipeline at one time. Previously, fields were added one at a time. After you select a pipeline, you choose fields from a single list instead of repeating the process for each field. The following changes were made:

• The list of fields is searchable and alphabetical, and it shows each field's column name in parentheses. Fields that are already API-enabled for the pipeline are selected, so you can clear a field to remove it.

• Selecting the "All Fields" group selects or clears every field listed.

• If you leave the window with unsaved changes, you are asked to confirm before the changes are discarded.

Note: Fields that are already API-enabled are not affected.

See Configuring API-Enabled Fields.

Added Assigned To User Field to Leave of Absence and EPLI Claim Forms

The Leave of Absence and EPLI Claim forms now include an Assigned To User field, so you can assign a dedicated user to each record, consistent with other forms. The list displays active users with the "PEO Employees" role. The field is in the Disability Details fieldset of the Leave of Absence form and in the Claim Details fieldset of the EPLI Claim form.

See:

• Adding, Editing, or Deleting an LOA Record

• Managing Employment Liability Insurance (EPLI) Claims

Updated Copy Link to Clipboard Confirmation Message

When you select Copy Link to Clipboard from More Options in the Action Center, the message "Link has been copied to clipboard" now displays briefly at the top of the screen and then fades out. You can click the message to close it. Previously, a Clipboard window opened and had to be closed. This applies to dataforms, tasks, workspaces, organizations, and contacts.

See Action Center.

Added Discussion Messages Widget to Client Service Cases

The new Discussion Messages widget lets users read, reply to, and start discussion threads directly from a client service case.

The widget comes in a new Discussion Messages Widget layout for Client Service Cases. The layout is published by default, so the widget displays on cases without any setup, unless another published Client Service Case layout takes priority. If you would rather use your own Client Service Case layout, add the Discussion Messages widget to it and unpublish the Discussion Messages Widget layout.

See:

• Case Discussions

• Widget: Discussion Messages

Previously, saving a security role with a Title longer than the maximum length failed with a generic "something went wrong" error. Now, when you add or edit a role in System Admin > Security > Roles and the Title exceeds 75 characters, a message tells you the title is too long, and the role is not saved until you shorten it. The Title field tooltip now notes the 75-character limit.

Previously, a business rule using the _ModifyFieldValue method failed with an exception when it prepended text to a log field and the new text plus the existing entries exceeded 500 characters. The existing log entries were also cleared. Now the rule prepends the text and keeps the existing entries, regardless of length.

In addition, when the TargetField is a long text field (such as Editor, Log or Text Area field datatypes), Replace fields in the format {DataformName.FieldName} in the Value now return the full text of the source field instead of the first 500 characters. No action is required.

See Business Rule Methods.