Release 130 Notes

Client Profitability Merge Enhancements

The following new fields have been added to the Payroll_New tab of the Client Profitability Report merge (System Admin > Outputs > Merges >Client Profitability) Excel template:

Gradient AI Health Benefits API - Coverage Type Validation Change

Previously, ClientSpace validated the coverage types of census data submitted to Gradient AI. This sometimes caused submission issues as not all coverage types in the file were represented in the client's offered plans.

Now, _GAICensusValidation triggers an error if there is no data in the Coverage Type column.

Error message reads "Coverage Type is required."

Gradient AI  validates the specific coverage types upon submission of the census data. If Gradient AI finds that specific coverage types are invalid, the Status field on the Gradient AI Health Results record (Benefits Batch dataform > Gradient AI Health Results link) is updated to "Failed" and validation error details are written to the Log field.

Note: ClientSpace validation of other census data requirements such as the presence of valid subscribers and underwriting groups is unaffected by this change.

See Gradient AI Health Benefits.

Added Field Set Collapse/Expand Functionality

A new optional field, Field Set Default, has been added to Dataform Admin (System Admin > Advanced > Dataform Admin). This setting allows you to control whether fields within a field set are visible or collapsed within the field set container when the form loads. Once the form loads, users can toggle between expanding and collapsing field sets where a Field Set Default has been applied.

Note: 

• With this update, when you add a new field set, the Field Set Default setting is automatically set to Expanded. You can change the setting to Collapsed or you can clear the field. When the field is cleared (i.e., empty or blank), all fields in the field set display just as they did prior to this change with no ability to expand or collapse field sets.

• The Field Set Default setting affects the field display only. Dataform field validation still occurs on fields contained within field sets that are collapsed. Additionally, this setting does not interfere with workflow channel configurations that reference fields in collapsed field sets.

See Adding Dataform Fields.

Auto-Create Workspace by PrismHR Import API

Previously, when the Can Create Workspaces checkbox was checked in PEO Configuration and the ongoing nightly import ran, if no active workspace was found for an imported Client Number, ClientSpace created a new workspace. This was a global setting that was applied to every import API. With PrismHR API imports in multi-tenant environments (where there are multiple PrismHR API configurations and where the Client Number may not be unique), there is a need to flag which PrismHR API imports should auto-create workspaces and which should not (to prevent potential duplicate workspaces).

Now, to support this requirement:

• You can specify a CanCreateWorkspaces API parameter in PrismHR API import map detail settings (System Admin > Advanced > API Configuration) to inform the system which PrismHR API import feeds can create workspaces.

   

  When PrismHR nightly imports run, ClientSpace evaluates each import file to determine if the PEOID in the import file matches the Secondary ID entered on the API Configuration record. If there is a match, ClientSpace then references the CanCreateWorkspaces parameter to determine if a workspace should be created using the following logic:

  • If the CanCreateWorkspaces parameter is set to a value of 1 and the Client Number does not already exist for the PEOID, a new workspace is created.

  • If the CanCreateWorkspaces parameter is set to a value of 0 or is blank, a new workspace is not created.

• Additionally, the Can Create Workspaces checkbox in PEO Configuration (System Admin > Administrative Data > PEO Configuration) has been renamed Create Workspace From Import. The functionality still creates a new workspace if no active workspace is found for an imported Client Number but now only works for non-Prism imports.

Note: With this update, if the PEO Configuration setting, Create Workspace from Import checkbox (formerly Can Create Workspaces checkbox) is found to be checked, existing PrismHR API configurations will be updated with the CanCreateWorkspaces API parameter set to 1. This will preserve your current functionality.

See Ongoing Imports: Configuring the API for Import Map Details and Multi-tenant Environments in ClientSpace.

Added OSHA Process Email Template

An OSHAProcessEmail template has been added (System Admin > Email Templates). The template supports and enhances existing OSHA Mass Creation/Distribution functionality by sending OSHA300 and OSHA300A files to the OSHA Contact when the OSHA process successfully runs.

Note: The OSHA Contact is set on the Client Teams page which can be accessed from the Client Team widget.

The email is triggered when both OSHA300 and OSHA300A fields on the OSHA Forms dataform are NOT EMPTY.

Watch Item: Freeze Review Date Enhancement

Previously, when a user or a process updated a Watch List item, the Review Date of the pinned item automatically updated to the current date. Now, when pinning a Watch List item, a new Freeze Review Date option on the Select Review Date window is available. When the checkbox is checked, the system preserves the original Review Date after a pinned record is updated. When the checkbox is unchecked, the system updates the Review Date to the current date after a pinned record is updated.

See Widget: Watch.