Release 127 Notes

R127 Sprint: 4/3/2023 to 5/1/2023. 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 R127 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 4/3/2023 to 5/1/2023
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	May 9, 2023
Group 2	Second Tuesday of the month	May 16, 2023
Group 3	Third Tuesday of the month	May 23, 2023

Enhancement

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

Benefits API

Case	Enhancement
61081	Added Multi-Tenancy Support to Benefit Plan Export API The following Benefit Plan Export API business rule methods were enhanced to allow the export of benefits data to the correct database instance of PrismHR in a multi-tenant environment: ExportOfferedPlansToPrism ExportBenefitGroupsToPrism ExportBenefitRulesToPrism To support multi-tenancy, the following now occurs when the Export Plans to Prism link is clicked on the Benefits Batch record in a Client Workspace: The system evaluates the Use Multitenancy field value on the PEO Configuration record (System Admin > Administrative Data > PEO Configuration). If Use Multitenancy = Yes, the system evaluates the PEOID on the Client Master record of the Client Workspace and attempts to locate the active API configuration record for this PrismHR instance by the Client Master PEOID. A valid match is determined when there is a PEOID value in the Secondary ID field of an active API configuration record that matches the Client Master PEOID associated with the workspace where the export is being initiated. If the PEOID is missing on the Client Master record, the following warning message displays: "There is no PEOID on this client's Client Master form. Please make sure that a valid PEOID is filled out on this client's Client Master before attempting to export this again." If the PEOID is invalid on the Client Master record (i.e., it does not match to any existing API configuration record), the following message displays: "The PEOID , "{PEOID#}" on this client's Client Master is invalid. Please correct the PEOID on the Client Master before trying to export this again." Once an active API configuration record is located for a valid Client Master PEOID, the offered plans, benefit groups and benefit rules are exported to the correct PrismHR database instance. Note: In a single tenant environment, ClientSpace will continue to use the default PrismHRAPI API Configuration record to export offered plans, benefit groups and benefit rules to PrismHR. Please contact the ClientSpace Professional Services team for configuration assistance before attempting to use the Benefit Plan API in a multi-tenant environment for the first time. See the Exporting Benefits in Multi-Tenant Environments section of Configuring Benefit Plan API Business Rules.

Case

Enhancement

61081

Added Multi-Tenancy Support to Benefit Plan Export API

The following Benefit Plan Export API business rule methods were enhanced to allow the export of benefits data to the correct database instance of PrismHR in a multi-tenant environment:

ExportOfferedPlansToPrism
ExportBenefitGroupsToPrism
ExportBenefitRulesToPrism

To support multi-tenancy, the following now occurs when the Export Plans to Prism link is clicked on the Benefits Batch record in a Client Workspace:

The system evaluates the Use Multitenancy field value on the PEO Configuration record (System Admin > Administrative Data > PEO Configuration).
If Use Multitenancy = Yes, the system evaluates the PEOID on the Client Master record of the Client Workspace and attempts to locate the active API configuration record for this PrismHR instance by the Client Master PEOID.
- A valid match is determined when there is a PEOID value in the Secondary ID field of an active API configuration record that matches the Client Master PEOID associated with the workspace where the export is being initiated.
- If the PEOID is missing on the Client Master record, the following warning message displays: "There is no PEOID on this client's Client Master form. Please make sure that a valid PEOID is filled out on this client's Client Master before attempting to export this again."
- If the PEOID is invalid on the Client Master record (i.e., it does not match to any existing API configuration record), the following message displays: "The PEOID , "{PEOID#}" on this client's Client Master is invalid. Please correct the PEOID on the Client Master before trying to export this again."

Once an active API configuration record is located for a valid Client Master PEOID, the offered plans, benefit groups and benefit rules are exported to the correct PrismHR database instance.

Note:

In a single tenant environment, ClientSpace will continue to use the default PrismHRAPI API Configuration record to export offered plans, benefit groups and benefit rules to PrismHR.
Please contact the ClientSpace Professional Services team for configuration assistance before attempting to use the Benefit Plan API in a multi-tenant environment for the first time.

See the Exporting Benefits in Multi-Tenant Environments section of Configuring Benefit Plan API Business Rules.

Other ClientSpace Premium

Case	Enhancement
60461	Added New "Edit Surcharge After Submit" Security Entity A new security entity, biz_EditSurcharge_After_Submit, has been added that allows users in a role containing the entity (with either View or Admin rights assigned) to continue to edit the pricing fields on the Surcharge dataform after pricing is submitted up until pricing is locked. Once pricing is locked, editing the pricing fields is not permitted. The new entity is supplemental and will not override form-level security provided by the gen_Surcharges entity. It will also not override any field-level security on individual pricing fields. Any user who is not in a role that allows them general access to view and edit the Surcharges form (as well as access to view and edit any individually secured pricing fields on the Surcharges form) will not be granted access by the biz_EditSurcharge_After_Submit entity to edit surcharge pricing fields after pricing is submitted. Once the appropriate rights to the Surcharges form (and to any secured fields) are granted, the following pricing fields can be changed on the Surcharges form after pricing is submitted up until pricing is locked: Surcharge Type Quantity - The presence of this field varies by Surcharge Type and may not always display. Override Surcharge Amt Surcharge Amt - Requires user to click Override Surcharge Amt checkbox to access the field. Note: By default, Global Administrators can edit surcharge pricing fields up until pricing is locked without this entity assigned. See Creating Pricing and Standard Security Entities.

Case

Enhancement

60461

Added New "Edit Surcharge After Submit" Security Entity

A new security entity, biz_EditSurcharge_After_Submit, has been added that allows users in a role containing the entity (with either View or Admin rights assigned) to continue to edit the pricing fields on the Surcharge dataform after pricing is submitted up until pricing is locked. Once pricing is locked, editing the pricing fields is not permitted.

The new entity is supplemental and will not override form-level security provided by the gen_Surcharges entity. It will also not override any field-level security on individual pricing fields. Any user who is not in a role that allows them general access to view and edit the Surcharges form (as well as access to view and edit any individually secured pricing fields on the Surcharges form) will not be granted access by the biz_EditSurcharge_After_Submit entity to edit surcharge pricing fields after pricing is submitted.

Once the appropriate rights to the Surcharges form (and to any secured fields) are granted, the following pricing fields can be changed on the Surcharges form after pricing is submitted up until pricing is locked:

Surcharge Type
Quantity - The presence of this field varies by Surcharge Type and may not always display.
Override Surcharge Amt
Surcharge Amt - Requires user to click Override Surcharge Amt checkbox to access the field.

Note: By default, Global Administrators can edit surcharge pricing fields up until pricing is locked without this entity assigned.

See Creating Pricing and Standard Security Entities.

Advanced Administration

Case	Enhancement
52227	Added Role Security Configuration for Custom Links Previously, there was a Security Entity field on the Configure Links Detail window that required you to select an entity, then associate that entity with a role in order to secure a link. Now, an Action Center panel has been added to the Configure Links Detail window. You can click the Security icon in the Action Center to access the Security Roles window where you can add one or more roles and secure the custom link to unlimited roles. Note: With this update, the former Security Entity field no longer displays on the Configure Links Detail window. Additionally, a one-time script runs that evaluates the previous Security Entity field value of each existing custom link record, determines which ClientSpace roles contain the entity, and adds those roles to the Security Roles window of each custom link record. See Configuring Custom Dataform Links .
58061	Added Query Widget A new Query widget has been added that allows you to display a table containing ClientSpace query results from a selected stored procedure. You can also upload an XSLT file containing custom table styles. (Default ClientSpace table styles are used if you do not upload custom styles.) Note: Please contact ClientSpace Professional Services for file layout instructions. The Query widget can be added to the following ClientSpace locations: Home page Workspace landing page Dataform header See Widget: Query (XSLT).
61049	Added Salesforce API Configuration "Test Connection" Capability A Test Connection feature has been added to the Salesforce API Configuration window (System Admin > Advanced > API Configuration). The Test Connection button is activated when you select and save the ClientSpace.Core.DataAccess.SalesforceConnectionTester value in the Connection Tester field. Clicking it allows you to test the API username and password prior to using the API for the first time. The system attempts to connect to the API and either returns a "Connected Successfully" message or an "Unable to connect" message. The "Unable to connect" message lists missing parameters contributing to the failure to connect to help you troubleshoot the issue. See Configuring the Salesforce API in ClientSpace.
61162	Enhanced User Audit Trail More Search The following new options have been added to the User Audit Trail More search: User Type: Valid options are Internal and External Include System Users: Click the Include System Users checkbox to include system users (such as developer users) in the filter results. See Viewing Audit Trails.

General Enhancements

Case	Enhancement
58249	Added Workers Comp Deductible Bill API A new Workers Comp Deductible Bill API named PrismHR Bill Records has been added to Scheduled Processes (System Admin > Advanced > Scheduled Processes). When triggered, the PrismHR Bill Records scheduled process performs the following tasks: Identifies all Claim Deductible Billing records in "Ready to Bill" status (and where the WC Deductible Bill Opt-Out setting on the Client Master record of each associated client workspace is unchecked.) Exports eligible billing records to PrismHR and creates a "Bill Pending" record for each exported bill in PrismHR. (Bill Pending Comment text, if entered, is also exported to the Comments field of the Bill Pending record in PrismHR.) Note: The Bill Pending Comment field has been added to the Claim Deductible Bill form in this release to provide the ability to export billing comments to PrismHR. Upon a successful export, updates the status of the Claim Deductible Billing records in ClientSpace to "Billed" and writes "Successfully Created Bill Record in Prism" to the Export Log field of the exported Claim Deductible Billing records. Upon an unsuccessful export, updates the status of the Claim Deductible Billing records in ClientSpace to "Failed to Export" and writes an error message to the Export Log field of the affected Claim Deductible Billing records. See the example image below of an Export Log error message: Note: Multi-tenancy is supported. Contact Professional Services for assistance configuring API parameters. See Scheduled Processes.
60873	Added Quick Case Dialog A new Quick Case dialog has been added to allow faster creation of a Client Service Case with minimal data entry of required fields. You can return to the case record later and add additional information as necessary. Please note the following: The Quick Case entry feature is only available on the Cases (Cases 2.0) dashboard, not the Cases-Old (Cases 1.0) dashboard. The Cases Dashboard toolbar was updated to display image buttons (icons) instead of button text. Hovering your mouse button over a tool displays tooltip text for the Quick Case, Add New and Edit options. Access to the Quick Case dialog for non-global Admin users is controlled by a new security entity: biz_ClientServiceCase_QuickCase. A Global Administrator must add the entity to desired roles and configure the entity to match role requirements. A new Quick Case pipeline has also been added. The Quick Case pipeline honors applicable Client Service Case business logic rules. However, hard and soft errors are not currently honored. A new lookup value of "Quick Case" was added to the Communication Method lookup group. The Communication Method field of any Client Service Case record created using the Quick Case dialog is automatically set to "Quick Case". Global Administrators: Some Quick Case configuration is required while other configuration elements are optional. Required: Add the biz_ClientServiceCase_QuickCase security entity to each role where Quick Case access will be permitted and set the access level for each role. Required: Set a flag on the Client Service Case Type form to determine which case types are available for selection in the Type field on the Quick Case dialog. Optional: Set a Short Name on Client Service Category Metadata form for each case type category to allow users to filter the Type field on the Quick Case dialog by category Short Name. Refer to Configuring the Quick Case Feature for configuration details. Once enabled, access the Quick Case dialog from the Cases dashboard by clicking the Quick Case button located in the top right corner of the Cases dashboard. Clicking the button displays the Quick Case popup window where you can add the required fields and save the case. See Configuring the Quick Case Feature and Adding a Quick Case.
61228	Added Hour (h) and Minute (mm) Date Time Datatype Shortcuts Date Time datatype fields now accept Hour (h) and Minute (mm) data entry shortcuts. Positive and negative values are supported. Examples: Type 15mm to apply the current date and time plus an additional 15 minutes. Type -1h to apply the current date and time minus one hour. See Configuring Your Dataform Datatypes.
61233	Added Export Log to Claim Deductible Bill Window An Export Log field has been added to the Claim Deductible Bill window. This field displays export details that can be helpful in troubleshooting when a Claim Deductible Bill fails to export. To support this enhancement, a "Failed to Export" value was added to the Status lookup group. When an export fails, the Status field of the Claim Deductible Bill record automatically changes to "Failed to Export". See Using the Claim Deductible Bill Form.
61536	Added Two New Address Source Options to Email Template External Case Notification Address Source Procedure Two additional address source options have been added to the email template external case notification address source procedure peo_clientservicecase_external_emailtemplate_recipient_v2_proc: ReportedByEEPersonalEmail - This address source adds the personal email address from the employee record of the Reported By (Employee) as an email recipient. ReportedByEEWorkEmail - This address source adds the work address from the employee record of the Reported By (Employee) as an email recipient. Note: The Reported By (Employee) field is in the Case Assignment fieldset of the Client Service Case. It displays only when the Communication Method field on the Client Service Case is set to Employee Portal. The new address source options are available to use when you build your recipient records on the Address tab of email template configuration as shown in the example image below: See Step 3: Addresses.

Fixes

Case	Issue summary	Resolution
61067	HomeCountry and HomeCounty Both Importing to County Field in Ongoing Employee Import	Previously, the Import Map Detail record for HomeCountry that is associated with the Ongoing Employee Import Map Header record was incorrectly mapped to the County (luCounty) field of the Employee dataform. This resulted in both HomeCountry and HomeCounty being mapped to the same field. Now the HomeCountry Map Detail record is correctly mapped to the Country (luCountry) field of the Employee dataform.
61104	Default Saved Search Displayed Instead of Associated Workspaces When Clicking Open Workspaces On an Organization Detail Record	Previously, when you opened an Organization Detail record (from the Organization module dashboard) and then clicked the Open Workspaces icon on the Action Center toolbar, if there was a default saved search and the organization had more than one associated workspace, instead of filtering the display to a list of workspaces associated with the organization, the default saved search for the Workspaces module displayed. Now, clicking the Open Workspaces icon on an Organization Detail record with more than one associated workspace always displays a filtered list of workspaces associated with the organization.
61133	"Updated By" on User Details Did Not Display Username of Global Admin Who Updated Another User's Password	Previously, when a Global Administrator changed a password for another user, the Updated By field of the User Details page (System Admin > Users > Edit) incorrectly displayed the username of the user whose password was changed. Now, the Updated By field displays the username of the Global Administrator who made the password change.
61198	Dependent Workflow Using a Child Tab Multi-Lookup With "Equals" Operator Did Not Work	Previously, using a multi-lookup field on a child tab of the main form to trigger a dependent condition did not work with an "Equals" operator. Only primary condition statements successfully triggered using a multi-lookup field with an "Equals" operator. Now, both primary and dependent conditions trigger using multi-lookup fields with an "Equals" operator.
61256	"HE_VerifyJurisdictionState" Business Rule Method Did Not Respect Non-Pricing Clients	Previously, the HE_VerifyJurisdictionState business rule method (which verifies that a selected Jurisdiction State of a client is covered by an active workspace pricing state) was triggering even when the client did not use pricing and had no pricing states configured. This resulted in an error message displaying. Now, the HE_VerifyJurisdictionState business rule method only triggers when Use Pricing on the Client Master record is set to Yes. When Use Pricing is set to No, the business rule method does not trigger.