Release 126 Notes

Added "Task Type to Task Category" Validation to ClientSpace API Version 2.0 POST and PATCH Task Methods

Previously, when saving a POST (i.e., insert) or PATCH (i.e., update) Task operation in version 2.0 of the ClientSpace API, it was possible to select a Task Type group lookup value that did not match the Task Category group lookup value and save the change. Now, when you attempt to save a POST or PATCH where the Task Type does not match the Task Category, the following error message displays in the Swagger interface "Response Body" section:

"The Type '{Task Type}' is not valid for the Category of '{Task Category}'."

You cannot complete the operation until the mismatch is corrected.

Note: Detailed documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding the desired method.

Updated Worker's Compensation Claim Deductible Process

The Worker's Compensation Claim deductible process has been updated to calculate Worker's Compensation deductible billing for export to an invoicing system. To support the changes, the SetClaimDeductible business rule method was modified to set the Claim Deductible field on the Comp Claim form from either the Pricing Batch or the Client Master record. Originally, this only set the Claim deductible from the Pricing Batch.

The SetClaimDeductible business rule method uses the following logic:

• ClientSpace retrieves the deductible from the current Pricing Batch first (if it exists) and uses it to set the Claim Deductible.

  • The Current Record checkbox must be checked on the Pricing Batch, denoting it as the current Pricing Batch.

  • If the deductible is set to $0.00 on the current Pricing Batch, it is treated as a valid value and may be used in deductible bill amount calculations.

• If there is no current Pricing Batch record, ClientSpace sets the Claim Deductible using the WC Deductible field from the Client Master record.

The following new dataform fields were created to store information relevant to the tracking of deductible billing details. The fields are INACTIVE by default:

Client Master

• WC Deductible

• WC Deductible Bill Opt-Out

PEO Configuration

• Claim Deductible Event Code

Claim Deductible Bill

• Change Source (uses new WC Deductible Source lookup group)

• Date Billed

The following new Lookup Group and values were created to support the process:

WC Deductible Source

• System

• Manual

The following Lookup Group was updated to add a new value:

Claim Deductible Billing Status

• Manual

See Administering a Workers' Comp Claim.

Also see related R126 case 60581.

Added Range of Year Values to OSHA Year Lookup Group

The years 2022 through 2030 have been added to the OSHA Year lookup group.

Added Output Type to Available Columns and More Search on Merge Admin Dashboard

An Output Type column is now available to add to the Merge Admin dashboard (System Admin > Outputs > Merges).

Add the Output Type column to view the configured output types of each of your merges at-a-glance and quickly verify that the correct output type has been set.

Additionally, the ability to search by Output Type has been added to the More search.

See Merges.

Added New "Date Time" Business Rule Methods

The following new business rule methods that use the Date Time datatype were added to Manage Rules (System Admin > Advanced > Manage Rules) for use in workflow and business rule configuration:

• _SetDateTimeFieldValue

• _SetDateTimeFieldValueFromSourceField

• _SetTabDateTimeFieldValue

Note: 

• Date Time shortcuts are supported. The valid codes are t = today, d = day, mm = minute, h = hour, w = week, m = month, and y = year. Examples: t (current date/time), 1w (plus 1 week), 3d (plus 3 days) or -1d (minus 1 day).

• Supporting Info Bubble text describing method parameters has been added.

See Business Rule Methods.

Added Case History Dataform

The Case History dataform stores PEO Client Service Case workflow details. Currently, the Case History dataform is hidden as it is only used to store historical workflow data such as date/time stamps and the length of time (in minutes) that a case remains in a certain state. However, you can use the associated dataform table (gen_CaseHistory) to create Business Intelligence reports based on Case History details.

For instance, you can build a report displaying the following:

• Average time from case creation to assignment

• Average time from case creation to resolution

• Average time cases spend in a particular Status

• Average time cases spend flagged as a particular Priority (such as High or Critical)

• Average "first response time"

Note:

• Functions to calculate duration states in minutes (Status State Duration, Assigned To State Duration, Priority State Duration, and Case Type State Duration) take into account ClientSpace application settings that define a PEO's business hours, work week parameters, and holidays. The accuracy of the calculations is dependent on these settings being correct.

• Date Time fields are set using PEO application time zone settings defined in ClientSpace.

See Case History Dataform for a complete list of Case History dataform fields.

Also see R126 related cases 60927 and 60940.

Added Out of Office Case Reassignment Functionality

The Reassign During Out Of Office feature is an optional enhancement to the Enable Out of Office feature located in the "Out of Office (OOO)" section of your user profile. On your user profile, when you check Enable Out of Office, specify a user in the Back Up User field and enter an out of office Start Date and End Date, ClientSpace sends notifications to the OOO backup user when you receive new task and case assignments during your out of office dates. When the Reassign During Out of Office feature is also enabled, in addition to sending notifications, ClientSpace reassigns your new cases to the specified OOO backup user while you are away.

To activate the feature, a Global Administrator must check the Reassign During Out of Office checkbox in the PEO Configuration settings.

Once the feature is activated, ClientSpace evaluates the OOO backup user each time you receive a new case assignment to ensure they are a valid user. The OOO backup user is determined invalid for reassignment when any of the following is true:

• User is flagged in the system as "out of office"

• User is expired

• User is inactive

• User lacks appropriate case type access

If the OOO backup user is invalid, ClientSpace evaluates Case Type default backup assignment settings specified in the "Default Assignments" section of the relevant Client Service Case Type record (Admin Workspace > Client Service > Client Service Case Type) to determine an appropriate reassignment path.

See Enabling Out of Office option and Personalizing Your User Profile.

Added Case History Business Rule

A new Case History Business rule that uses the SetHistoryRecord business rule method has been added to create or update a new Case History record. The rule is triggered when:

• A new Client Service Case record is created

   

  OR

   

• A Client Service Case record is updated and one or more of the following fields change:

  • Status

  • Assigned To

  • Case Type

  • Priority

  • Active flag

Note: Case History updates only occur where there is an initial Case History record. Therefore, the "update" logic cannot be applied to any active cases created prior to the release of this feature.

See Case History Dataform.

Also see R126 related cases 57724 and 60940.

Previously, when configuring a Field Display rule (System Admin > Advanced > Manage Field Display) with Type set to "Style", the Discard button used to clear style settings (i.e., Font Type, Font Style, and Color) remained active even when no style settings were chosen. Now, the Discard button is only active when style settings are present.