Release 165 Notes - July 2026

Added "Mass Update Renew" Feature to Benefits Plan and Benefits Batch Module Dashboards

A Mass Update Renew feature has been added to the Benefits Plan module dashboard (i.e., Benefit Plan Search window) and to the Benefits Batch module dashboard (i.e., Benefits Batch Search window). The feature allows you to flag Benefits Plan and Benefits Batch records for renewal by setting a new Mass Update Renew field on the selected records to Yes. Then, when the Benefits - Mass Update Renew nightly scheduled process runs, any records set to "Yes" are renewed using the renewal logic that is on the Benefits Plan or Benefits Batch.

Note: The Benefits - Mass Update Renew scheduled process is Active by default.

See:

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

• Using the Benefits Plan Mass Update  Feature for Benefits Plan Renewal

Added Benefits Batch "Clone to Child Batches" Action Center Link

A new Clone to Child Batches Action Center link has been added to the Workflow section of the Benefits Batch dataform, allowing you to automatically create or update child company benefits batches from a parent company batch (for eligible child companies).

Note: 

• Eligible child companies cannot have a terminated or inactive Client Master record.

• The parent benefit company is identified as a parent on its Client Master record in the Parent Company field.

This enhancement ensures that child company benefits batches remain aligned with the parent company and helps maintain benefit plan consistency and compliance across related organizations. In addition, this feature can provide a great assist to the Benefit Plan Manager (BPM) workflow. Once a parent batch is approved by the client, you can then automatically create or update child company benefits batches from the approved parent batch.

Note: Please do not confuse this feature with the existing Clone Parent OBPs functionality. While similar, Clone Parent OBPs is available on a displayed child batch and allows you to clone selected Offered Benefit Plan (OBP) records from the identified Benefit Parent Company batch to the child company batch (which must be blank). Additionally, for the process to work, the parent company OBPs must have an Effective Date that matches the Effective Date of the existing blank benefits batch in the child company workspace.

The new Clone to Child Batches feature provides broader functionality. You activate the link from a displayed parent batch. It clones both benefits batch fields (except for the exclusions listed in the related article), benefit groups/codes, and all OBPs that are not in Rejected or Expired Status from the benefit parent company batch to its child company batches, with the goal of creating child batches that fully mirror the parent batch and offer the same benefit plans.

In summary, the Clone to Child Batches feature:

• Creates new child batches that match the parent batch when existing child batches do not share the same Effective Date as the parent batch.

• Updates existing child batches that share the same Effective Date as the parent batch. This includes:

  • Overwriting existing child batch data to match the parent batch.

  • Clearing child field values when the corresponding parent field is blank.

• Synchronizes child batch details, including benefit groups, active OBPs in "Selected" Status, and other fields from the parent batch.

• Logs update failures in the Update Log field of the parent batch.

IMPORTANT: 

• There are plans to clone Additional BPM Contacts in a future ClientSpace release.

• While Benefit Groups and OBPs are being cloned from the parent batch to the child batches as of ClientSpace Release 165, it only occurs on the initial run (i.e., the first time the Clone to Benefits link is clicked). If you were to click the link again on the same parent batch, Benefit Groups and OBPs will not clone. Other batch details, however, will update. There are plans to update OBPs and Benefit Groups from the parent to the child batches on subsequent runs of the Clone to Benefits Process in a future ClientSpace release.

See Cloning Parent Company Benefits Batch Data to Child Company Batches.

Added Global Search Security Entity

A new security entity named GS_Display has been added to the existing PEO Employees role. If the Global Search feature has been implemented by ClientSpace Professional Services, Global Search is visible in the ClientSpace user interface for any user in the PEO Employees role (or any other role where you add the entity) if the GS_Display entity is set to View.

Note: 

• If the Global Search feature is not implemented, Global Search is hidden regardless of entity assignment.

• Only the View access permission must be checked on the GS_Display entity to enable Global Search. Add, Edit, Delete, and Admin access permissions are not applicable.

• Global Administrators do not require the security entity to access Global Search. (The only requirement is that Global Search is implemented.)

See:

• Global Search Configuration

• Standard Security Entities

Added Department Column to Users Dashboard

A Department column (which is visible by default) has been added to the Users Dashboard (System Admin > Resources > Users).

See Users Dashboard.

Updated Forms Functionality to Keep the Parent Form Editable When a Related Form is Opened

Previously, when you opened a related (i.e., child) record from a form, the original form (i.e., parent) became "grayed out" and locked in a read-only state. Now, the original form remains unlocked and editable.

Note:

• This feature is enabled by default but is controlled by a Lock Parent Form App Setting that can be set to the previous functionality upon request by a ClientSpace Professional Services/Support team member.

• Unsaved changes on the original form and related form(s) must be saved independently. Saving parent form edits, for instance, does not automatically save child form edits and vice versa.

• If you update a shared field on a form and the same field on a related open form has been updated more recently, saving the form will fail and display an error indicating that a newer version of the data exists and that the page must be refreshed:

  

  This behavior is consistent with the existing data contention protection that prevents multiple users from overwriting each other's changes on the same record. It now also applies when the same user is working in related parent and child forms that share fields or business logic, helping prevent conflicting updates.

Updated ClientSpace Browser Icon

The ClientSpace internet browser tab has been updated to use the following image:

Added Ability to Save Work Items

You can now save Work Center work items and restore them.

See the Saving Work Items section of theWork Center topic for details.