Release 101 Notes
R101 Sprint: 2/1/2021 to 2/28/2021. To learn about product features that you may not recognize, contact your Customer Success Manager.
Release schedule
Release updates are implemented by the group, as indicated in the following table.
The release schedule is subject to change and updated as required. To determine your group or ask questions, please log a case for Professional Services in the Extranet.
Sprint 2/1/2021 to 2/28/2021 |
||
---|---|---|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
Group 1 | First Tuesday of the month | March 9, 2021 |
Group 2 | Second Tuesday of the month | March 16, 2021 |
Group 3 | Third Tuesday of the month | March 23, 2021 |
Enhancement
Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.
Change in Functionality
Case |
Enhancement |
---|---|
46811 |
Remove Overall Pricing Breakdown from GAs Previously, Global Admin users did not require a role with a security entity to see the Overall Pricing Breakdown. With this case, Global Admins can no longer see the Overall Pricing Breakdown without the addition of the biz_pricingconsole_breakdown security entity to the Global Administrators Role or another role to which the user is a member. |
47364 |
Drag and Drop for Work Items With this case, a user can move Work Item Sets within the Work Center to change the order in which the system displays the Work Item Sets. See Work Center. |
48493 |
Filter Benefit Plan field on Offered Benefit Plan to remove Expired Plans Previously all benefit plans appeared in the Benefit Plan field drop-down of an Offered Benefit Plan dataform for a workspace. This included the old expired plans, which made it difficult for users to find the active plans in the drop-down. Now, the Benefit Plan field drop-down on the Offered Benefit Plan dataform only shows the active plans. |
49298 |
OSHA | History (Prior Years) This case adds a new parameter to the PrismHR API to denote the number of years of OSHA totals to get from PrismHR content. See Ongoing Imports: Configuring the API for Import Map Details and OSHA 300A Report Details. |
49498 |
Out of Office-Include Name with Inbox Notifications In the R100 ClientSpace release, a change was made to the Out of Office Email notifications to include the name of the original recipient in the Subject line. This previous change only applied to outgoing Email notifications and did not include a users' Inbox notification. This update applies the same changes to the Inbox notifications in ClientSpace. |
ClientSpace Premium
Case |
Enhancement |
---|---|
47983 |
Surcharge Selector Confirmation Message This case adds a confirmation dialog message that the system displays for a user to confirm that surcharges were added to the Pricing Console. |
48492 |
View in Salesforce Link With this case, a ClientSpace user can access SalesForce directly from ClientSpace so that the user can easily see the lead in SalesForce without the need to go out of ClientSpace to do so. The Organization record now includes a View in Salesforce link. When a user selects the link, a new browser opens to the SalesForce login page. Once logged in, the user is directed to the Client from which the user accessed the link. Before you can implement this functionality, you must submit a case with the ClientSpace Professional Services team. |
Advanced Administration
Case |
Enhancement |
---|---|
47934 |
BI Name isn't disabled after form save when Exclude from BI is set to true Previously, when the Exclude from BI field was set to True, the BI Name field was disabled to not allow data entry into the field. However, when the dataform was refreshed, the BI Name field was enabled again when the field should have remained disabled. Now when the Exclude from BI field is set to True and the dataform refreshes, the BI Name field is properly disabled (no entries allowed in the field). |
49053 |
#CurrentWorkspace For Run BI Report Custom Links This case enhances custom links that are configured to run a BI report. A user can configure a custom link to run a BI report without the need to configure a custom link URL and specify a form ID or project ID in the URL for the report. Now, when a user selects the BI report link on a dataform or workspace, the system appends &formid= and &projectid= to the end of the URL and indicates the proper form and project ID numbers for the current dataform or workspace. |
General Enhancements
Case |
Enhancement |
---|---|
47941 |
Reset Button on Saved search With this case added the reset button to any Search dashboard that users can save a search on. Previously, users could not reset the search. Users needed to close the module and reopen it to reset the Search. Now, users can click the Reset Button. |
47968 |
CSCDISCCONFIRM Renamed for Future Removal With this case, it was determined that the CSCDISCCONFIRM email template is no longer needed. The name of the CSCDISCCONFIRM email template was updated to CSCDISCCONFIRMOLD to indicate that the template is old and no longer necessary. This template will be removed in a future release. |
48497 |
Case Discussion Responsive Design This case updates the responsive design layout for a mobile browser while using the Case Discussion feature, by better utilizing the white space within the browser window. |
48994 |
Client Team: Client Contacts Section This case adds the following fields to the Worksite Contacts fieldset of the Client Team dataform so that information can be included when sending notifications to worksite contacts:
|
Technical Enhancements
Case |
Enhancement |
---|---|
46381 |
New Rule to Run When a User Attempts to Create an External Source Linking Record Added a new rule to prevent duplicate External Source Linking Records to be created when adding from a link. |
48873 |
Mark for Deletion - Mass Update This case adds the ability for Global Admin users to mass delete tasks by using the Mass Update feature found on the Task Manager dashboard. The Mass Update dashboard includes a Mark for Deletion option. If a Global Admin user selects this option and then runs the Delete Marked Tasks scheduled process, the system removes any tasks that the Global Admin user selected for mass update. Note: Only a Global Admin user can use this option. |
49392 |
Imports, Exceptions in Dataform Save Logic Previously, during an Import, if an exception occurred during the dataform save, a general error message was set on the Import row. This message lacked details for users to troubleshoot and resolve import issues. Now, the system logs an appropriate exception in both the Import logs and the exception log. |
49535 |
Email Integration: Invalid Characters in Email Body This case includes changes to prevent any issues from processing Single Quotes (') in the Email Body. The Email Body now displays Single Quotes (') if they are present. |
49576 |
Improve performance of the WC Claims Dashboard for Large Data Sets This case includes adjustments to the WC Claims dashboard to improve performance by loading information faster for large data sets. |
49585 |
Improve performance of the Contacts Dashboard for Large Data Sets This case includes adjustments to the Contacts dashboard to improve performance by loading information faster for large data sets. |
Fixes
Case |
Issue summary |
Resolution |
---|---|---|
49357 | Task Field Auditing Not Working As Expected |
With this case, the Incident table column fkUserID was added to the table configuration to audit the Task Assigned To field. Now, tasks that the system generates from workflow channels display the Assigned To User. |
49556 |
In Person Signer source of Address Stored Procedure doesn't work |
Previously, the system displayed a text box for the In Person Signer Name field when a user selected Address Source Procedure in the Source field and In Person Signer in the Type field on Step 3- Addresses when creating a DocuSign email template. Now, the system displays a drop-down for the In Person Signer Name in this scenario, and the drop-down displays a list of selectable options from the Address Stored Procedure. |
49646 |
XML Error Processing Email Integration if Dataform Field Mapping Contains |
Previously, if field mappings for an email integration configuration contained a text area or log field that contained a period (or other standard punctuation) prior to a field replacement string, the system failed during dataform creation and threw an exception. Now, if the system cannot properly decode a field replacement string, the system will capture the exception and continue with evaluating the next field replacement string. This case also corrects the issue with field replacement failing when standard punctuation is used. |
49677 |
SetFieldOnFormFromForm |
This case fixes an issue where users tried to use the SetFieldOnFormFromForm business rule targeting attachment fields. If the source field was empty, an error would occur. This error no longer occurs. |
49783 |
OSHA - Inactive Location Record - Obsolete Date |
This case updates the PrismHR OSHA location data. This process will now retrieve OSHA location data for inactive locations. This will still take into account obsolete location logic. |
49813 |
Email Integration Line Break Preservation |
This case resolves an issue with line breaks in HTML-enabled emails. Previously, when HTML-enabled emails were used with email integration and the body was mapped to a TextArea, the <br> tags were removed. This resulted in the email lines displaying on a single wrapping line in the TextArea. Now, the system properly handles the <br> tags and content displays with line breaks. |
50016 |
Multiple Emails Triggering |
This case added logic to prevent saving Stale/Duplicate/Invalid Primary Trigger Conditions on Email Templates. Changing primary triggers will no longer cause issues with triggering. |
50017 |
Pricing Batch Delete Exception |
Previously, when attempting to delete a Pricing Batch and Client Activity records existed for that batch, an unhandled exception was thrown. This case adds Client activity records to the delete to prevent errors from occurring. Now, the system deletes the batch as expected. |
50059 |
Attach To - Include the Triggering Form |
This case fixes an issue with the Attach To lookup in Workflow Channels so that the value of Triggering Form is included. |