Release 119 Notes

R119 Sprint: 8/8/2022 to 8/31/2022. To learn about product features that you may not recognize, contact ClientSpace Professional Services.

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, General, and Staffing.

ClientSpace Premium

Case

Enhancement

57012

Added OSHA 300 and 300A Mass Creation Feature

You can now run a scheduled process that generates all OSHA 300 and OSHA 300A reports at once for all client workspaces where an OSHA Contact is identified on the Client Team page. To support this feature, the following changes were made:

  • Added a Generate OSHA Forms scheduled process.

  • Added an OSHA Process dataform to the Admin Workspace. Use it to add a yearly OSHA Process record. This record is read by the Generate OSHA Forms scheduled process to determine when OSHA reports are "Queued" (i.e., ready to be created) and which OSHA year to use for processing. Error log messages and other processing statuses (such as "Completed" or "Failed) are also recorded on the OSHA Process record.

  • Added an OSHA Forms dataform to the Client Workspace template. After the Generate OSHA Forms scheduled process runs, successfully generated reports are added as PDF attachments to the OSHA Forms dataform of each Client workspace where an OSHA Contact was identified.

See OSHA Report Mass Creation.

Advanced Administration

Case

Enhancement

56283

Added New Business Rule that Applies SUTA Rate Default for Client Reporting State

A new UpdateSUTARateForCRS business rule has been added that uses the Pricing State in combination with the related Legal Entity and Contract Type to set the SUTA Billing Rate field on the Pricing State record using the SUTA Billing Rate field value from the State Legal Entity record. In addition to updating the SUTA Billing Rate, theBilling Rate field located on the Pricing Comp Code records associated with the state is also recalculated. The rule is triggered when the SUTA - Client Report State checkbox on the State Master record is checked AND the value in the SUTA Billing Rate field on the Pricing State record is cleared or the value in the Legal Entity field on the Pricing State record is changed.

 

Note: The UpdateSUTARateForCRS business rule is inactive by default. Activate it in System Admin > Advanced > Manage Business Rules.

See Creating Pricing.

56374

Added _GAICensusValidation Business Rule Method to Automate Gradient AI Health Submissions

A new _GAICensusValidation business rule method has been added that submits offered benefits and Health Census information to Gradient AI when the Completed Health Census file upload field on the Benefits Batch dataform is populated (i.e., "Not Empty" and "Is Dirty").

 

Notes:

  • This feature requires assistance from your Salesforce system administrator. Salesforce must be configured to export completed Health Census reports and attach them to the Completed Health Census file upload fields on the correct Benefits Batch dataforms.

  • The manual submission method using the Submit to Gradient AI link on the Benefits Batch dataform remains available for use after configuring automated submissions.

  • A new Validation section has been added to the Gradient AI Health Results window to log "Accepted", "Succeeded" or "Failed" notification details from Gradient AI.

See Gradient AI Health Benefits.

56862

Added _SetFieldOnRelatedForm Business Rule Method

Added a new _SetFieldOnRelatedForm business rule method that takes a value from a field on a child form and sets it on the parent form.

See Business Rule Methods.

General Enhancements

Case

Enhancement

52274

Enhanced Docusign "Merge All Documents" with Multiple Attachments on Email Templates

Previously, signed and returned Docusign documents failed to attach if there were multiple attachments and Merge All Documents? was not checked on the Attachments tab of the Docusign email template. This issue has been corrected with the following enhancements to improve Docusign Email Template functionality.

  • When adding a new Docusign email template, the Triggering Form field value from the Initial tab auto-fills the Link To Form field on the Attachments tab. Editing the Triggering Form causes the Link To Form to reset. The Link To Form field can also be directly edited. The selection list only populates with single forms and a triggering multi-form, if applicable.

  • Link To Form is now a required field.

  • Link to Field only displays when Merge All Documents? is checked. Link to Field is NOT a required field. If Merge All Documents? is checked and a Link to Field value is not specified, the files are merged into a single file and added to the Attachments Action Center panel on the dataform

  • When Merge All Documents? is NOT checked, documents are saved in their original, individual fields in keeping with previous functionality. An enhancement was made to return supplemental documents attached to the email template to the Attachments Action Center panel on the dataform.

  • The Link To Form and Link To Field info bubbles have been updated to reflect the outlined changes to field functionality.

See Step 5: Attachments.

56481

PrismHR Link Enhanced to Support Multi-Tenancy

The PrismHR link on the Workspace Landing page has been enhanced to work with multi-tenancy environments where there are multiple instances of PrismHR and one instance of ClientSpace. When you click the PrismHR link to connect to PrismHR, ClientSpace uses the PEOID field value from the workspace's Client Master dataform to identify the correct PrismHR instance to log into.

See Multi-tenant Environments in ClientSpace.

56902

Non-System Lookup Code Values Secured After Save

Once the Code value of a lookup that does not have the System check box checked (i.e., a non-system lookup) is saved, the Code value now becomes "read only" for Global Administrators. Only users with a Developer account can edit a lookup Code value once saved.

Note: If the lookup Code is saved with an error and it is a newly added lookup that is not yet being used in the system, a Global Administrator may safely delete the lookup and re-enter it correctly. However, if you are unsure about whether it is safe to delete a lookup, please log an Extranet case.

See Configuring Lookups.

56954

Added Ability to Configure ClientSpace Behavior on Import of Invalid Email Data

On the Import Map Detail screen, when a Data Type of "Email" is selected, a new required field named Validation Behavior displays. Use this field to configure ClientSpace behavior when an invalid email address is encountered in a PrismHR import record by selecting a configuration option from the drop down list. Available options are:

  • Fail Entire Row - Fails the entire import file row when an invalid email is encountered and logs an error message.

  • Use Default Value - Allows the row to import but applies a specified Default Value setting (i.e., a permitted substitution) in place of the invalid email address in the import record.

Note: 

  • When you click the Required Value checkbox on the Import Map Detail screen and the selected Data Type is "Email", "Fail Entire Row" is set by default in the Validation Behavior field and cannot be edited (unless you uncheck Required Value). No Default Value substitutions are permitted.

  • Info Bubble text has been added to the Validation Behavior field.

See Configuring the Import Map Detail.

57108

Modified PrismHR Import API "Employment Status" Update

Previously, when an Employment record imported from PrismHR, if the first letter of the PrismHR Employment Status was "T", the ClientSpace Employment Status field was updated to "Terminated". This created an issue when Employment records with other Employment Status codes beginning with "T", such as TE (Temporary Employment), were imported as they were being incorrectly marked "Terminated". Additionally, an Employment Status that did not begin with "T", such as "Left Without Notice" could never be recognized by ClientSpace as a "Terminated" Employment Status.

Now, to determine a "Termination" code, ClientSpace uses the PrismHR Status Classification (statusCode) field. If the PrismHR statusCode is set to "Terminated", the ClientSpace Employment Status field is updated to "Terminated" and the ClientSpace Termination Date is set to the PrismHR statusDate value. If PrismHR statusCode is NOT set to "Terminated", the ClientSpace Employment Status field is updated to the value in the PrismHR employeeStatus field.

Note:  For proper record processing, Import IDs and code values in the Employment Status lookup group (System Admin > Lookups) are still required to match.

See Importing to ClientSpace.

Staffing

Case

Enhancement

56354

Added OSHA 300 and 300A Reports for Staffing

OSHA 300 (Staffing) and OSHA 300A (Staffing) reports are now available in ClientSpace. Both reports can be run from a workspace landing page. Add the report links from Custom Links (System Admin > Custom Links > Workspace Landing). Both reports are very similar to the standard OSHA 300 and OSHA 300A reports except that the filter settings on the report configuration filter pages for these reports have been modified to only display fields pertinent to staffing placement. As a result, the Contract Type, Summarize By Account, Include Terminated Clients, and Hide Location Name fields have been removed and the Client Options field has been renamed to Location Options.

See OSHA 300 (Staffing) Report and OSHA 300A (Staffing) Report.

Fixes

Case

Issue summary

Resolution

56477

Added Workflow Channel Ancestor Default and Validation for Missing Source

Previously, when adding conditions to a workflow channel, if the most recent ancestor dataform in a child workflow condition was a multi-form and you added a new trigger condition row, the Source field remained "Empty" and there was no validation to warn that the Source field needed to be completed. The broken workflow condition could then be saved to the channel. Now, when a child workflow condition is added to a workflow channel, no selections will display in the Field, Operator, and Value fields until a value is selected in the Source field. If you try to save the workflow channel without selecting a Source, an error displays. Additionally, with this update, a script will run (see Case# 56908) to remove any instances of an "Empty" Source field on previously saved workflow conditions by replacing the "Empty" value with the parent form name.

See Step 4: Conditions.

56655

Saving Current Worker's Comp Policy as the Parent Policy Created Infinite Loop

Previously, a user could specify a currently displayed worker's comp policy as the parent policy and save it, creating an infinite loop. The following error message has been added to prevent users from saving the current policy as the parent policy: "The Parent Policy may not be set to the current policy."

56770

Adding Dataform Attachment With File Name Greater than 100 Characters Caused File Save Issue

Previously, an attachment file with a file name greater than 100 characters saved without a file extension causing ClientSpace to be unable to display the saved file when a user attempted to view it. Now, file name length validation has been added to check the length of an attachment file name and limit it to 100 characters (including the file extension). File names greater than 100 characters are now truncated to 100 characters by the system.

56908

Added Script to Fix Empty Source on Workflow Channel Conditions

A script has been created to look for instances of an "Empty" Source field in a child workflow condition on the Triggering Conditions tab and set the Source field to the parent form.

Also see related Case# 56477.

56922

Date Chiclet Not Displaying on More Searches Using Date Shortcuts

Previously, when creating a More search on a date field using date shortcuts such as 30d, -30d, 5y, -5y or t, the filter chiclet for the date did not display below the search bar (in keeping with standard functionality to always show the current set of filters applied to a records list). This issue has been corrected.

57099

Modified PrismHR Initial Sync to Queue I9 Initial Import Records After Employee and Employment Records

Previously, it was possible for I9 initial import records to be processed ahead of the related employee and employment initial import records resulting in orphaned I9 records. Now, when the PrismHR Initial Sync process runs, a Pending import queue record is created for each initial Employee, Employment and I9 import map for every employee associated with a Client. Then, when the PrismHR Initial Import runs, the Pending import queue records are processed first and in this order: Employee, Employer, and I9.

See PrismHR to ClientSpace Client sync.

57144

Removed AppCode Parameter on ExportLocationToHRP (Client Location) and ExportLocationsToHRP (Client Master) Business Rules

Previously, an AppCode parameter present on the ExportLocationToHRP (Client Location) AND ExportLocationsToHRP (Client Master) business rules was incorrect and caused the rule not to work when activated. Now, the AppCode parameter has been removed from both rules.
57148

Unhandled Error Configuring Business Rules on Non-dataforms

Previously, when configuring business rules on non-dataform tables, if a user entered a value in the Primary or Secondary trigger field that did not match the field's datatype or the field was not found, the following message displayed: "An error has occurred on this page - please notify support if this error persists." Now, a more descriptive error displays: "The specified {Primary or Secondary} Trigger Field was not found or has not been configured to work with Custom Logic Rules, please contact ClientSpace professional services."

57340

Custom Font & Colors Removed Upon Form Edit

When editing a dataform field, any previously saved custom fonts and colors defined for the field label were removed. Now, custom field label changes are preserved when a dataform field is edited.

57572

SIDES: Corrected SSN and Name Not Exporting

Previously, when Unemployment Claims were posted to SIDES, the OtherSSN and ClaimantNameWorkedAsForEmployer fields were not exporting. This issue has been corrected.