Release 144 Notes

R144 Sprint: 9/2/2024 to 9/30/2024. 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.

Click to view the R144 release schedule.

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/2/2024 to 9/30/2024
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	October 15, 2024
Group 2	Second Tuesday of the month	October 22, 2024
Group 3	Third Tuesday of the month	October 29, 2024

Enhancement

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

ClientSpace Premium

Case

Enhancement

65207

Added Risk Module User Template

Important: To preserve customers' existing configurations, the changes below will not impact sites who are already using the Risk module.

A default Risk module user Template has been added to (System Admin > Users). It contains default settings, including user profile settings, module assignments, role assignments, and license settings for new Risk module users. This was done to make future Risk module setup quicker.

65216

Added Risk Module Widget Layout

Important: To preserve customers' existing configurations, the change below will not impact sites who are already using the Risk module.

A new widget layout named Workspace Landing Page (Risk) has been added to support quicker Risk module installations. It includes the WC Claims widget at the bottom of the new layout.

65219

Added Risk Module Home Page Dashboard

A new Risk (Home) widget layout is available that functions as a Risk Home Page Dashboard for users in the Risk_Member role.

The Risk Home Page Dashboard displays:

Claim statistics in an easy-to-read tile format.
A table showing the Top 500 most recently created claims.

Note: Click any column header in the table to sort by that column.

Note: The layout is inactive by default (i.e., unpublished). A global administrator must publish the layout to make it available. Additionally, only users with a Risk_Member role assignment can see the layout listed under Action Center > Home Pages and apply the layout.

See Risk Home Page Dashboard.

65246

Updated Risk Module Role Permissions

Important: To preserve customers' existing configurations, the change below will not impact sites who are already using the Risk module:

Additional security entities were added to the Risk_Member and Risk_Admin roles (System Admin > Users > Roles) to make future Risk module setup quicker.

66632

Added New Default Widget Layouts and Widgets for Benefits Plan and Benefits Batch Dataforms

Previously, the widgets at the top of the Benefits Plan and Benefits Batch dataforms were BI reporting widgets. (See Configuring BI Reporting Widgets.)

Now, there are two default Widget layouts containing pre-configured product widgets for the Benefits Plan and Benefits Batch dataforms. The new widgets replace the BI reporting widgets and feature optimized performance over the BI Reporting Widgets.

See Default Benefits Widget Layouts and Widgets.

67441

Inactivated Old OSHA Lookup Values

Important: To preserve customers' existing configurations, the change below will not impact sites who are already using the Risk module.

Any OSHAYear lookup value (System Admin > Lookups) more than two years in the past has been inactivated. This was done to make future Risk module setup quicker.

Note: Prior years are still available, but inactive.

67449

Updated Risk Module Field Display

Important: To preserve customers' existing configurations, the changes below will not impact sites who are already using the Risk module.

Two changes were made to Risk module field display rules:

On the Comp Claim dataform, when the Claim Type field value = Indemnity, the Comp Claim Legal tab displays.
On the Third Party Administrator dataform, when the Transmission Method field value = API, the Claim Transmittal fieldset displays.

67474

Updated Merges, Reports and Links for Risk Implementation Group

The following changes were made to merges, reports and links in the Risk Implementation Group to make future Risk module setup quicker.

Important: To preserve customers' existing configurations, the changes below will not impact sites who are already using the Risk module:

Location of Change	Change
System Admin > Outputs > Merges	Made the OSHA 301 merge record active by default.
System Admin > Advanced > Reports	Made OSHA 300 and OSHA 300A reports active by default.
System Admin > Advanced > Custom Links	Checked the Pinned Open flag on the following links: Employee dataform: WC Claims Client Location dataform: Location OSHA Totals Comp Claim dataform: Retrieve Vouchers Comp Claim RTW History: Change Status Made the following links inactive: Comp Claim dataform: All links with a display value beginning with "FROI". Comp Claim dataform: All links with a display value beginning with "Wage Statement". Added the following new links: Workspace Landing: OSHA 300 Workspace Landing: OSHA 300A Comp Claim dataform: Send FROI Applied the security lock setting (using the Action Center Lock icon) and secured the following links to the Risk Member Group: All OSHA 300 links in all locations All OSHA 300A links in all locations
System Admin > Implementation Groups > Manage Features	The Risk Implementation Group has been added to the following links on the Implementation Features form: Client Location > Link1 > Location OSHA Totals Comp Claim > Action > Retrieve Vouchers Comp Claim RTW History > Action > Change Status Workspace Landing > Link1 > OSHA 300 Workspace Landing > Link1 > OSHA 300A Comp Claim > Action > Send FROI

68464

Added Benefits Batch Process Enhancements to Support the Benefits Batch Renewal Process

Important: To preserve customers' existing configurations, the changes below will not impact sites who are already using the Benefits module.

The following changes have been made to support the Benefits Batch renewal process:

Added a new Date of Approval field in the Batch Details fieldset of the Benefits Batch dataform. This is a read only date field that auto-fills when the Benefits Batch Status is set to Approved.
Added seven (7) new lookup values to the Benefits Batch Status lookup group. These statuses are set when you click the corresponding Workflow links in the Action Center or when you manually select them from the Status drop down list on the Benefits Batch:
- Prep For Presentation - Used to indicate that you are preparing OBPs to present to the client.
- Client Review - Used to indicate that you are in the process of reviewing OBPs with the client. Also triggers the Client Benefit Workbook Review email template.
- Update Client Selection - Used to indicate that you are in the process of updating the client's selected benefits for the year.
- Sent For Approval - Used to indicate that you have sent the client's benefit renewal selections that you have updated in ClientSpace back to them for approval.
- Approved - Indicates that you have received approval from the client on their benefit renewal selections.
- Prism Setup - Indicates that you are in the process of setting up the selections in the PrismHR application.
- Pending Activation - Indicates that the approved benefits are ready to be activated.
The changes appear in the Status drop down field on the Benefits Batch dataform.
Updated the display order of the five (5) existing Benefits Batch Status lookup values and set a display order on the seven (7) new Benefits Batch Status lookup values referenced in the previous bullet.
Added a Cancel lookup value to the Benefit Plan Selection Status lookup group and set the display order so that it appears last in the drop down list. The change appears in the Status field of the OBP dataform.

Note: Selecting Cancel inactivates the OBP.
Added eight (8) new Workflow links to the Benefits Batch Action Center.
- Prep For Presentation -Displays when the value in the Benefits Batch Status field equals Pending.
- Client Review -Displays when the value in the Benefits Batch Status field equals Prep for Presentation.
- Update Selections - Displays when the value in the Benefits Batch Status field equals Client Review.
- Send For Approval - Displays when the value in the Benefits Batch Status field equals Update Client Selection.
- Approved - Displays when the value in the Benefits Batch Status field equals Sent for Approval.
- Prism Setup - Displays when the value in the Benefits Batch Status field equals Approved.
- Pending Activation - Displays when the value in the Benefits Batch Status field equals Prism Setup.
- Activate - Displays when the value in the Benefits Batch Status field equals Pending Activation. When the link is selected, the following confirmation message is displayed:
  
  "This will activate any related offered benefit plans and set the effective date of those plans to the effective date of this benefits batch. It will also expire the benefits batch (if any) that this batch was renewed from and its related offered benefit plans. Are you sure you want to activate this benefits batch?"

Added eleven (11) new business rules.

Rule Title	Method	Description
Set OBP to Inactive if Cancel Status	_SetFieldValue	Sets the OBP to Inactive if Status equals Cancel.
Set IsActive True when Pending	_SetFieldValue	Sets the Active flag on the Benefits Batch form to True when Status equals Pending.
Set Status to Prep For Presentation	_SetFieldValue	Sets the Status field on the Benefits Batch to Prep For Presentation when the Prep For Presentation link is clicked in the Action Center.
Set Status to Client Review	_SetFieldValue	Sets the Status field on the Benefits Batch to Client Review when the Client Review link is clicked in the Action Center.
Require Contact before Client Review	_RequireFieldOnThisForm	Displays a hard error if a Renewal Client Contact is not entered on the Benefits Batch when the Client Review link is clicked in the Action Center.
Set Status to Update Client Selection	_SetFieldValue	Sets the Status field on the Benefits Batch to Update Client Selection when the Update Selections link is clicked in the Action Center.
Set Status to Sent For Approval	_SetFieldValue	Sets the Status field on the Benefits Batch to Sent for Approval when the Send for Approval link is clicked in the Action Center.
Run Docusign Approval	_GenerateMergeFile	Runs the Docusign Approval procedure and stores the approved/signed renewal document in the Renewal Approval field. The Status of the Benefits Batch must equal Sent for Approval.
Set Status to Approved	_SetFieldValue	Sets the Status field on the Benefits Batch to Approved when the Approved link is clicked in the Action Center.
Set Status to Prism Setup	_SetFieldValue	Sets the Status field on the Benefits Batch to Prism Setup when the Prism Setup link is clicked in the Action Center.
Set Status to Pending Activation	_SetFieldValue	Sets the Status field on the Benefits Batch to Pending Activation when the Pending Activation link is clicked in the Action Center. Note: A new scheduled process, Benefits Batch Activation, is also being added in this release. It activates Benefits Batches in "Pending Activation" status on their renewal date. See Case# 69311 for details.

Added the Client Benefit Workbook Review email template. This sends an email to the Renewal Client Contact listed on the Benefits Batch with the Benefits Renewal Workbook attached for them to review. The email is triggered when the value in the Benefits Batch Status field equals Client Review. The default settings include default email body text which can be used "as is" or customized.

See Renewing a Benefits Batch.

69311

Added Scheduled Process to Activate Benefit Batches on Renewal Date

A new scheduled process, Benefits Batch Activation, has been added to activate Benefits Batches in "Pending Activation" status on their renewal date. If the Effective Date of the batch is less than (<) today's date, the Status field on the batch updates from "Pending Activation" to "Active".

See Scheduled Processes.

69654

Added Multiplier Field to OBP Dataform and Billing Rules Export

A new Multiplier lookup field has been added to the Offered Benefit Plans (OBP) dataform in the Setup Details fieldset. If the amount of coverage for a Life Insurance plan is equal to an amount multiplied by the employee's annual base pay, you can select the annual pay Multiplier in this field.

A Multiplier column has also been added to the Benefit Batch Billing Rules export so that the multiplier setting is exported to PrismHR along with the other OBP Setup Details entered in ClientSpace.

See Manually Adding an Offered Benefit Plan.

69848

Updated Premium and Contribution Rounding on Benefits-Related Merges

Two Benefits module merge procedures have been updated to add 4-digit decimal precision to Premium and Contribution fields:

Benefits Renewal merge (peo_merge_excel_benefitscomparison) - Updated the Current Contribution and Renewal Contribution fields.
Benefit Batch Billing Rules Export merge (peo_merge_client_benefit_billing_rules_export) - Updated the Premium and Contribution fields.

Note: The Client Benefit Plans Export merge (peo_merge_client_benefit_plans_export_202405) required no updates as the Premium and Contribution fields were already set to use 4-digit decimal precision.

See Benefits Renewal Merge and Benefit Batch Billing Rules Export.

Advanced Administration

Case	Enhancement
60955	Long Role Names Now Wrap in System Admin > Users Previously, when there was a long role name of more than 50 characters shown on the User Details page in the Action Center under Roles (System Admin > Users > Roles), you could not see the entire role name. It was cut off. Now, the role name wraps so that you can see the entire name.
61083	Added "Reports Used On Widget Layouts" View A new view named nw_vwAdHocReportsWidgets has been added to the list of preformatted CORE views in the Reporting Profile. The view contains fields that allow you to create a Business Intelligence report showing all reports currently used on widget layouts. In the example below, the nw_vwAdHocReportsWidgetsview has been used to create a report which is filtered to show only reports used on widget layouts where the widget layout is Active. The report displays the Report Name, Widget Layout Active, and Widget Layout Name columns. See CORE View Listing
64387	Added Case Subscription and Task Subscription Views Two new views have been added to the list of preformatted PEO views in the Reporting Profile. The views contain fields that allow you to create Business Intelligence reports showing the cases and tasks to which you are subscribed: peo_vwCaseSubscribers peo_vwTaskSubscribers In the example below, the peo_vwCaseSubscribers view has been used to create a report showing the Project ID, Case ID, Subscriber Email and Subscriber First and Last Name. A filter has been applied to only include records for a single subscriber. See PEO View Listing
65232	Updated the SE_VerifyPolicyWithDOI Business Rule Method on Comp Claim Previously, customers who use the ClientSpace Risk module without the Sales module received a soft error when selecting a Worker's Comp Claim if there was an attached Worker's Comp Policy with no associated Policy Comp Codes. This was happening because the SE_VerifyPolicyWithDOI business rule method contained validation logic that checked for an associated Policy Comp Code record and triggered the soft error message if it was not found. For clients that use the Risk module without the Sales module, there are often no Policy Comp Codes configured. Now, the Policy Comp Code validation logic has been removed from the SE_VerifyPolicyWithDOI business rule method. The rule only triggers the following soft error when the Date of Injury is before the Policy Effective Date or after the Policy Expiration Date: "The selected policy is not valid for the Date of Injury."
69093	Added New Salesforce Parameter to Support Using Multiple ClientSpace Instances with a Single Salesforce Instance A new Salesforce parameter, csinstance, has been added to support ClientSpace sites using multiple instances of ClientSpace with a single Salesforce instance. Add the parameter to each instance of ClientSpace in the PrismHRAPI Configuration for Salesforce (System Admin > Advanced > API Configuration) and enter the name of the instance in the Value field. EX: CS1 for the first instance, CS2 for a second instance, and so forth. You must also configure a new Work Queue field in Salesforce (setup by Salesforce Administrator) named CS_Instance to hold the instance value for each instance. Two underscores, followed by "c" are added by Salesforce once you save the field name, resulting in a field named CS_Instance__c. Once configured, an instance of ClientSpace will only retrieve work queue records where the ClientSpace csinstance value equals the Salesforce CS_Instance__c value. See Additional Salesforce Parameters.
69263	Added DocuSign API Retry Threshold Enhancements The following enhancements were added to help users manage failed document uploads that occur when the DocuSign API Retry Threshold (set in System Admin > Advanced > API Configuration) is met: Exception Log Error Message: The Envelope ID and Queue ID have been added to the Exception Log (System Admin > Exception Log) "retry threshold" error message. View this information from the Exception Log dashboard Error Text column or open the record to view the details. Uploaded Files Queue Reset Retry Count: A Reset Retry Count button has been added to the Uploaded Files Queue dashboard under Mass Update (System Admin > Imports > Uploaded Files Queue). Select one or more failed queue records and then select Reset Retry Count to set the Retry Count field on the Uploaded Files Queue detail record to 0 so that the failed document uploads can be reprocessed. Note: A Retry Count column has also been added to the Uploaded Files Queue. It is hidden by default and can be enabled from the vertical three dot menu (i.e., Kebab menu) of any column header. SeeViewing and Managing Document Statuses in the DocuSign Process andViewing DocuSign Exception Errors.
69851	Widget Layout Compatibility Refactoring The External Case widget and Activities widget can no longer be selected to add to a widget layout with a Target Type of Home. These widgets are not compatible with the Home page and were causing widget layout loading issues and errors, or in some instances, the widget layout loaded but did not work properly after loading. Note: The External Case widget and Activities widget can still be added to widget layouts with a Target Type of Workspace or a selected dataform. Related to Case# 65067.

General Enhancements

Case	Enhancement
58285	Added "Reported By Info" fieldset and "Reported By Type" field on Client Service Case A new Reported By Info fieldset has been added to the Client Service Case dataform. This was done to organize the "Reported By" fields similar to the Quick Cases form. The fieldset contains a new field named Reported By Type. Valid field selections include Employee, Client Contact, or Contact Information. Note: The selected Reported By Type determines the field display of some of the existing fields that have been moved into this fieldset. The five existing fields that have been moved into this fieldset are: Reported By (Employee) - Displays when Employee is selected as the Reported By Type. Client Contact - Displays when Client Contact is selected as the Reported By Type. Reported By - Displays when Contact Information is selected as the Reported By Type. Email Address - Always displayed and auto-fills from a Contact or Employee record if data is present. The field also accepts typed entries. Phone Number - Always displayed and auto-fills from a Contact or Employee record if data is present. The field also accepts typed entries. See Adding cases.
67444	Added Tooltips to Multiple Risk Module Fields Tooltips have been added to multiple fields on multiple Risk module forms so that users can quickly view the definition of a field. Updated forms include Comp Claim, Comp Claim Claimant, Comp Claim Financials, and PEO Config.

Case

Enhancement

58285

Added "Reported By Info" fieldset and "Reported By Type" field on Client Service Case

A new Reported By Info fieldset has been added to the Client Service Case dataform. This was done to organize the "Reported By" fields similar to the Quick Cases form. The fieldset contains a new field named Reported By Type. Valid field selections include Employee, Client Contact, or Contact Information.

Note: The selected Reported By Type determines the field display of some of the existing fields that have been moved into this fieldset.

The five existing fields that have been moved into this fieldset are:

Reported By (Employee) - Displays when Employee is selected as the Reported By Type.
Client Contact - Displays when Client Contact is selected as the Reported By Type.
Reported By - Displays when Contact Information is selected as the Reported By Type.
Email Address - Always displayed and auto-fills from a Contact or Employee record if data is present. The field also accepts typed entries.
Phone Number - Always displayed and auto-fills from a Contact or Employee record if data is present. The field also accepts typed entries.

See Adding cases.

67444

Added Tooltips to Multiple Risk Module Fields

Tooltips have been added to multiple fields on multiple Risk module forms so that users can quickly view the definition of a field. Updated forms include Comp Claim, Comp Claim Claimant, Comp Claim Financials, and PEO Config.

Fixes

Case	Issue summary	Resolution
58180	Corrected Workspace Template Issue	Previously, if a template workspace was created from another template, the parent and child templates remained linked. Therefore, if you made a change to the parent template, such as deleting a dataform, the child templates were affected. Now, when a template workspace is created from another template, changes to the parent template have no effect on the child template.
65067	Corrected Widget Issues and Errors	Previously, issues such as 500 server errors and improper widget layout loading occurred when an External Case widget or Activities widget was added to a widget layout with a Target Type of Home. These widgets are incompatible with a Home Page widget layout. Now, the External Case widget and Activities widget can no longer be selected to add to a widget layout with a Target Type of Home. Related to Case# 69851.

Case

Issue summary

Resolution

58180

Corrected Workspace Template Issue

Previously, if a template workspace was created from another template, the parent and child templates remained linked. Therefore, if you made a change to the parent template, such as deleting a dataform, the child templates were affected. Now, when a template workspace is created from another template, changes to the parent template have no effect on the child template.

65067

Corrected Widget Issues and Errors

Previously, issues such as 500 server errors and improper widget layout loading occurred when an External Case widget or Activities widget was added to a widget layout with a Target Type of Home. These widgets are incompatible with a Home Page widget layout. Now, the External Case widget and Activities widget can no longer be selected to add to a widget layout with a Target Type of Home.

Related to Case# 69851.