Release 118 Notes

R118 Sprint: 7/1/2022 to 8/5/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.

Click to view the R118 release schedule.

The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for ClientSpace Professional Services.

Sprint 7/1/2022 to 8/5/2022
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	August 9, 2022
Group 2	Second Tuesday of the month	August 16, 2022
Group 3	Third Tuesday of the month	August 23, 2022

Enhancement

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

ClientSpace Premium

Case	Enhancement
53932	Added "Submit w/Action (close and refresh)" Action to Benefits Batch Renew Link Previously when clicking the Renew link on a benefits batch, the renewed plan remained open. A Submit w/Action(close and refresh) action was added to the Renew link to automatically close the renewed benefits batch and refresh the Benefits Batch list.
56253	Added Claim Notes Report Link to Comp Claim Dataform. A new Claim Notes report link has been added to the Comp Claim dataform. When the link is clicked, a report showing claim notes related to the current claim is displayed. The report displays Note Category, Subject, Notes, and Additional Details.
56696	Added Subject Field and Enhanced Notes Field on Claim Notes Dataform The following updates were made to the Claim Notes dataform: A Subject field has been added. The Notes field has been changed from a Text field to an Editor field with a formatting toolbar for advanced text editing. Use the formatting toolbar to add bold type, change the font size or color, add bullets or numbering, insert links and more. Note: Any formatting of Claim Notes (such as carriage returns or line breaks) entered prior to this update will be preserved.

Case

Enhancement

53932

Added "Submit w/Action (close and refresh)" Action to Benefits Batch Renew Link

Previously when clicking the Renew link on a benefits batch, the renewed plan remained open. A Submit w/Action(close and refresh) action was added to the Renew link to automatically close the renewed benefits batch and refresh the Benefits Batch list.

56253

Added Claim Notes Report Link to Comp Claim Dataform.

A new Claim Notes report link has been added to the Comp Claim dataform. When the link is clicked, a report showing claim notes related to the current claim is displayed. The report displays Note Category, Subject, Notes, and Additional Details.

56696

Added Subject Field and Enhanced Notes Field on Claim Notes Dataform

The following updates were made to the Claim Notes dataform:

A Subject field has been added.
The Notes field has been changed from a Text field to an Editor field with a formatting toolbar for advanced text editing. Use the formatting toolbar to add bold type, change the font size or color, add bullets or numbering, insert links and more.

Note: Any formatting of Claim Notes (such as carriage returns or line breaks) entered prior to this update will be preserved.

Advanced Administration

Case	Enhancement
43523	Enhanced Business Rules Parameters Dataform to Allow Trigger Value Selection from Drop Down Primary and Secondary trigger values are now selectable from a drop down list when the associated Primary or Secondary trigger field is a HdrAction or a Lookup. See Configuring Rules and Business Logic.
55980	Added Parent Form Field Validation to Prevent Dataforms With Identically Named Fields From Being Added as Tabbed Form Validation now occurs on parent forms to check for identically named fields in a tabbed form relationship. If one or more identically named fields is found between the two forms, an "Unable to save Tab Form" error displays. The validation error occurs when: Adding a new tabbed dataform to a parent form where there are one or more identically named fields between the two forms. Editing two dataforms already in a tabbed form relationship where the user attempts to add a new field with a name that matches a field on one of the tabs. The error lists all conflicts that must be corrected in order to save the tabbed form relationship. Note: The system will not allow duplicate field names even if the datatypes of the conflicting fields are different. See Adding dataform tabs.

Case

Enhancement

43523

Enhanced Business Rules Parameters Dataform to Allow Trigger Value Selection from Drop Down

Primary and Secondary trigger values are now selectable from a drop down list when the associated Primary or Secondary trigger field is a HdrAction or a Lookup.

See Configuring Rules and Business Logic.

55980

Added Parent Form Field Validation to Prevent Dataforms With Identically Named Fields From Being Added as Tabbed Form

Validation now occurs on parent forms to check for identically named fields in a tabbed form relationship. If one or more identically named fields is found between the two forms, an "Unable to save Tab Form" error displays. The validation error occurs when:

Adding a new tabbed dataform to a parent form where there are one or more identically named fields between the two forms.
Editing two dataforms already in a tabbed form relationship where the user attempts to add a new field with a name that matches a field on one of the tabs.

The error lists all conflicts that must be corrected in order to save the tabbed form relationship.

Note: The system will not allow duplicate field names even if the datatypes of the conflicting fields are different.

See Adding dataform tabs.

General Enhancements

Case	Enhancement
52722	Enhanced Milestones Widget Functionality You can now pin a selected project milestones category as the default view by clicking the Pin icon in the upper right corner of the Milestones widget. The pinned filter remains the default widget display until you click the pin again to restore the system default view. See Widget: Milestones.
54762	Updated CSCDISCNEW Template to Capture External Sender Email Address, First Name and Last Name The CSCDISCNEW Template has been enhanced to include the sender email address, first name, and last name on new email replies to case discussion emails. Two field replacements are now available to configure to capture this information: {LASTREPLY_FromEmailAddress} - This will be decoded as the sender email address. {LASTREPLY_FromName} - This will be decoded as the sender First and Last name separated by a space. See CSCDISCNEW: Case Discussion New Template.
55274	Added Incident.pkIncidentID Replacement Field for Email Templates Triggering from Tasks Incident.pkIncidentID is now available in the list of Replacement fields. This list is accessible from the Content step of email template configuration by clicking See Replace Fields.
55994	Enhanced Watch Widget Functionality The following enhancements were made to the Watch widget: After selecting a dataform to pin, a Select Date window now displays which allows you to select the review date. The watch item name is now comprised of the value in the dataforms Default field followed by the workspace name in parenthesis. Up to 50 characters are displayed. If the watch item name is more than 50 characters, an ellipsis displays after the character limit is met. Hover your mouse pointer over the watch item to see the full description. See Widget: Watch.
56470	Added Enhanced Salesforce API v3 Error Logging with Client Master Duplicate Import Validation Salesforce API v3 can now be configured to log Client Master import hard errors on the Salesforce API pipeline to both the ClientSpace Scheduled Process History log and the Salesforce Work Queue. Once this feature is configured, if failures occur, the Work Queue record will be marked Completed and failures are recorded in the Salesforce field configured in the API record as the workqueueerrorfieldname parameter. This prevents Client Master records with hard errors from importing into ClientSpace. Since failed records are marked Completed, Salesforce Work Queue errors can be reviewed and corrected and manually marked as not completed in the queue. Then, the work queue records can be processed again with the next scheduled import. Hard errors logged in Salesforce are preceded by 4 dashes as shown in the example below: Note: This feature requires configuration assistance from the ClientSpace and Salesforce system administrators. See Salesforce API v3.
56687	Improved Info Bubble Text for Workflow "Channel Owner" The Workflow Channels info bubble text for both the Channel Owner field (new workflows) and Owner field (existing workflows) has been updated to the following: "This user is the responsible user for the Workflow Channel. On a Task, if the Assigned To or Owner fields cannot find a user to fill these fields it will default to the Channel Owner."
56697	Added Create Claim Notes Module for Outlook Add-In A Create Claim Notes module has been added for the Outlook Add-In. This module adds a Create Claim Notes link to the Post To ClientSpace page of the External Mailbox for Outlook. When the link is clicked, you can post the subject line and body details of a selected email as a note on a Comp Claim record within a specified Workspace. Note: Subject line and body details are added to the Comp Claim Note by default. These settings can be changed by editing the Email Addin Configuration field on the Module Details record. To activate the Create Claim Notes module, go to System Admin > Modules, locate and open the Module Details record, and click the Active checkbox. See Configuring the Outlook add-in module for Create and Creating Activities, Cases, Tasks, and Claim Notes from Outlook.
56708	Added Case Discussion Attachments Link and New Security Role Entity gen_DiscussionMessage A Discussion Attachments link has been added to the Client Service Case dataform. The Discussion Attachments link opens a window listing all attachments added to all case discussions associated with a case. The attachments are in order by Discussion Subject and you can click an attachment name in the list to download it. A new gen_DiscussionMessage security entity has been added to the Case Discussion and Discussion Attachments dataforms to allow system administrators to allow or deny access to Case Discussions functionality. Previously, the Case Discussion dataform was an unsecured form open to all users. Therefore, to prevent current security role settings from being impacted, with this update, the gen_DiscussionMessage security entity is added to the EVERYONE role with View, Add, and Edit access set. See Adding case discussions and Standard Security Entities.
56986	Added OAuth (Office 365) Email Integration App Record for All Sites Previously, the OAuth (Office 365) Email Integration record was not available for all sites. With this update, the app configuration has been added in System Admin > Advanced > Third Party Applications for all sites. See Email Integration.

Staffing

Case	Enhancement
56698	Added Ability to Refresh ClientSpace Staffing Placement List and Placement records with PrismHR Staffing Placement Data A Refresh Placement List link has been added to the Comp Claim dataform. When the link is clicked, ClientSpace uses the PrismHRAPI to make API calls to PrismHR for the list of placements as well as for the placement data. The Client Number and Employee ID are used to match to the correct employee in PrismHR. If a new staffing record is found, a new record is created in ClientSpace. If a staffing record exists but has been updated in PrismHR, the record is also updated in ClientSpace. At the end of the process, a progress window will either show "Refresh Completed Successfully" or an error message indicating why the refresh could not complete. See Refreshing the Staffing Placement List and Error messages: ClientSpace and PrismHRAPI Staffing Placement Refresh.
56736	Added Comp Claim Date of Injury Validation to Staffing Placement HE_ValidateDOIStaffingPlacement Rule The HE_ValidateDOIStaffingPlacement business rule has been updated to validate the Date of Injury (DOI) field on the Comp Claim form. If the Staffing Placement field on the Comp Claim Claimant tab is updated and contains a value, the validation checks the following: The DOI cannot be missing. The DOI must be on or after the Staffing Placement Start Date and the DOI must fall within the range of the Start Date and End Date on the Staffing Placement form. (The latter validation step only occurs when an End Date has been entered).

Case

Enhancement

56698

Added Ability to Refresh ClientSpace Staffing Placement List and Placement records with PrismHR Staffing Placement Data

A Refresh Placement List link has been added to the Comp Claim dataform. When the link is clicked, ClientSpace uses the PrismHRAPI to make API calls to PrismHR for the list of placements as well as for the placement data. The Client Number and Employee ID are used to match to the correct employee in PrismHR. If a new staffing record is found, a new record is created in ClientSpace. If a staffing record exists but has been updated in PrismHR, the record is also updated in ClientSpace. At the end of the process, a progress window will either show "Refresh Completed Successfully" or an error message indicating why the refresh could not complete.

See Refreshing the Staffing Placement List and Error messages: ClientSpace and PrismHRAPI Staffing Placement Refresh.

56736

Added Comp Claim Date of Injury Validation to Staffing Placement HE_ValidateDOIStaffingPlacement Rule

The HE_ValidateDOIStaffingPlacement business rule has been updated to validate the Date of Injury (DOI) field on the Comp Claim form. If the Staffing Placement field on the Comp Claim Claimant tab is updated and contains a value, the validation checks the following:

The DOI cannot be missing.
The DOI must be on or after the Staffing Placement Start Date and the DOI must fall within the range of the Start Date and End Date on the Staffing Placement form. (The latter validation step only occurs when an End Date has been entered).

Fixes

Case	Issue summary	Resolution
56536	All Errors Occurring On "Generate Scheduled Workflows" Processor Were Not Logged and Did Not Reference Channel ID	All errors that occur from running Generate Scheduled Workflows (ScheduledWorkflowProcessor.GenerateWorkflow) now display in the error log and include a reference to the Channel ID number.
56579	"Failed to load dashboard "<DashboardName>" Error Clicking Design/Edit on Business Intelligence Dashboards	Corrected a missing folder name in the Business Intelligence Admin Design/Edit link that caused an error when clicking Design/Edit from the Business Intelligence Admin search page.
56583	Pay Frequency Field Not Validated on Pricing Console Quick Upload	Pricing Console Quick Upload validation was updated to check the value in the Pay Frequency field against valid and active code values in the Pay Frequency Lookup Group. Invalid entries result in the display of a validation error.
56677	"Error rebuilding dataform file index" on Document Indexing.	Updated a stored procedure to stop document indexing errors from occurring in the Document Search module when the File Management Cleanup scheduled process runs.