Release 156 Notes

R156 Sprint: 9/1/2025 to 9/30/2025. 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.

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/2025 to 9/30/2025

Upgrade groups

Date of upgrade

Tentatively occurs on
Group 1 First Thursday of the month October 14, 2025
Group 2 Second Tuesday of the month October 21, 2025
Group 3 Third Tuesday of the month October 28, 2025

Enhancement

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

Announcements

We are excited to let you know that we are preparing to roll out Sigma! To help ensure a smooth transition from Izenda to Sigma, please take a moment to archive any unused reports.

To get up to speed with Sigma, we encourage you to attend an upcoming Report Center Conference or watch the Sigma Jump Start Training videos.

ClientSpace Premium

Benefit Plan Manager (BPM)

Case

Enhancement

72467

Updated the Benefits Summary Tab UI to Add Filters and Support for "Supplement Plan Only" Benefits Groups and Batches

Previously, if you had a Benefits Group or an entire Benefits Batch consisting of only supplemental plans (i.e., no tier-based Health, Dental, or Vision plan categories), the Benefits Summary tab of BPM was not accurate as it was configured to display "Per employee per month" (PEPM) tier-based plan calculations. Now, the following changes have been made to the BPM user interface to better support displaying all plans, including "supplemental plan only" Benefits Groups or Batches:

  • The Benefits Summary tab now has two sub-tabs: Base and Supplemental. The Base tab displays tier-based plan calculations. The Supplemental tab displays supplemental plan calculations.

  • The display rules for the Base and Supplemental tabs are as follows:

    • If the Benefits Batch contains a mix of tier-based and supplemental plans, both the Base and Supplemental tabs display.

    • If the Benefits Batch contains only tier-based plans, only the Base tab displays.

    • If the Benefits Batch contains only supplemental plans, only the Supplemental tab displays.

  • The Benefits Summary tab also contains a new "Filters" section containing filter drop-down lists for Summary Type, Category (i.e., plan categories such as Health, Dental , Vision, Other, etc.), Group (i.e., Benefits Group name), and Include New Plans.

    • The filters are set to display all plan categories and benefits groups in the batch by default.

    • The default Summary Type is Total Premium when you are viewing the Base tab. The default value (and only available value) is Employee Contribution when you are viewing the Supplemental tab.

    • Include New Plans defaults to No. This means that only plans in Selected status are included in the Benefits Summary calculations. on the Base and Supplemental tab grids.

See BPM Option 1: Reviewing, Selecting, and Approving Benefits With Prior Batch History and BPM Option 2: Reviewing, Selecting, and Approving Benefits - No Prior Batch History.

73658

OBPs Containing All New Plans Now Display in Benefits Summary

Previously, if a new Benefits Group containing all new Offered Benefit Plans (OBPs) was added to a renewal Benefits Batch, the Benefits Group did not display in the BPM Benefits Summary unless one plan was in "Selected" status. Now, Benefits Groups where all OBPs are in "New" status display on the BPM Benefits Summary.

Note: If all plans in a Benefits Group are in "New" status, you must set the Include New Plans filter on the Benefits Summary to Yes for the group to display. See related Case# 72467.

See BPM Option 1: Reviewing, Selecting, and Approving Benefits With Prior Batch History and BPM Option 2: Reviewing, Selecting, and Approving Benefits - No Prior Batch History.
72682

Added Prospect Login Capability

Previously, BPM end users could only log in with their Client Number. Now, login functionality has been expanded to allow prospect/RFP users to enter an ID to login. The ID is the Benefits Batch ID. You can find it in the Administrative Fields fieldset of the Benefits Batch dataform:

Note: Only Global Administrators and users with Admin rights can see the Administrative fields.

A new BPM Prospect email template is used for prospect/RFP. It includes a BPM access link that prompts for the ID on the login window instead of the Client Number.

The email template is configured to trigger when all of the following conditions exist:

  • Benefits Batch Status = Client Review

  • Benefits Batch Status "Is Dirty" (i.e, the field value changed or was updated.)

  • Benefits Batch Open To BPM = Yes

  • Benefits Batch Type = Prospect

Note: 

  • The BPM Prospect email template is Inactive by default. It must be flagged Active and published before first use.

  • The ID is included as a Replace field in the default body text of the email template. The Replace field name is {gen_BenefitsBatch.pkBenefitsBatchID}.

See:

Other ClientSpace Premium

Case

Enhancement

72664

Plan Design and Prism Coverage Level Field Values Copy from Model Plan to New Plan

When adding a new client-level Benefits Plan, when you select a plan from the Model Plan drop-down list, in addition to the plan details which were already copying to the new plan from the selected model plan, all model plan values present in the "Plan Design" and "Prism Coverage Level" fieldsets are also copied to the new plan.

See Adding a Benefits Plan.
72683

Added the Ability to Identify a Client-Level Base Plan to Populate the Model Plan Field on Benefits Plan Dataform

Previously, the Base Plan checkbox on the Benefits Plan dataform had no functional impact in ClientSpace. Now, when the Base Plan checkbox is checked on a client-level plan, the benefit plan is added to the Model Plan drop-down list on the Benefits Plan dataform.

 

How this can help: Master plans from the Admin Workspace as well as other client-level plans flagged as a Base Plan are now available in the Model Plan list of plans to copy from when you add new, client-level plan.

See Adding a Benefits Plan.
73311

Updated "Suppress From Presentation" Options

Previously, the "Suppress From Signature Page Only" and "Suppress From Plan Selection & Contributions Only" Suppress From Presentation options were configured to work with BPM only. Now, these options have been updated to allow you to exclude a benefit plan from the Benefits Renewal DocuSign Approval merge and the Benefits Renewal Workbook merge.

 

Suppress From Presentation field options are now defined as follows:

  • Suppress From Entire Presentation - Removes this plan from all locations in BPM and from the Benefits Renewal Workbook merge.

  • Suppress From Signature Page Only - Removes this plan only from the Signature Page in BPM and the Benefits Renewal DocuSign Approval merge.

  • Suppress From Plan Selection & Contributions Only - Removes this plan from the Plan Comparison and Summary pages in BPM and from the Benefits Renewal Workbook merge.

Note: Since suppression options can apply to multiple areas, including the Benefits Renewal Workbook merge, the Benefits Renewal DocuSign Approval merge, and BPM, carefully review the option definitions to ensure you are selecting the correct item.

See Benefits Renewal Merge and BPM Benefit Plan Suppression.
73896

Removed OPB Field Display Rule to Hide Employer Contributions

Previously, when "Standard Deductions" was selected in the Benefit Plan Category lookup, the Employer Contribution section on the associated Offered Benefit Plans (OBPs) displayed. Now, the field display rule has been removed from "Standard Deductions" so that the Employer Contribution fieldset is always visible and accessible on OBPs.

73958

Added OBP "Cancel" Workflow Link and Business Logic

A Cancel workflow link has been added to the Action Center of the Offered Benefit Plan (OBP) dataform. The link is always pinned open. When the link is clicked, the following confirmation message is displayed:

Are you sure you want to Cancel this Benefit Plan?

If you click OK, the OPB is inactivated and set to a Status of Cancel. The inactivated plan will not show in Benefit Plan Manager (BPM), the Benefits Renewal Workbook merge, or the DocuSign Benefit Renewal Merge.

To support this change, a Cancel lookup value was added to the OBP Status field and the following two business rules were added:

  • Set OBP Status to Cancel - Sets the OBP to Cancel when the Cancel link is clicked. Uses the _SetFieldValue business rule method.

  • Inactivate OBP on Cancel Status - Inactivates the OBP when the Status is set to Cancel. Uses the _SetFieldValue business rule method.

See Offered Benefits Plan Status Definitions.

Advanced Administration and System Administration

Case

Enhancement

67387

Added "PreferredName" to PrismHR Initial and Ongoing Import API

An Employee PreferredName column has been added to PrismHR Initial Import and Ongoing Import mapped fields. A Preferred Name field has also been added to the "Employee Detail" fieldset of the Employee dataform Home page:

71220

Updated _ModifiyFieldValue Method to Display Custom Datatype Decode Values

Previously, the _ModifyFieldValue business rule method set the code value instead of the decode value for custom datatypes.

Note: The Code is a typically shorter and not as descriptive "behind the scenes" value while the Decode is the more descriptive display value.

Additionally, #ThisForm could be used as the TargetForm, but choosing to enter the name of the current form (i.e., the form listed in Table Name) as the TargetForm instead of using #ThisForm did not work. This issue has been corrected.

Note: 

  • The _ModifiyFieldValue business 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.

71905

Updated Import Map Search Dashboard to Improve Import Map Detail Record Management

The Import Map Search dashboard has been updated with new columns, additional More search options, and a Mass Update feature.

Note: The Import Map Search page is accessed by going to System Admin > Advanced > Configure Import, opening a map header record, and then clicking the Fields in the right pane

The following new columns were added:

  • Data Type

  • Required Column

  • Required Value

  • Default Value

  • API Path

The following additional More search options were added. All options are "Equals" searches:

  • Location

  • Field

  • Data Type

  • Default Value

  • Required Column

  • Required Value

The Mass Update interface (which is accessed by clicking the Mass Update button on the Import Map Search dashboard) contains the following fields:

  • Active - Sets the Active checkbox to Yes (i.e., checked) or No (i.e., unchecked).

  • Required Value - Sets the Required Value checkbox to Yes (i.e., checked) or No (i.e., unchecked).

  • Required Column - Sets the Required Column checkbox to Yes (i.e., checked) or No (i.e., unchecked).

See Mass Update Import Map Detail Records.
72840

Updated Business Rule to Create Third Party Application User ID for Users Imported from PrismHR

The CreateTPAUser business rule (which uses the business rule method named CreateTPATSSOUSER to add a PrismHR user based on the Secondary ID) has been updated (System Admin > Advanced > Manage Business Rules). Now the rule is Active by default and Execution Pipeline is set to All Pipelines.

See Business Rule Methods.

72947

Added "Department Manager" as Case Type Default Assignment and Backup Assignment Option

You can now select "Department Manager" as the Default Assignment or Backup Assignment on a Case Type record.

When "Department Manager" is selected, the system evaluates the Case Category metadata and uses the manager of the responsible department.

See Configuring Case Types.

74069

Added a Contact Source Dialog in Workflow Channels

Previously, when there was a cloneable Contact field on a dataform, in Workflow Channel configuration, you could only clone the Contact field with a specific contact value or leave it blank to clone the field with no value to the dataform. Now, a Contact Source dialog (which works like other Workflow Channel field cloning dialogs such as those for Lookups, Multi-Lookups, Dates, and Users) has been added. It displays when you click the link for the Contact field in Workflow Channel Item Configuration Step 2: Content:

The dialog allows you to select the following cloning options:

  • None: Leaves the contact field blank. A user would have to select a contact on the new dataform cloned by the workflow, if applicable.

  • Specific Contact : Allows you to clone a specific value to the contact field of the new dataform cloned by the workflow.

  • From a Field on a Form : Allows you to specify a field on a parent or child dataform. The value in that field is cloned to the new dataform cloned by the workflow.

Note: To use this feature, the Contact field (i.e., any field with a datatype / dataform field Element Type of Org Contact, Contact, or Contact Typeahead) must be configured in the Dataform Admin field properties as Cloneable and the Triggered Form dataform properties must have the Enable WFC Cloning field enabled (i.e., the dataform must be configured as a clone-configurable dataform.)

See Step 2: Content.

74076

Added Workflow Channel and Email Template Primary Contact Email Replace Field

In Workflow Channel and Email Template configuration, the primary contact email address Replace Field now becomes available when the channel trigger dataform (Triggering Form field) contains a field of one of these datatypes: Org Contact, Contact, or Contact Typeahead.

The new field appears in the Replace Fields list (Step 2: Content > Get Replace Fields of Workflow Channel Configuration) and (Step 2: Content > See Replace Fields of Email Template Configuration) using following naming convention: {TableName.FieldName.Email1}

For example, if a Contact field was on the Customer Data form, the Replace Field would be listed in the Customer Data section of the Replace Fields window and named as follows: {gen CustomerData.fkPreFilledContactID.Email1}

See Replacement Fields.

74113

Added "EESource" to HCM Initial and Ongoing Import API

The EESource column has been added to HCM Initial Import and Ongoing Import mapped fields.

See ClientSpace Data Mapping for the HCM Initial Import API and ClientSpace Data Mapping for the HCM Ongoing Import API.

74295

Updated Allow International Phone Number Flag to Work on Client Master and Pricing Console Organization Phone Number

Previously, the Allow International Phone Numbers on CRM forms checkbox in App Settings (System Admin > Advanced > App Settings) only worked to change Phone datatype fields on CRM forms (i.e., Contact and Organizations). Now, this functionality has been updated to also include the organization's phone number on the Client Master and Pricing Console.

  • On the Client Master, this is the Phone field in the "Company Information" fieldset of the Client Master.

  • On the Pricing Console, this is the Phone field that displays in the "Company Information" fieldset of the Pricing Console when you click the Edit button within the fieldset.

 

When the Allow International Phone Numbers on CRM forms checkbox is checked, the affected Phone datatype fields function as a free text entry fields, with no validation of the data, to allow international phone number input.

 

Note: Only Developer Users can access App Settings. If you need this feature, please contact your ClientSpace Professional Services representative or log an extranet ticket.

SeeConfiguring Dataform Datatypes.

General User Enhancements

Case

Enhancement
66591

Added PowerPoint Merge

You can now run any existing Word or Excel merge procedure as a PowerPoint mergeClosed A ClientSpace merge gives our customers the ability to merge specific data from the ClientSpace system dynamically into your business documents and forms, removing the need for manual completion of forms, such as a Request for Proposal (RFP) or Client Service Agreement (CSA). Merges are available in Word, Excel, PDF and PowerPoint format. by changing the Type and Output Type fields on the Merge Admin Detail form (System Admin > Outputs > Merges) to PowerPoint. You can also create (or receive assistance to create) a custom merge procedure.

Use the PowerPoint merge feature to create a PowerPoint (.PPT) file containing text, charts, images, tables, audio, and video files. However, the creation of slides with charts, tables and media may require configuration assistance from the ClientSpace Professional services team.

How this can help: This feature can be helpful for presenting Sales data from ClientSpace.

You can easily insert text on a slide without making any modifications to an existing procedure when the Procedure file on the Merge Admin Detail record contains single value text fields. To insert text, you would:

 

Step 1: Add replacement fields (i.e., placeholder fields) wrapped in elbow brackets << and >> in your PowerPoint (.pptx) project like this example : <<EmployeeName>>. (Click Show Procedure Fields under Links in the Action Center of the Merge Detail Admin record to see the available procedure fields and get the field names.)

Step 2: Save the PowerPoint project containing the placeholder fields and upload the PowerPoint file (.pptx) to the Template File field of the Merge Admin Detail record.

Step 3: Run the merge. (You can configure the merge to run when you click a custom link on a dataform in the Action Center under Reports as shown in the example below or you can configure it to run when triggered by a workflow action such as saving a dataform.)

Once the merge is run, the field data from ClientSpace is added to your PowerPoint presentation as shown in the example below. You can retrieve the PowerPoint file generated by ClientSpace (named the same as your Template file name) from your Windows Downloads folder and open it in the PowerPoint application to view the merged data and continue editing the presentation.

IMPORTANT: For more advanced PowerPoint presentations containing slides with charts, tables and media such as audio, video, or image files, if you are a Global Admin and you know how to create or modify a merge procedure to add the desired elements to the stored procedure and link the procedure to the Merge Admin Detail record, steps are covered in the referenced Help Center article. If you are unable to customize or create a merge procedure for a PowerPoint presentation on your own, please log an extranet case for assistance.

 

Note: 

  • Some procedures may already contain image fields. They must have a column name prefix of IMG_.

  • Table, chart and media files used in a PowerPoint presentation must have a column name prefix of TABLE_, CHART_, AUDIO_, or VIDEO_.

  • Any table, chart or media file used in a PowerPoint presentation field that does not contain the correct column name prefix in the stored procedure is treated as a text replacement field.

Here is an example field listing of procedure modified to include a table, chart, video, audio file, and images.

Note: Some video and audio files may be incompatible. Please refer to the following Microsoft article: Video and audio file formats supported in PowerPoint.

 

See PowerPoint Merge.

 

Video

Also view the "Learning How" video on Creating a PowerPoint Merge.

Performance

Case

Enhancement

72258

Refactored a Project User Table Process to Improve Performance

A Project User Table process was refactored to improve long run times when adding new template users to a template workspace. Now, users are added to the Project User table when added directly to a template workspace, or when created from a template user that is a user in the template workspace.

74354

Changed Audit Tracking on the Scheduled Process Table to Improve Performance

Audit tracking on the scheduled process table previously tracked all updates to the table which resulted in longer scheduled process kickoff times. Now, to improve performance, only the following is tracked:

  • The Administrative fields of Date Updated and Updated By are only changed when a scheduled process record is saved. Date Updated is no longer changed when the scheduled process is run.

  • When a scheduled process is run, the Last Run Date field (located on the Scheduled Process Admin dashboard) is both the scheduled process start time and end time.

  • A field named Last Run By (LastRunByUserID) has been added to the Schedule Process detail form. It stores either the Admin User ID (or the User ID of a developer who clicked Run Process to manually kick off the scheduled process.)

Technical Enhancements

Case

Enhancement

71744

Corrected Inconsistencies in User Display

In some areas within ClientSpace, users displayed as the Login ID only. Now, users display with the following details: <lastname>, <firstname> <dept> <status>.

Note: Status only displays when the user is out of office or expired. "OOO" or "Expired" is shown, respectively.

These changes were made in the following areas of ClientSpace:

  • Add Role Users drop-down: System Admin > Security > Roles > Open Role Record >Action Center > Users > Add (Add Role Users drop-down)

  • Ad Hoc Profile Users grid: System Admin > Security > Reporting Profile>Edit> Action Center > Users (Ad Hoc Profile Users grid)

  • Add Profile Users drop-down: System Admin > Security > Reporting Profile>Edit> Action Center > Users (Ad Hoc Profile Users grid) > Add (Add Profile Users drop-down)

  • Business Intelligence Admin grid: System Admin > Outputs> Business Intelligence (Business Intelligence Admin grid)