Release 102 Notes
R102 Sprint: 3/1/2021 to 3/31/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 3/1/2021 to 3/31/2021 |
||
---|---|---|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
Group 1 | First Tuesday of the month | April 6, 2021 |
Group 2 | Second Tuesday of the month | April 13, 2021 |
Group 3 | Third Tuesday of the month | April 20, 2021 |
Enhancement
Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.
Change in Functionality
Case |
Enhancement |
---|---|
49428 |
Legal Entity Defaults for New Pricing States In this case, the system will use one of two functions to determine the legal entity for a new pricing state. By default, and if the Legal Entity field on the Client Master is empty, the system will check the Contract Type to determine how to choose the legal entity. The second option will only occur if the Legal Entity field is filled in on the Client Master. If filled in, the system defaults the legal entity setting for the states to the legal entity used on the Client Master when the user saves the new state. See Creating Pricing. |
49525 |
Case Create Date/Time and Resolution Date/Time Inconsistency Previously when a user created a new case, the system adjusted the Create Date/Time to respect the timezone set in the application. However, when a user resolved a case, the system did not respect the setting for the Resolution Date/Time. This can lead to reporting issues when trying to calculate how long it took to resolve a case. Now, the system adjusts Resolution Date/Time to respect the timezone set in the application setting. |
49699 |
Lookup Import Behavior Change With this case, ClientSpace validates imports against the Group/ImportID as well as the Group/Code of the lookup so that if an ImportID is not configured the system will still find the lookup and recognize that it is a valid value. See Configuring lookups and Configuring the Import Map Detail. |
49770 |
Editor Element Type fields in Workflow Channels and Email Integration Previously, the system experienced issues with Workflow Channels and Email Integrations when referencing a dataform field that used the Editor element type. When used with Email integration, the fields were locked from editing regardless of the Field Behavior option setting for the field. For Workflow Channels, the system threw an exception error when the Field Behavior option for the field was set to Read Only. Now, when referencing a dataform field that uses the Editor element type, the field behavior performs as expected for Workflow Channels and Email Integrations. Users can edit the fields when allowed and users cannot edit the fields when the Field Behavior option is set to Read Only. |
49814 |
Changes to the 'Attach to' field in Workflow Channels This case moves the Attach to field for Workflow Channels from Step 1: Channel to Step 2: Content. See Step 2: Content. |
ClientSpace Premium
Case |
Enhancement |
---|---|
48295 |
CS API: Log Datatype - Append Data Feature This case adds the new FormatLogTypes method so that a user can use the ClientSpace API to append data to dataform fields. For example, an Employee Portal user could send cases by using the Employee Portal over the ClientSpace API into a log field and have that item append to the field. This method:
|
General Enhancements
Case |
Enhancement |
---|---|
48886 |
Employee Tax Event Mappings This case updates the employee tax event mappings to track changes to a number of Federal and State related Tax fields in PrismHR. These will create PrismHR Event records to allow triggering. See PrismHR Event Monitoring for an updated list of fields. |
48894 and 48895 |
Employee State and Federal Tax Change Email Template Notification These cases introduce the following new email templates:
|
49605 |
ClientSpace Digest Flag With this case, a ClientSpace user utilizing Sales Activity Management can enable access to the ClientSpace Digest by selecting the ClientSpace Digest field on the user profile. If this option is enabled, the system sends a notification to the user for follow-up activities when the system runs the ClientSpace Digest scheduled process. |
49691 |
Email CC Line Previously, when the system sent an email that used an email template configured with a CC address, the system did not indicate the email address of the CC recipient in the CC field. Now, a system admin user can configure email templates to use the {RecipientsTO} and {RecipientsCC} replacement fields in the Body of the message when it is necessary to display the email addresses of the TO and CC recipients in the email message. See Step 3: Addresses. |
Technical Enhancements
Case |
Enhancement |
---|---|
49757 |
New Window Opens with Error When Calendar Module is Configured to Open in a New Window Previously, ClientSpace threw an exception when the Calendar module was configured to open in a new window. Now, the window opens and functions without throwing an exception. |
49769 |
Remove RelatedData from Filter Pages, Merges, and Reports. Use FieldProperties Instead. This case continues converting related data functionality to now using FieldProperties. |
49820 |
Contact Search Procedure Performance This case increases the performance of the Contact Search procedure. |
49923 |
Workflow Error Message Detail This case improves messaging to differentiate workflow channel errors from workflow item errors. When a workflow-related error occurs, the system displays a message that correctly includes the ID of the workflow channel or workflow item. The user can use this message to troubleshoot and correct the error within the workflow. |
Fixes
Case |
Issue summary |
Resolution |
---|---|---|
49591 | No Email Address Added When Using Address Stored Procedure for DocuSign | Previously, an issue caused email addresses provided by Address stored procedures to be lost when generating emails from templates. Now, address stored procedures work as expected and provide appropriate email addresses that are used by the system when generating the email. |
49593 | Email Templates: From Address Options |
Previously, when the From Address option on Step 3: Addresses for an email template was set to use a procedure, the system did not display the existing procedure setting in the From Address Options window when attempting to edit the From Address field. Now, when a user attempts to edit the From Address field for this scenario, the system properly displays the procedure that is currently set in the From Address Options window. |
49629 |
Trigger Condition Labels not Validated Properly During the Add Process |
Previously, when adding a workflow channel or email template the labels of the triggering conditions were not validated for uniqueness. This allowed an admin to set multiple trigger conditions with the same label. The field validation did not execute until the admin attempted to save the changes to the workflow or email template. Now, the system executes field validation while the admin user attempts to set condition labels. The system does not allow the user to set two different conditions to have the same label. |
49888 | Email Template Creation: Error Presented on Addresses tab if User Previously Selected DocuSign and Switched to Email |
Previously, during the process of creating an email template, the system presented an error on Step 3: Addresses when a user had changed the Type field on Step1: Initial from DocuSign to Email. Now, if a user selects DocuSign in the Type field on Step1: Initial and then changes the type to Email, the system does not present an error when the user proceeds to Step 3: Addresses. |
50113 |
Case Subscription Issues |
Previously it was possible to customize the Client Service Case dataform in such a way that could cause dataform subscription to fail, the user could select the checkbox for a subscriber, but the system would not add the subscribers. Additionally, if a user double-clicked the row in the user list, the system threw an exception. Now, a user can double-click a user row and the system does not throw an exception. Additionally, the system adds the selected users to the Subscribers list after saving the changes. |