Release 110 Notes

R110 Sprint: 11/1/2021 to 11/30/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.

Click to view the R110 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 11/1/2021 to 11/30/2021
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	December 7, 2021
Group 2	Second Tuesday of the month	December 14, 2021
Group 3	Third Tuesday of the month	December 21, 2021

Enhancement

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

Change in Functionality

Case	Enhancement
51032	Clone Location Data on Pricing Renewal This case introduces cloning the Pricing Code Location during pricing renewal. If the Pricing Comp Location field on the Pricing Comp Code is active and populated, the system clones the location information when a user clones a pricing batch, adds a comparison, or a user executes the Resale workflow for a Terminated client.
52962	Workflow Channel: New Option to Control if the System Triggers a Business Rule When the Last Workflow Task is Complete This case adds the Save triggering form when last task complete? field to Workflow channels. Previously, when the final workflow item in a workflow chain was completed, the system executed business rules with the Workflow Tasks Complete pipeline on the linked form. Now, the system evaluates the Save triggering form when last task complete? field upon completing the final task in a workflow chain. When selected, this field indicates that the system will trigger business rules when completing the final task in the workflow chain. When not selected, the system does not trigger the business rules when the final task in the workflow chain is complete. See Step 1: Channel.
52252	New Rule to Set Pay Frequency on Pay Group This case adds the Payroll Frequency field to the Pay Group dataform. The system uses the SetPayrollFrequency rule to determine the pay frequency. The SetPayrollFrequency rule uses the difference between the Period Start and Period End date fields on the Pay Group to determine the pay frequency. See Business Rule Methods.

Case

Enhancement

51032

Clone Location Data on Pricing Renewal

This case introduces cloning the Pricing Code Location during pricing renewal.

If the Pricing Comp Location field on the Pricing Comp Code is active and populated, the system clones the location information when a user clones a pricing batch, adds a comparison, or a user executes the Resale workflow for a Terminated client.

52962

Workflow Channel: New Option to Control if the System Triggers a Business Rule When the Last Workflow Task is Complete

This case adds the Save triggering form when last task complete? field to Workflow channels. Previously, when the final workflow item in a workflow chain was completed, the system executed business rules with the Workflow Tasks Complete pipeline on the linked form. Now, the system evaluates the Save triggering form when last task complete? field upon completing the final task in a workflow chain. When selected, this field indicates that the system will trigger business rules when completing the final task in the workflow chain. When not selected, the system does not trigger the business rules when the final task in the workflow chain is complete.

See Step 1: Channel.

52252

New Rule to Set Pay Frequency on Pay Group

This case adds the Payroll Frequency field to the Pay Group dataform. The system uses the SetPayrollFrequency rule to determine the pay frequency. The SetPayrollFrequency rule uses the difference between the Period Start and Period End date fields on the Pay Group to determine the pay frequency.

See Business Rule Methods.

ClientSpace Premium

Case	Enhancement
50718	Add New Edit SUTA Security Entity This case adds a new security entity biz_EditSUTA_After_Submit. If a user is in a role that contains this entity with the View option, the user can edit the SUTA Bill Rate until Pricing is locked (for example, when a deal is approved). Once Pricing is locked, the system does not allow editing. This case also adds the Validate SUTA Discount rule that the system will trigger on any change of the SUTA Bill Rate. This rule validates that the new rate is within the discount threshold of the user editing the rate.
50719	Add new WC Pricing Edit Security Entity This case adds a new security entity biz_EditWC_After_Submit. If a user is in a role that contains this entity with view rights, the user can edit the pricing state WC Discount and Client Modifier fields, and also override the pricing code Net Comp Rate field until Pricing is locked (for example, when a deal is approved). Once Pricing is locked, the system does not allow editing. This case also adds the Validate Work Comp Discount rule that the system will trigger anytime the Net Comp Rate field is changed by a user. This field change can occur from the Pricing State (updating Comp Discount or Client Mod fields) or directly from the Pricing Code. This rule validates that the Work Comp discount does not exceed the maximum allowed for this role.
53219	Add new Edit Administrative Fees Security Entity This case adds a new security entity biz_EditAdmin_After_Submit. If a user is in a role that contains this entity with view rights, the user can edit the Admin Fee section on the Pricing Batch and the Pricing Code until Pricing is locked (for example, when a deal is approved). Once Pricing is locked, the system does not allow editing of these fields. This case also adds the Validate Discount Thresholds rule that the system will trigger if any Admin Fee is changed (for example, Pricing Method, Admin %, Per Head Fee, Per Check Fee, or Per Invoice). This rule validates that the Total Per Head Admin Fee or Total Per Account Admin Fee is not less than the configured minimums on the Discount Threshold for this role. See Standard Security Entities .
52417	New Salesforce API parameter to Update the Workspace Name Previously, when changing the name of an organization via Salesforce import, the system did not update the Workspace to reflect that name change. This case includes a new API Config Parameter updateworkspacename. When set to 1, existing organizations that have an updated name from the Salesforce Import will also update the Primary Project Name to match. Note: Contact the ClientSpace Professional Services group to add this API Config Parameter to the Salesforce API Configuration. See Additional Parameters.

Advanced Administration

Case	Enhancement
46300	New Workflow Items Dashboard This case adds a new Workflow Items dashboard. A global admin user can access this dashboard by selecting the Workflow Items button on the Workflow Channels dashboard. Previously, when it was necessary to edit workflow items the system required an admin user to drill into each workflow channel to locate the workflow items to edit. Now, a global admin user can use the Workflow Items dashboard to find and then edit workflow items without drilling into each workflow channel. The Workflow Items dashboard provides an efficient mechanism for workflow item maintenance. For example, you can use the More search option to find all workflow items for a specific pipeline and apply edits to those workflow items. See Workflow Items dashboard.
52467	Custom Logic Rules: Feature Tags This case adds the FeatureTags lookup group and the SIDES, Pricing, PRM, and Gradient lookups to the new FeatureTags lookup group. This lookup is editable and users can add any other classifications they desire. This case also adds the following features to custom logic rules: The new Tags field allows a Global admin to categorize a rule based on the feature it is associated with. The More search option allows a user to filter search results for custom logic rules with one of the new tags. See Configuring Rules and Business Logic.

Case

Enhancement

46300

New Workflow Items Dashboard

This case adds a new Workflow Items dashboard. A global admin user can access this dashboard by selecting the Workflow Items button on the Workflow Channels dashboard.

Previously, when it was necessary to edit workflow items the system required an admin user to drill into each workflow channel to locate the workflow items to edit. Now, a global admin user can use the Workflow Items dashboard to find and then edit workflow items without drilling into each workflow channel. The Workflow Items dashboard provides an efficient mechanism for workflow item maintenance. For example, you can use the More search option to find all workflow items for a specific pipeline and apply edits to those workflow items.

See Workflow Items dashboard.

52467

Custom Logic Rules: Feature Tags

This case adds the FeatureTags lookup group and the SIDES, Pricing, PRM, and Gradient lookups to the new FeatureTags lookup group. This lookup is editable and users can add any other classifications they desire. This case also adds the following features to custom logic rules:

The new Tags field allows a Global admin to categorize a rule based on the feature it is associated with.
The More search option allows a user to filter search results for custom logic rules with one of the new tags.

See Configuring Rules and Business Logic.

General Enhancements

Case	Enhancement
52982	Add Priority and Reported By to the Column List on the Cases Module This case adds Priority and Reported By to the column list on the Cases module. These columns are hidden by default. See Search for Cases from the Cases Dashboard.
52235	Outlook Add-in Module: New Parameter to Add Email as an Activity for new Case or Task This case allows a user to configure the ShowEMBActivity parameter for the Email Addin Configuration field on an Outlook Add-in module. With this option, the system displays the Add Email as Activity check box when a user creates a new client service case or task. This check box gives the user the option to add an email as an activity when creating a new client service case or task. See Configuring the Outlook add-in module for Create.
50998	Enhance Company Merges to Include Pricing Code Location This case updated peo_merge_word_companydata to include Location Name and updated peo_merge_excel_companydata to include Location Name and Location Code.

Case

Enhancement

52982

Add Priority and Reported By to the Column List on the Cases Module

This case adds Priority and Reported By to the column list on the Cases module. These columns are hidden by default. See Search for Cases from the Cases Dashboard.

52235

Outlook Add-in Module: New Parameter to Add Email as an Activity for new Case or Task

This case allows a user to configure the ShowEMBActivity parameter for the Email Addin Configuration field on an Outlook Add-in module. With this option, the system displays the Add Email as Activity check box when a user creates a new client service case or task. This check box gives the user the option to add an email as an activity when creating a new client service case or task.

See Configuring the Outlook add-in module for Create.

50998

Enhance Company Merges to Include Pricing Code Location

This case updated peo_merge_word_companydata to include Location Name and updated peo_merge_excel_companydata to include Location Name and Location Code.

Fixes

Case	Issue summary	Resolution
53083	Field Display Rule Error When the Equals This Value Field Contains an Apostrophe	Previously, a JavaScript error could occur if a field display rule contained an apostrophe in the Equals this value field. Now, an apostrophe in this field does not cause an error when the system triggers a field display rule.
52710	The System Should Not Enforce Required Fields on Hidden Tabs When Saving Dataform Changes	Previously when a tabbed child dataform included a required field and a field display rule hid the tabbed dataform, the system did not allow a user to save the dataform. The system expected the user to enter a value for a required field even though the system hid the tab that contained the required field. Now, the system does not enforce a required field on a hidden tab and a user can save changes to the dataform.
52991	Users Dashboard Sort by Name	Previously when searching for users on the Users dashboard and sorting the results by the Name column, the system did not always sort the values in the expected order (alphabetical by last name, then alphabetically by the first name). For example, the system previously might sort users with the last name Smith as follows: Smith, Ann Smith, Alice Smith, Bob Smith, Bill Now, when sorting by the Name column, the system sorts alphabetically by the last name then alphabetically by the first name. For example, the system now sorts users with the last name Smith as follows: Smith, Alice Smith, Ann Smith, Bill Smith, Bob

Case

Issue summary

Resolution

53083

Field Display Rule Error When the Equals This Value Field Contains an Apostrophe

Previously, a JavaScript error could occur if a field display rule contained an apostrophe in the Equals this value field. Now, an apostrophe in this field does not cause an error when the system triggers a field display rule.

52710

The System Should Not Enforce Required Fields on Hidden Tabs When Saving Dataform Changes

Previously when a tabbed child dataform included a required field and a field display rule hid the tabbed dataform, the system did not allow a user to save the dataform. The system expected the user to enter a value for a required field even though the system hid the tab that contained the required field.

Now, the system does not enforce a required field on a hidden tab and a user can save changes to the dataform.

52991

Users Dashboard Sort by Name

Previously when searching for users on the Users dashboard and sorting the results by the Name column, the system did not always sort the values in the expected order (alphabetical by last name, then alphabetically by the first name). For example, the system previously might sort users with the last name Smith as follows:

Smith, Ann

Smith, Alice

Smith, Bob

Smith, Bill

Now, when sorting by the Name column, the system sorts alphabetically by the last name then alphabetically by the first name. For example, the system now sorts users with the last name Smith as follows:

Smith, Alice

Smith, Ann

Smith, Bill

Smith, Bob