Release 103 Notes

R103 Sprint: 4/1/2021 to 4/30/2021. To learn about product features that you may not recognize, contact your Customer Success Manager.

Product Feature Review

Listen to a discussion of new product features.

Release schedule

Release updates are implemented by the group, as indicated in the following table.

Enhancement

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

Change in Functionality

Case

Enhancement

48179

Export Employees to PrismHR During Onboarding

This case modifies exporting an employee (or employees) from ClientSpace to PrismHR by allowing an employee social security number (SSN) to exist in multiple clients in PrismHR.

See Exporting Employees.

49081

Module Refresh (Top Frame)

This case incorporates an automatic refresh of the top frame modules when a user saves their module changes in their user profile. If a user edits their user profile and selects the Modules action item, they can add, remove, or change the display order of modules. When the user selects Save or Apply, the modules listed in the top frame automatically refresh and reflect any changes that the user made.

49160

DocuSign Fail email going out more than once

Previously, when a DocuSign email failed the system triggered the DocuSignFail email template for each failed attempt. This led to the system sending many email messages. This case adds logic to check the Queue record retry count against the retrythreshold API parameter and only triggers the DocuSignFail email template when the retry threshold limit has been reached.

See Notifying Users of Status.

50254

PrismHR API Client Team Import error

Previously, when importing data from a Client Team event, if the 'my SupportTeamDashboard' value was empty (missing the UserID) an exception was thrown. Now, the system clears the value on the Client Team form (unless a default value is configured for the import field) and the system no longer logs an exception..

See Importing to ClientSpace.

50376

Link Condition Expression Length Issue

Previously, the Link Condition Expression had a maximum length of 500 in the database table. This case changes the column to varchar(max) on the table. This case also verifies that any related procedures that use the Link Condition Expression also use varchar(max).

50420

Allow "Pending Activation" status Benefit Plans to show in Benefit Plan field on Offered Benefit Plans

Previously with 48493 for the R101 release, the Benefit Plan field drop-down on the Offered Benefit Plan dataform was updated to only display the active plans. With this case, the system now filters for both active plans and plans that are pending activation.

ClientSpace Premium

Case

Enhancement

49928

UI Claim-Delete/Move Claim Buttons

This case adds the ability to delete or move an unemployment insurance claim through the use of the UI Claim dashboard. With this feature, an admin user can delete a claim if the claim is not needed, or move a claim if the claim was created for the wrong employee or workspace. For example, an admin user can select an unemployment insurance claim on the UI Claim dashboard and complete one of the following:

  • Select the Delete button for the system to delete the claim

  • Select the Move button, select a new workspace, and select a new user for the system to move the claim to the new user in a different workspace

  • Select the Move button, select the same workspace, and select a new user for the system to move the claim to a new user in the same workspace

See Managing Unemployment Claims.

50156

Duplicated ImportIDs on Offered Benefit Plans

When adding a new Offered Benefit Plan to a workspace, the system validates the new Offered benefit plan against active and inactive plans during a Save or Apply.

If the new plan is a duplicate of an active or inactive plan, the system displays a message that indicates that offered Benefit Plans must not be duplicates of other Offered Benefit Plans. The system does not create the new plan.

When editing an existing plan the system validates the changes to the plan against active and inactive plans during a Save or Apply.

If the change to the plan makes the plan the same as an active or inactive plan, the system displays a message that indicates the following:

  • That offered Benefit Plans must not be duplicates of other Offered Benefit Plans.

  • That the benefit plan, benefit group, or rate group combination is associated with another plan and must be unique.

The system does not save the changes to the plan.

50249

SQL Error When Generating Pricing Console

If a contract type is set to use state master and the state is without a default policy for the selected comp model, the system cannot determine the pricing policy and displays an error when a user attempts to create pricing by using the Add State and Code approach.

Previously, the system displayed an SQL error for this scenario. The SQL error message did not advise the user how to proceed and resolve the issue. Now, a hard error message alerts a user to contact the system administrator to resolve the error. The following message is an example for the state of Texas:

"The Pricing cannot be generated because a Pricing Policy cannot be determined for TX. Please contact your system administrator."

See Administration troubleshooting.

50251

Create WC Claim Document Search

This case adds a new Workers' Claim Document Search feature. The WC Comp Claim Document Search module allows you to find Workers' Comp Claim-related documents across the system by using filtered searches. 

See Workers' Comp Claim Document Search .

50374

Parent Form field for location on the Pricing Code

This case adds the Pricing Code Location field (FieldName: fkassocatiatedlocationID) to the Pricing Comp Code dataform so that a user can analyze pricing data by location and also categorize payroll by location.

Advanced Administration

Case

Enhancement

49955

Exclude fieldsets when configuring _SetField type business rules

This case adds validation to prevent a user from saving a fieldset to the

TargetField or SourceField fields when creating or editing business rules. If a user attempts to save a business rule that contains a fieldset in either of these fields, the system will display a message to alert the user that indicates that the fieldset "<NameOfFieldset>" is not a valid field for use in business rule configuration.

50131

Suggestion: Display warning when unlocking security on data form

Previously, when adding or removing security for a dataform no confirmation message displayed that informed the user that the form security changed. Now, the system displays a confirmation message to the user when adding or removing security for a dataform.

See Adding a dataform.

50168

Update the Import Cleanup Scheduled Process to Delete Additional Import Records

This case updates the Import Cleanup scheduled process to also include deleting the following:

  • Import records with the Status of UploadComplete that are greater than 1 day old.

  • Import records with the status of ImportCanceled that are greater than 1 day old.

  • Import records with the status of ImportInProgress that are greater than 30 days old.

See Scheduled Processes for a complete list of the functionality of the Import Cleanup scheduled process.

50481

Import Past Year Payroll Batches

This case allows past year Payroll Batches to be imported.

This case adds the following scheduled processes:

  • PrismHR Import Payroll Batch Queue By Date Range

  • PrismHR Import Payroll Batch Sync

This case exposes the following fields on the PrismHR Subscription using the Payroll Schema:

  • Last Process Date

  • Number of Days to Process

After a system administrator user selects a date in the Last Process Date field and a number of days in the Number of Days to Process field on the PrismHR Subscription using the Payroll Schema, the system administrator can run the PrismHR Import Ongoing scheduled process to import the payroll batch based on the selected criteria.

Note:  The HRPAPI_payroll_batch*.csv import map must be active.

General Enhancements

Case

Enhancement

48446

Primary Location issues

This case adds the following business rules to the Client Location dataform:

  • HE_ValidatePrimaryState

  • SetPrimaryStateLocation

The system uses these rules to set the Primary State location when the Client Location is created either manually or by the PrismHR API, and the Client Location's state is unique.

49850

Dataform Link Badge Count Refactoring

This case creates an index on the foreign key when a dataform link is setup for a dataform associated with an foreign key. This change helps boost performance when the target table is large.

49910

Expose the SYS_CSNEWUSER (New User Account Authentication) email template

This case makes the SYS_CSNEWUSER (New User Account Authentication) email template available for use. A system admin user can customize this email template to include company-specific information that is useful to new hires (for example, credentials, standard procedures, etc.).

See Preloaded Alerts and Notifications.

50247

User - Calendar Sync Issue

Previously, the External Calendar URL field on a user could contain an invalid URL and return an error when attempting to sync. This case resolves this issue. The system now:

  • Disables the Sync button if the External Calendar URL field does not contain a URL

  • Disables the Sync button if the External Calendar URL field contains random text, but the system will validate the URL and display a message if the URL format is invalid

  • Attempts URL validation before accessing the remote server

  • Checks blank values on the server-side before accessing the remote server

50250

PrismHR API - USERS

Previously, when processing User Import Queue records, if the email address was bad, or there was no email address, the system marked the record as Failed.

Now, the system marks the record as Complete and adds a message to the Import Queue Log Data. For example, the system adds the following message if the user carlos had an incomplete email address:

User 'carlos' invalid or missing email address carlos@gmail, queue record automatically Completed.

See Initial Import Queue management.

50365

Bad Link Configuration Error Difficult to Find

This case adds the Link ID search filter to the More search option on the Configure Links dashboard. You can use the Link ID filter with More search to find when you have the link ID (for example, when troubleshooting a bad link that was logged in the exception log).

50375

Script to Delete Classic Dashboard modules

In this case, a script was developed to delete older Classic interface modules. This script deletes the following:

  • Sec Role Entity Records

  • Sec Entity Row Records

  • Dashboard Users

  • Dashboard itself

  • Classic Module Type Look Up Item

50482

Remove RelatedData from Filter Pages, Merges, and Reports. Use FieldProperties Instead.

This case continues converting related data functionality

Fixes

Case

Issue summary

Resolution

50225

Active checkbox on Field display rules not working

Previously, when trying to inactivate a field display rule (deselecting the Active check box), the form did not recognize that the check box had changed and did not allow the user to save the display rule. Now, the system recognizes that the Active check box value changed, and the system allows the user to save the change to the field display rule. A user can now activate or inactivate field display rules as expected.

50287

Reset Button Restored

With sprint 102, the Reset button was removed from Saved Searches. This case restores the Reset button and changes the logic to display the Reset button in all searches that use the Saved Search functionality. This case also adds logic to display the Reset button on any searches that have a Default Filter (with the exception of Custom Dataform Search Modules and Multiform Searches within a Workspace). Custom Dataform Modules and Multiform Searches within a Workspace will continue to function as they do today and only display the Clear button.

50364

Recurring Task Bug(s)

Previously, recurring tasks could lead to an infinite loop if the recurring template was marked as private (IsPrivate=True). The error could occur when the user running the scheduled process did not have access to private tasks. This case introduces a new procedure that ignores the current user and privacy filter so that the system will always process template tasks marked as private (IsPrivate=True).