Release 125 Notes

Added "Set Expiration Date" Business Rule

A new Set Expiration Date business rule for the Offered Benefits Plan dataform has been added. This rule uses the _SetFieldFromRelatedForm method and is deployed as an Inactive rule. It updates the Expiration Date field value on the Offered Benefit Plan record with the Expiration Date field value on the associated master Benefit Plan record to ensure that selected benefit plans exported to PrismHR have the correct expiration date. The field update occurs when you click the workflow link to select the Offered Benefit Plan.

See Configuring Benefit Plan API Business Rules.

Enhanced Datatype Validation for Multiple Business Rule Methods

Previously, datatype validation on the following "set field" and "stage changes" business rule methods did not warn you of invalid configuration where the TargetField and SourceField datatypes were mismatched:

• _SetFieldFromForm

• _SetFieldOnFormFromForm

• _SetFieldFromLookupMetadata

• _StageChangesOnFormFromForm

• _SetFieldOnRelatedForm

• _SetFieldFromRelatedForm

The datatype incompatibility between the TargetField and SourceField resulted in exception errors when the rule was triggered. Now, the validation rules function as follows: 

• If the TargetField and SourceField values share the same datatype, validation passes on Save. Example: Text to Text.

• If TargetField value datatype is NOT the same as the SourceField value datatype but IS of another compatible datatype, validation passes on Save. Example: Currency to Decimal.

• If the TargetField value datatype is NOT the same as the SourceField value datatype and is NOT of another compatible datatype, the following soft error message displays: "The TargetField '<TargetField Value>' on Dataform '<Dataform Name>' may not be compatible with the SourceField '<SourceField Value>'. Do you wish to continue?"

   

  The soft error allows you to continue with the Save but if you do not correct the issue, errors may occur when the rule is triggered.

Note: In cases where there is not an exact datatype match, validation against a list of other compatible datatypes may not be exhaustive.

See Field Datatype Validation - Compatible Datatypes and Configuring Rules and Business Logic

Enhanced Error Message When Adding Duplicate Department and Department Name Change Enhancement

Previously, when you added a new department (System Admin > Department) and it could not be created because duplicate Member and Admin roles already existed, the error message was not meaningful and only indicated that "something went wrong during the save". Now, when you add a new department that cannot be created because duplicate Member and Admin roles exist, the following error message displays: 

"The Role Name '{DepartmentName}_Admin' or '{DepartmentName}_Member' cannot be duplicated so this department cannot be created. You must update the department name or alter the existing roles before proceeding."

Additionally, an enhancement was made to automatically update associated role names (System Admin > Security > Roles ) when you update a department name.

See Configuring Organization and Workspace Security and Administering role security.

Made CSCDISCEMINT Email Template Generally Available

The CSCDISCEMINT email template is used to send notification messages to external users when a discussion response has been posted to the thread. This template is part of the standard PEO installation but was not available at sites by default. With this update, a script will run that makes the CSCDISCEMINT email template available as an active and published template at all sites. Validation is in place to only add the template where it does not already exist to prevent duplication.

Previously, if you made changes in PrismHR to a Job Code, the HRPAPI_Ongoing scheduled process did not update affected ClientSpace workspaces with the changes. A stored procedure change was made to correct this issue.

Previously, the UI Claims module dashboard did not display SIDES claims that were added by default to the Client Services Department workspace due to a missing Client Master or employee association. Now, these claims display in the UI module dashboard. Additionally, you can now use the Client field in the More search to filter for the Client Services workspace and you can also use the Move Claim button (located in the top right corner of the dashboard) to move a Client Services claim to another workspace.