Release 152 Notes

Added Ability to Configure BPM Links

You can now configure custom merge/report links or URL links (System Admin > Advanced > Custom Links) on the Benefits Batch dataform which will appear in BPM in any of the following locations (depending on link display conditions):

• The Welcome Page

  

• The Benefits Summary Page

  

• The Signature Page

  

How this can help: A BPM user may need to view benefit carriers while reviewing offered plan selections in BPM. Having a way to jump to a URL from BPM and display it on a separate tab while working in BPM may create a better user experience. Similarly, being able to run a helpful report or merge (such as the Benefits Comparison) from BPM and access the resulting Benefit Comparison spreadsheet from their Windows Downloads folder might be helpful.

Note: 

• BPM links can be accessed by any internal or external BPM user.

• When an external user (i.e., your client) logs in to BPM, they are automatically added to the BPM User role (System Admin > Security > Roles). Likewise, when an internal user logs into BPM using the Internal BPM Access link, they are also automatically added to the BPM User role.

See Configuring BPM Links.

Added Ability to Specify a Benefit Plan Category "Premium Basis" and Display or Hide Relevant Details in BPM Accordingly

A new way to classify plans by Benefit Plan Category Premium Basis has been added. This classification governs how plan information displays in the Benefit Plan Manager (BPM) for each plan type.

This change was made because of the difference in the way contributions and premium amounts are calculated for "Per employee per month" (i.e., PEPM) plans that use tier-based pricing (such as Health, Dental, and Vision) versus Supplemental plans (such as STD, LTD, Life, Legal, and Pet) that do not use tier-based pricing.

How this can help: Previously, the column display favored the presentation of PEPM plans, with fields for total premiums and coverage levels that did not apply to supplemental plans. Now, with proper designations of the Premium Basis for each plan type, only necessary details will display for each plan type, resulting in a better user experience, particularly when viewing supplemental plan details.

To support this enhancement, the following changes were made:

• Added a new lookup group named Benefit Premium Basis containing the following lookup values for plan classifications:

  • Per $10,000 of coverage

  • Per $1,000 of salary

  • Per employee per month

• Added a new metadata field Benefit Plan Category Lookup Detail records named Premium Basis in the "Additional Settings" fieldset. This field displays the lookup values from the Benefit Premium Basis lookup field in a drop-down list as metadata. It is where you assign the Premium Basis for each plan. In the examples below, you see that the Life Plan has been assigned "Per $1,000 of salary" and the Health plan has been assigned "Per employee per month".

  

  

In BPM:

• On the Group Summary > Summary tab, a new field label displays next to the Plan Type. Also, if the assigned Premium Basis is not PEPM, the Total Premium column displays "N/A".

  

• On the Selection Summary page, a Premium Basis column has been added which displays the Premium Basis assignments for each plan.

  

See Configuring the Benefit Plan Category Premium Basis.

Added Plan Title Hidden Column to Benefits Batch OBPs Search Dashboard

A Plan Title column (which is hidden by default) has been added to the Benefits Batch OBPs Search Dashboard. Display it by clicking the vertical three dot menu (i.e., kebab) icon next to any displayed column, selecting Columns and then selecting Plan Title.

How this can help: This column can help you verify which plan selections you are updating before using the Mass Update feature.

See Using Mass Update from Benefits Batch OBPs Search

Made Benefits Batch a Required Field on OBP

When adding an Offered Benefit Plan (OBP), the Benefits Batch field is now required and the field value defaults to the current Benefits Batch.

See Manually Adding an Offered Benefit Plan.

Added "Date Last Renewed" Field and Hide Renew Link on Already Renewed Master Benefits Plans

Previously, if you clicked the Renew link on a master Benefits Plan that had already been renewed, a duplicate renewal plan was created. Now, the following changes have been made to the Benefits Plan renewal process to prevent duplicate renewal plans from being created:

• A "read only" Date Last Renewed field has been added to the Benefits Plan dataform.

• When you click the Renew link in the Action Center, the Date Last Renewed field on the plan is auto-filled with the current date and time and the Renew link is hidden.

• When the new plan is generated, it has a blank Date Last Renewed field so that the process of tracking the Date Last Renewed and hiding the Renew link carries forward with every Benefits Plan renewal.

SeeRenewing a Master Benefits Plan .

Made Employer Contribution Fieldset on OBPs Always Visible

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 Employer Contribution fieldset is visible and accessible on OBPs.

SeeManually Adding an Offered Benefit Plan.

Removed "Link 2" as a Group Option in Custom Link Configuration

After an extensive analysis of ClientSpace code to ensure that Link 2 is not used in any stored procedures or code paths, the Link 2 option has been removed from the list of valid selections under Group in custom link configuration (System Admin > Advanced > Custom Links.

Note: Link 2 items were once used to help set the display order of items in the Links section of the Action Center. Items in the Link1 Group displayed at the top of the section and items in the Link 2 Group began after the last item in the Link 1 Group. This was for configurations where it was important to have a group of links that appeared first (in any order, as long as they appeared before the items in the Link 2 Group). However, this confused users, was seldom used, and the same result can easily be achieved by applying a Sort Order to each item.

If any of your existing custom links were configured for Link 2, they will now be converted to Link 1 and resorted. The new sort order respects that items in the Link 2 Group have always displayed after items in the Link 1 Group, which allows the existing display order of your links to be preserved.

See Configuring Custom Dataform Links .

Made Source/Field Source Values Consistent on Custom Links and Field Display Configuration

Previously, when configuring a custom link(System Admin > Advanced > Custom Links, one of the options in the Source field was "Form Data". When configuring a field display rule (System Admin > Advanced > Manage Field Display), one of the options in the Field Source field was "This Table". "Form Data" and "This Table" mean the same thing. Now, "This Table" has been changed to "Form Data" on the Field Display Rule Detail form so that the drop-down lists in both locations are consistent.

How this can help: If you use keyboard shortcuts on ClientSpace forms to quickly filter drop-down lists and make selections, this could result in a small efficiency gain when setting up custom links and field display rules as you no longer have to recall which form uses which value when specifying a source in a custom link condition expression or a field display rule. You can now type "f" for "Form Data" in both places.

See Configuring Dynamic Field Display.

Added Two Columns to the Department Search Grid

The Parent Department and Member Org Access columns have been added to the Department Search grid (System Admin > Departments). Both columns are visible by default.

Added Business Rule Methods to Validate Character Limits on Dataform and Associated Tabbed Dataform Text Fields

Two new CORE validation business rule methods (System Admin > Advanced > Manage Business Rules) have been added to validate the character limits of text fields on dataforms and associated tabs, respectively:

• _HE_ValidateFieldOnForm

• _HE_ValidateTabField

If you create a business rule to validate a field by one of these methods, the rule is triggered when a user enters a value greater than the MaxLength value defined on the business rule and clicks Save or Apply. One of the following hard error messages displays, depending on the method used:

For _HE_ValidateFieldOnForm: The {TargetField} field on form table gen_{TableName} has exceeded the maximum allowable length of {XXX} characters, and cannot be saved. Please adjust the field to an appropriate length before saving.

For _HE_ValidateTabField: The {fieldname} field on {TabTableName} dataform has exceeded the maximum allowable length of {XXX} characters, and cannot be saved. Please adjust the field to an appropriate length before saving.

How this can help: If you use an API, such as SIDES, where you export text values entered on ClientSpace forms, values that are over the maximum character length allowed may be truncated. Requiring a user to evaluate and shorten the data before it is exported allows the user to ensure that meaningful information is exported and this may reduce the likelihood of needing to export corrected data later.

See Business Rule Methods.

Added Ability to Display a "Friendly Name" in Place of the Tab Label Name on Dataforms

Previously, when you added a form as a tabbed dataform to a related parent form, there was no way to display a "user-friendly" or alias name as the tab name on the parent dataform. Now, a new field named Tab Friendly Name has been added to Dataform Properties - Tabbed Forms (System Admin >Advanced > Dataform Admin > Action Center > Tabbed Forms). This value displays on the tab when the form is added as a tabbed dataform to a related parent form.

How this can help: The Tab Friendly Name displays in place of the dataform name, potentially creating a better user experience.

The Tab Friendly name has also been added to the Tabbed Forms search window as a hidden column. Display it by clicking the vertical three dot menu (i.e., kebab) icon next to any displayed column, selecting Columns and then selecting Tab Friendly Name.

SeeAdding Dataform Tabs.

Added Ability to Add Lookup Values from a Lookup Group

Previously, when you added a new lookup field, you had to add the Lookup Group and then navigate to a different screen to add the lookup values to the group. Now, there is a Lookup Values link on the Lookup Group Details page that redirects you to the Lookups page where you can add the lookup values to the group without having to navigate away from the Lookup Group record.

Note: The Lookup Values link features a badge counter showing the number of Active lookup values. A symbol next to the count indicates that an Archived (i.e., Inactive) value is present (though not included in the count.) Hover the mouse pointer over the badge to view the number of archived values.

How this can help: This provides greater efficiency and a better user experience when adding and managing lookup fields.

See Configuring Lookups.

Disabled "Show On Landing Page" on PFML - Config Dataform Properties

The Show On Landing Page option has been disabled on the PFML - Config dataform properties (System Admin > Dataform Admin) to discourage the use of PFML state compliance tracking functionality in unsupported states. This prevents the PFML - Config dataform from showing up in the dataform search at the bottom of a workspace landing page.

Note:

• The PFML - Config dataform can be accessed on the Admin Workspace by Global Administrators via dataform search in the Action Center.

• Currently, only Delaware PFML state compliance tracking is supported. We plan to add support for additional states in upcoming releases.

See Selecting PFML States.

Inactivated Unused Fields in PrismHCM Import API Initial and Ongoing Data Mapping Configuration

The following fields have been inactivated in the PrismHCM Import API Initial and Ongoing Data Mapping Configuration as they no longer appear in the HCM user interface.

Company

In HCMAPI_initial_company*.csv and HCMAPI_ongoing_company*.csv:

• Description of Operations

• Date of First Payroll

Division

In HCMAPI_initial_division*.csv and HCMAPI_ongoing_division*.csv:

• Address 1

• Address 2

• City

• State

• Zip

Employment

In HCMAPI_initial_employment*.csv and HCMAPI_ongoing_employment*.csv:

• Standard Hours Per Period

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

Added Ability to Configure Email Template to Include or Exclude "Immediate Supervisor" as Recipient

A Supervisor column has been added to Step 3: Addresses of Email Template Configuration. When you select any internal user field (such as User, Role, Project User, etc.) as a recipient in the Address column with either a dataform or "Current User" as Source, the Supervisor column becomes enabled. Once enabled, when you click in the Supervisor column on a line item in the grid, a drop-down menu displays:

You can select one of the following options from the drop-down list of the Supervisor column:

• Exclude: Do not include the user's supervisor on this email.

• Include: Include both the user and the user's supervisor on this email.

• Supervisor Only: Include only the user's supervisor on this email.

Note: If you select Include and no supervisor is associated with the user or there is no valid email address, the email will only be sent to the recipient identified in the Address column. If you select Supervisor Only and no supervisor is associated with the user or there is no valid email address, the email will not be sent for the affected recipient record.

See Step 3: Addresses.

Added Visual Indicator on Invalid Drop-Down Field Values

Invalid drop-down field values now display in red text in the field as well as in the drop-down. This includes multiple types of drop-down field values in the system, such as lookup, parent form, and user list values.

In the example below, the Lookup Group in the dataform field properties was changed from Gender (with valid values of Male and Female) to YesNo (with valid values of Yes and No). "Male" had been previously selected in the field before the Lookup Group was changed. Now, "Male" is an invalid value and is displayed in the field in red text. It is also displayed in the drop-down list as a highlighted value in red text:

If you correct the Lookup Group in the dataform field properties, the value is no longer invalid and no longer displays in red text.

How this can help: Users can quickly identify invalid values in a drop-down field (such as a lookup, parent form, or user field) and report them to a Global Administrator for correction.

See Deleting, Inactivating or Editing Dataform Fields.

Previously, the text in the summary heading of "Critical" Inbox messages was cut off at 100 characters. Now, when the announcement Priority of a message is set to "Critical", the summary is not truncated.

As of February 17th, 2025, Microsoft officially shut down support for Legacy Exchange Online Tokens. These tokens were essential for retrieving attachment data when posting emails from the Outlook Add-in to ClientSpace. Looking ahead, by June 2025, these legacy tokens will be fully deprecated, requiring a mandatory transition to Nested App Authentication (NAA). This change has caused a significant issue: When users attempt to post emails with attachments, the attachments are no longer included in the submission. To address this, a fix is being deployed.