Release 150 Notes

Made Parent Form Fields Available on Custom Link Display Configuration

Parent form fields are now available when configuring custom link display conditions on dataforms (System Admin  > Advanced > Custom Links). When building the display condition, when Source equals Form Data and the Field has a datatype (i.e., Element Type) of "Parent Form", the available operators are Empty, Not Empty, Equals, and Not Equals.

See Configuring Link Display Conditions.

Made Department Field Required on Internal User Profile Records

The Department field is now a required field to save an internal user profile record.

Adding and Editing User accounts

Added Prism HCM API Configuration Parameter to Retrieve Only Specified Client Statuses

Previously, there was no way to exclude Prism HCM records for clients with a status such as Terminated from importing into ClientSpace. Now, a new HCM API configuration parameter named AllowClientStatuses has been added that allows you to enter a comma-separated list of client status values to allow.

In the example HCM API Configuration record below, only Prism HCM records for clients in Active and Pending status will import into ClientSpace.

Note:

• The AllowClientStatuses parameter applies to both initial and ongoing Prism HCM imports.

• If you do not add the AllowClientStatuses parameter, the default record retrieval functionality remains in place as records will continue to import for all client statuses.

See Importing to ClientSpace from HCM Using Initial Import Sync and Importing to ClientSpace from HCM Using Ongoing Import.

Related Metadata is Now Removed upon Lookup Deletion

Previously, when a lookup value was deleted, related metadata was orphaned. Now, when you delete a lookup value with associated metadata, the metadata is also deleted.

See Lookups with Metadata.

Removed Password Field from DocuSign API Configuration Form

The Password field has been removed from DocuSign API configuration in ClientSpace (System Admin  > Advanced > API Configuration) as this field is no longer used. An OAuth2 RSA Key, instead of a password, is required by DocuSign for all DocuSign API integrations after 12/31/2023.

See Configuring the DocuSign API Record.

Added "Run on Demand" Setting to BI Report Widget Configuration

A new Run on Demand setting has been added to the Widget Settings form (System Admin  > Widget Layouts) of BI report widgets.

When this setting is applied to a BI report widget, it does not load automatically. It is triggered by a "Click to Load" link in the center of the widget frame.

Use this setting to prevent specific BI Report widget(s) from attempting to load at once on Widget layouts containing a lot of BI Report widgets. This can improve performance by reducing page load times.

SeeConfiguring BI Reporting Widgets.

Added Additional Fields to the HCM Initial and Ongoing Import Mapping

The following additional mapped fields have been added to the HCM Initial and Ongoing Imports.

Company

HCMAPI_initial_company*.csv and HCMAPI_ongoing_company*.csv

• NAICS

Employee

HCMAPI_initial_employee*.csv and HCMAPI_ongoing_employee*.csv

• Employee Identifier

Employment

HCMAPI_initial_employment*.csv and HCMAPI_ongoing_employment*.csv

• Employment Status

• Employment Type

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

Updated SetFieldFromSalesEntity Business Rule Method

Previously, when you used the SetFieldFromSalesEntity business rule method, depending on configuration, a duplicate single form could be created in the same workspace. There were also instances of duplicate multi-forms being created when the method was used on a multi-form. Now, the business rule method has been refactored to only be used on single forms in the same workspace. 

When a rule using this method triggers, a new form is only created when there is no existing single form and existing single forms are updated appropriately.

See Business Rule Methods.

Added Security Mask to SSN Datatype Fields

A security mask (xxx-xx-####) has been added to SSN datatype field. The mask is automatically applied when a user opens a form with an existing SSN or types an SSN into a field.

Example:

A new eye button mask entity in the following format, will be created for each SSN datatype field: <dataform>.<fieldname>.Mask. This is separate from and in addition to the standard SSN field security entity.

Example: gen_Employees.SSN.Mask

This entity enables a View/Hide (i.e., eye) button next to the SSN. This serves as a toggle switch to remove the mask for temporary viewing of the complete SSN  and to reapply the mask.

Note: 

• The SSN security mask feature is automatically enabled upon receiving the upgrade to ClientSpace Release 150.

  • All existing SSN fields will have the new eye button mask entities created to give them access to the button. The eye button mask entities have been assigned to all roles ending in "_Admin" in a one time script.

  • Although the eye button mask entity is automatically created when new SSN datatype fields are created, it is not assigned. You must manually assign it to roles with View rights if you want those roles to have access to the eye button.

  • If you do not assign the eye button mask entity, the SSN mask will still be applied but users without the eye button cannot remove the mask to view the complete SSN.

• The security mask is applied to both accessible and "read only" fields.

  • If a field is disabled by a field display setting and the eye button mask entity is applied, the eye button still displays but is disabled.

• On an accessible field, if you try to edit an SSN by backspacing over any part of it, the entire value clears and you must re-enter the SSN.

See Configuring Your Dataform Datatypes.

Updated Move Comp Claim Process

Previously, if you moved a Comp Claim that had custom parent form fields on it, an error message displayed. This happened because custom parent form fields retained their values and if a value linked to a record in a different workspace, the error occurred. Now, when you move a Comp Claim record that contains custom parent form fields on the main Comp Claim form or any related tabbed form, the custom parent form fields are cleared.

When you initiate a Comp Claim move where there are custom parent form fields, a message now displays at the top of the Move Comp Claim form as shown in the example below:

See Administering a Workers' Comp Claim.

Added "Search on Load" to Initial Import Form

Previously, when the Initial Import form loaded, the following message was displayed on the Initial Import dashboard: "Please enter search criteria and click the search button to see results". Now, when the Initial Import form loads, the list of import records loads into the grid. You can use Quick Search and More Search to filter the list as desired.

Previously, you could enter a date on a Workflow Channel trigger condition containing an invalid year, such as 03/18/002. Now, Workflow Channel date fields only accept valid two-digit and four-digit values. Additionally, when entering a two-digit year value, the system is able to interpret and apply it correctly as a four-digit year value. For example, entering 11/20/94 is interpreted and applied as 11/20/1994 and entering 11/20/24 is interpreted and applied as 11//20/2024.