Release 107 Notes
R107 Sprint: 8/1/2021 to 8/31/2021. 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, and General.
Change in Functionality
|
Case |
Enhancement |
|---|---|
| 50221 |
Case type option to set a client role as the backup assignment With this case, a Global Admin user can select a single user or a user role in the Backup Assigned To field when editing a client service case type, and the Default Assignment field contains Client Role. Selecting a client role instead of a single user allows the admin to dynamically assign the backup user based on the workspaces configured client team form. This mirrors the Assigned to user functionality. See Adding Case Types. |
| 50253 |
Client Master: Clearing ImportID on client master clears ImportID on client master and child dataforms With this case, when a user with access to the field clears the Client Number on a client master and saves the change, the system will clear the ImportID for the Client Master and all child forms. This will affect the following forms:
|
| 50918 |
Cases module optimized for case resolution searches In this case, we optimized the Cases module to now include the Resolution date in the More search. We also removed lesser used filters to help improve performance of the module when searching in large data sets. The original module is still available in the modules section, now called Cases-Old. See Cases Dashboard. |
| 52134 |
Increase the limit for the number of characters that the system can copy between dataforms This case changes the _SetFieldFromFormOnForm method to increase the limit for the number of characters that the system can copy between dataforms. When the system executes a rule that a Global Admin user configured to use the _SetFieldFromFormOnForm method, the system can now copy up to 500 characters from the source field on the source dataform to the target field on the target dataform. |
ClientSpace Premium
|
Case |
Enhancement |
|---|---|
| 50996 |
Add Pricing Code Location Field to the Upload Pricing Console Pre-Load .CSV This case adds the Pricing Location to the Pricing Console Pre-Load .CSV template so that imports can include pricing code locations. See Creating Pricing. |
| 51909 |
Pricing: Enhancing Quick Create/Edit Pricing to include new Location field With this case, a salesperson can set the Location of the Pricing code during the quick edit so that they do not have to take additional steps to set the location separately. Note: The Location field must be active in the Pricing Comp Code form for the Location field to be available in the pricing grid. The Location field is inactive by default. See Creating Pricing. |
Advanced Administration
|
Case |
Enhancement |
|---|---|
| 49874 |
Dataform Fields: Field label updated for the IsIndexed dataform field This case changes the label for the IsIndexed dataform field from Index this Field to Include in Document Index. This case also updates the tooltip for the field to the following: "Include this field when indexing documents attached to this form so that it can be used as part of the document search." |
| 50896 |
Dataform Fields: New style tool to customize the style of dataform fields With this case, a Global Admin user can change the style of a field when editing the Dataform Properties. An admin user can select the settings option and set the following styles for a field:
|
| 50897 |
Email Templates: New options to include first and last name of user who generates the email template (current user) This case adds the ability to set the From address of an email template to the user who is triggering the notification. This case adds:
|
General Enhancements
|
Case |
Enhancement |
|---|---|
| 50690 |
Reactivate case when a reply comes through case discussion The system evaluates this rule when a new discussion message is received after the case is in the Resolved status and inactive. This rule will reactivate the case by triggering business logic with a HdrAction of Activate. To utilize this function, activate the ReactivateCase rule on the Discussion Message dataform. |
| 51609 |
Update ImportIDs on related dataforms if client number keyed prior to Implementation status Previously, if a client number was keyed in prior to Implementation status, child forms would not have their ImportIDs set. This case ensures that system updates related form ImportIDs if the Client Number is entered prior to Implementation status. |
Technical Enhancements
|
Case |
Enhancement |
|---|---|
| 52086 |
PrismHR Ongoing Import (HRPAPI_I9): New message scenario when employee is deleted in PrismHR before Clientspace receives I9 data Previously, if the system created an I9 import record and the status of an employee in PrismHR changed from CREATED to DELETED before ClientSpace retrieved the I9 data, the system marked the queue record as FAILED. This occurred because the system could not find the employee entity. Now, after the PrismHR Ongoing import runs for this scenario, the system marks the queue record as COMPLETE - FAILURE and logs a message that includes the employee ID (empoyeeId) and the client number (clientNumber). For example, the system displays the following message for employee M01628 and client 188. Employee 'M01628-188' has been deleted from PrismHR, queue record automatically Completed. |
Fixes
|
Case |
Issue summary |
Resolution |
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 52182 |
Multiple Email Templates associated with a dataform |
Previously, when more than one email template was configured to trigger on the same dataform from the same triggering event, and the email templates used different merge procedures, the system would not process all of the merge procedures. This case added a method to properly evaluate merge procedures for subsequent email templates in this scenario. |
||||||||||||
| 50968 |
Manual Rate on Pricing Code Defaulting Issue |
Previously, the manual rate on a pricing comp code would default to values other than 0.0000 when using quick create pricing for a contract type with a Comp Model set to N/A. This case changes the quick create pricing calculation process for states that are not using Workers' Comp. Now, when generating pricing, the system defaults the manual rate to 0.0000 on the pricing comp code for the affected state. |
||||||||||||
| 51392 |
Work Item Behavior |
Previously, if a user selects a Work Item in the Work Center (left navigation window) and the user moves the item down the list, the item remains selected when the user moves the cursor to the right (out of the Work Center pane). Now, when the work item is dropped after the cursor moves out of the Work Center, the work item will be re-ordered based on where the cursor crosses into the frame. |
||||||||||||
| 51621 |
Nested Fieldsets on Metadata dataform |
Previously, when a metadata dataform that was configured to use nested fieldsets was used in a lookup group, editing the associated lookup would cause the system to throw an error. This case fixes the lookup details so that lookups can use nested fieldsets without throwing an error. |
||||||||||||
| 51772 |
Payroll Batch Imports, missing PayDate |
Previously, payroll batch records that did not have a payDate value could cause the system to throw an exception while constructing the PayrollBatch dataform data. This could leave the import queue record in Pending status. Now, the system marks the queue record as Complete with the following message: "Pay date is required to import payroll batches into ClientSpace" |
||||||||||||
| 51901 |
Location Exports to PrismHR |
Previously, when exporting a list of Client Location records from the Client Master to PrismHR, the export could fail and cause the system to create new and empty Client Location records. These failures occurred due to the system dropping the primary key (PK) of the ClientSpace location during the export process. This case resolves the creation of blank location records. and now the system updates the export status and system log for the following scenarios:
|