Release 115 Notes

R115 Sprint: 4/1/2022 to 4/30/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 groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.

Change in Functionality




Multiform Search "More" Criteria Ordering

The More search option now considers the row number of fields within fieldsets when displaying the order of the fields in the search option.


Workflow Attachment Link

There is now a Link tab on the Attachments panel of Workflow Channel Configuration. Use this option to add a link to the dataform or task that the system creates when a workflow triggers. The Link can be accessed through the Link Tab under the Workflow Attachment section on the cloned record.

See Workflow Channel Action Items.


Added UI Claims Dashboard Enhancements

The following enhancements have been made to the UI Claims Dashboard:

  • Added a State lookup and a State Claim Number field to the More search and made the columns hidden by default.

  • Added a Source lookup to the More search in the Advanced Filters section.

  • Docket Number is now a hidden column by default.

  • Claims not associated with Employee are now visible in the grid.

See Managing Unemployment Claims.


Require Linked Form Field on Task

Previously, ClientSpace users could add a task from an Organization or Contact that was not attached to a dataform. Now, security role entity Incident_Can_Add_Without_Dataform can be set to allow or disallow adding a task not attached to a dataform. The following changes have been made:

  • To prevent current security role settings from being impacted, with this update, the Incident_Can_Add_Without_Dataform entity is added to the EVERYONE role with View access set. This allows users to save a task not associated with a dataform just as in prior versions.

  • A Related Form field with Link to Dataform auto-filled now always displays at the top of the Task entry form.

  • If a user is assigned to a role where the Incident_Can_Add_Without_Dataform entity is set to View, clicking Apply or Save on the Task entry form allows the user to save without selecting a related form.

  • If a user is assigned to a role where the Incident_Can_Add_Without_Dataform entity is not set to View, clicking Apply or Save on the Task entry form without selecting a related form results in a "Related form cannot be Empty" error displaying. To proceed, the user must click in the Related Form field and select the Record Type and Record (i.e., related form) from the Link Form window and then click Apply or Save.

The following graphic illustrates the Link Form window.

See Adding tasks.


Employee/Employment Field Locking

Previously when the Source field on the Employee dataform was set to External System, the system did not disable some fields in the New Hire field set of the Employee dataform. Additionally, the system did not disable fields in the Employment Information field set and the Compensation Information field set of the Employment dataform.

Now, the system disables the fields as expected. When the Source field on the Employee dataform is set toClientSpacethe system enables these fields.


Salesforce Import Lookup/Multilookup Default Value

Previously the Default Value configuration specified on the Import Map Detail dataform for Salesforce Import Mapping did not work with Multiform lookups. Now, when a Default Value of Current Value is selected, and the value from Salesforce is blank, the current values in the field will be preserved. When a Default Value of Specific Value is selected, and the value from Salesforce is blank, the specified value is used. When a value is retrieved from Salesforce, the lookup is set to the value imported from Salesforce.


OSHA Locations Scheduled Processes Exclude Obsolete Locations

Updated the PrismHR Import OSHA Location Data and PrismHR Import OSHA Location Data CLIENT scheduled processes to exclude OSHA Location Totals on obsolete locations if the Obsolete Date on the Client Location dataform does not fall within the current OSHA year (or years). OSHA Location Totals will only be imported and used on the OSHA Log reports (300, 300A) if the following rules apply:

  • Location is Active and Obsolete Date is empty.

  • Location is Active and Obsolete Date is within the current OSHA year (or years) selected.

  • Location is Inactive and Obsolete Date is within the current OSHA year (or years) selected.

Note: The PrismHR Import OSHA Location Data CLIENT scheduled process includes one year of locations data. The PrismHR Import OSHA Location Data scheduled process includes up to 3 years of locations data as determined by the OSHAYearsToProcess API parameter.

See Scheduled Processes.


Added Role Security to Delete Validation of Organization Category Security

When a user attempts to delete a role that is in use in Organization Category Security, the system now displays a message that alerts the user that this role is tied to an existing Organization security category. The message includes links that will allow the user to delete these categories. Once the relationships are removed the user can delete the individual security role. The Delete button will be inactive until all such records are re-configured to use a different role or deleted.


Email Add-in Attaching to Inactive Records

Previously when using the email add-in, the system attached the email to a case, but the contact field could pull an inactive contact if there was an active and inactive record with the same email.

Now, when the system creates the email activity the system prioritizes active contacts over inactive contacts. When assigning the primary contact on the activity, the system will use the first email recipient and the active contact with that email address. If more than one contact is active, or if all contacts are inactive the system sorts priority by date updated.


Template User Saved Searches Copy to New Users

Saved dashboard searches from a template user record are now applied to new user records created from the template user record and to existing user records that have a new template applied.

See Adding and editing user accounts.

Advanced Administration




Create Pipeline Linking Table and Expose On UI

A new Pipeline Linking table (System Admin > Pipeline Linking) has been added to allow you (Global Administrators) to define which Pipeline Behaviors can be applied in the following functional areas: Rules, Import Mapping, Email Templates and Workflow Channels. You define which behaviors can be applied by reviewing each Pipeline record in the Pipeline Linking table and setting one of the following behaviors for each functional area within the selected Pipeline:

  • Default

  • Allow

  • Disallow

Upon updating a record, the Pipeline Linking table filters the Execution Pipeline field in each of the aforementioned functional areas using the Pipeline Behavior designations you set.

This change will not impact existing Execution Pipeline entries until you edit the entries.

The Pipeline Linking table includes preloaded Pipeline Names that match the current Pipeline Lookup Decode names in the Lookups table as illustrated in the graphic below:

Pipeline Linking to Pipeline Lookup Comparison

If you have custom pipelines, our Professional Services staff can assist you in adding them.

See Configuring Pipeline Linking.


Added Create Task Rule to Handle Incident Data Import

A Create Task rule that uses the CreateTask business rule method has been added. The CreateTask method is used on the Import_Incidents dataform to import historical incident data from another application into ClientSpace tasks within the correct Workspaces. The Import_Incident dataform is an existing dataform used in other import processes. It is where imported incident information is temporarily stored until the task information is extracted from it. To support the new CreateTask method, the Import_Incident dataform was modified to include the following new import fields:

  • Assigned To

  • Send Notification

  • More Info

  • Completed

  • Delete

  • External Object

  • Search ID

Once the CreateTask business rule method is triggered, an Import_Incident file is uploaded through Import Management, the file is processed, and each row is read and stored in the Import_Incident dataform until the task is generated. Then, the dataform is deleted. Any errors encountered during file processing are stored in the Import Log (without any disruption to Import_Incident file processing). Finally, the imported task information is imported into new ClientSpace task records within the correct Workspaces.

See Business Rule Methods.


User Templates Notification Message: Applying Template User Change

This case adds the Applying Template User Change notification message when applying a template user to a new user. Previously the system only displayed the message when editing an existing user. If you select a value in the Template User field for a user, the system displays the Applying Template User Change message. Click Yes to continue and use the template user settings for the current user that you are creating or editing.

The following graphic illustrates the Applying Template User Change message.

See Adding and editing user accounts.

General Enhancements




Update the User Audit Trail when a Developer User Moves a Dataform to Another Workspace

In this case, the system logs dataform moves in the User Audit Trail when a developer user moves a dataform from one workspace to another.


Enhance Case Escalation User Re-assignment Parameters

This case updates the Client Service Case Escalation dataform so that it is now possible to escalate a client service case to users in a more dynamic way. For example, previously a set of client service case escalation parameters could only indicate a specific user in the Next assigned To User field on the form. The system then assigned the case to the indicated user. Now, client service case escalation parameters can be set to a user by indicating any of the following methods:

  • A single user

  • A client team role

  • The department manager of the Assigned To user for the case

  • The immediate supervisor of the Assigned To user for the case

See Case Escalation.


Added New Link Display Action

A new link display action called Submit w/Action (close and refresh) has been added to the Display Action lookup on the Configure Links Detail form (System Admin > Advanced > Custom Links). This display action generates a HdrAction on the page to trigger rules or workflow. Then, the page closes and the list containing the record the action occurred on is refreshed.


Deleting/Inactivating Fields - Shows Duplicate field names

This case updates the Confirm Delete message that displays when a user attempts to delete a dataform field that includes a dependency (for example, the field is in use in an email template, workflow item, field display rule, or custom link trigger). The Confirm Delete message now includes a link that a user can click for the system to direct the user to the field dependency (for example, the workflow that references the field). This allows the user to quickly resolve the issue by selecting a different field for the indicated system function. After resolving the dependency, the user can proceed with deleting the dataform field.


Added MarkRehire Business Rule

Added a MarkRehire business logic rule that sets the Rehire checkbox on the Employment dataform to checked. The rule is triggered when an employee’s Employment Status is updated from Terminated to Active and the Last Hire Date is different from the Original Hire Date. This change will be pushed out as active for all clients.

See Business Rule Methods.

Technical Enhancements




Improve Message for an Email Template Trigger Condition Exception

Previously, when an error occurred with an Email Template condition, the system displayed an error message that did not provide details necessary to troubleshoot the issue. For example, "An error occurred trying to evaluate an Email Template Trigger Condition Expression. Trigger Condition ID: 1461"

Now, if an error occurs with an Email Template condition, the system displays an error message that includes the Template Code from the EmailTemplate and the Trigger Condition Expression. For example, "An error occurred trying to evaluate the trigger condition for Email Template <templatecode> Trigger Condition Expression: "


Email Integration Exceptions - Include Details That Indicate Source of the Exception

With this case, when the system generates an exception from an email integration, the exception now returns the email integration configuration name and the API Config App Code in the message for the failed email integration that triggered the exception. Now, a Global Admin user can better identify email integrations that fail.


API - Invalid JSON Response

Previously, if data was submitted with an invalid JSON format, the system threw a null reference unhandled exception. The exception did not help a developer determine how to resolve the issue. This case changes the API so that all methods that bind a request parameter from [FromBody] now return a message explaining the invalid JSON format.


Pipeline Linking Core Drift + Default Insert Script

Added the following two internal scripts to assist the Product Management team in supporting customers who have custom pipelines and who want to use the new Pipeline Linking functionality included with this release.

  • Pipeline Linking Core Drift - Gets a list of a customer's custom pipelines that need to be added.

  • Default Insert Script - Inserts the default pipelines and behaviors in the Pipeline Linking table to match the standard, core Pipeline Lookups.



Issue summary



Workflow Channel Duplicates When Workflow Set To Trigger Only Once

This case fixes an issue when evaluating cascading workflows and the Only trigger this workflow once option is set. Now, the system will prevent cascading workflows from cloning the same item multiple times.


Pricing Codes without Locations Display NULL in the States and Codes List

Previously, when a pricing comp code did not include a pricing code location, the system displayed "null" in the Location column in the State and Codes section of the Pricing Console. Now when a pricing comp code does not have a defined pricing code location the system displays an empty string instead of "null" in the State and Codes section of the Pricing Console.


Do not display Email Integration API Configuration Options in the API Configuration Drop-down

This case updates the system to not display email type API configurations in the API Configuration drop-down when configuring third party applications or when using the More search for the Uploaded Files Queue.


The _SetFieldFromProc method validation Does Not Handle Time datatype

This case fixes an issue in the _SetFieldFromProc method validation.

Previously, the method validation rejected SQL Server Time datatype for Time fields on a dataform.

Now, when a custom logic rule uses the _SetFieldFromProc method, the rule will set Time datatype fields properly for Time fields on a dataform.


Improve Email Add-in efficiency: Refactor the cs_uploadedfileslinking_i_copy Stored Procedure

This case improves system efficiency with the email add-in by refactoring the cs_uploadedfileslinking_i_copy stored procedure.


Clear Field on Disable/Hide Check Box Disabled for Fieldsets

This case disables the Clear Field on Disable/Hide check box on field display rules for fieldsets. Clearing fields is not a valid option for fieldsets.


User Profile Save Error

Previously, some users reported an issue where they could not update their profiles (for example, name, phone number, email, etc.). This issue occurred when the DefaultProjectID field on their user record contained -1. This case includes a script that sets the DefaultProjectID on the Users Table to 0 when the DefaultProjectID equals -1. This update resolves the user profile change issue for this situation.


Trailing Space on SetFieldFromForm Parameter

Previously, when the system validated the fields entered in the TargetField and the SourceField parameters for the _SetFieldFromForm business rule method, the system did not properly validate fields. If a user entered a field name that contained a trailing space in the field name, the system validated the field even though the field name was invalid. Now, the system trims any training spaces in the field name before validating the field.