Release 113 Notes
R113 Sprint: 2/1/2022 to 2/28/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.
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 2/1/2022 to 2/28/2022 |
||
---|---|---|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
Group 1 | First Tuesday of the month | March 8, 2022 |
Group 2 | Second Tuesday of the month | March 15, 2022 |
Group 3 | Third Tuesday of the month | March 22, 2022 |
Enhancement
Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.
Advanced Administration
Case |
Enhancement |
---|---|
52231 |
Add Category Filter Column and Search Criteria to the Lookups Dashboard With this case, a Global Admin user can now use the More search option to search for lookups by Filter. This case also adds the option to view the Filter column on the Lookups dashboard. |
53598 |
New parameter for the _GenerateMergeFile method: Trigger save before generating a merge file This case adds the SaveRecord method parameter to the _GenerateMergeFile method. If the SaveRecord checkbox is checked, then the dataform records will be saved before generating the merge file and the merge will contain the new data. |
53872 |
Add Time to Audit Trail Search With this case, a ClientSpace user can determine the time that a field audit occurred so that it is easier to troubleshoot and track changes. Now, the Date column on the Audit Trail returns the datetime instead of just the date. The system orders the column by datetime. |
53890 |
Add Tags and Pipeline Columns to the Custom Logic Rules Dashboard This case adds Tags and Pipeline to the column list on the Custom Logic Rules dashboard. These columns are hidden by default. |
General Enhancements
Case |
Enhancement |
---|---|
52077 |
Contact Export Enhancement - Export updates Note: Contact ClientSpace Professional Services to implement this feature. With this case, the system exports any changes to contacts from ClientSpace to PrismHR when a user changes any of the following contacts fields in ClientSpace:
Note: If these fields changed due to the PrismHR API, the system does not export the change to PrismHR. |
53425 |
UI Change: Workflow History Link Added to Links Panel in the Action Center Previously, the Workflow History option was available as an action item button in the Action Center toolbar drop-down to only Global Admin and Developer users. This case removes the Workflow History action item button from the toolbar and adds a Workflow History link in the Links panel of the Action Center. The Workflow History link is available to Global Admin and Developer users by default. Additionally, the workflow history link is available to users in a role that contains the Can_Access_Workflow_History security entity. The system will only display the Workflow History Link on dataforms or tasks that were generated by a workflow channel. |
53846 |
PrismHR Event Record Created Before Employee Created in ClientSpace Previously, it was possible that a PrismHR Event record (such as a direct deposit event) could be created for an employee in PrismHR who was not yet in ClientSpace. This case adds the AssociatePrismEvents rule that the system triggers when importing a new employee. This rule analyzes all PrismHR events missing an fkemployeeID in the current workspace by trying to match on the Employee Identifier. If a match is found, the PrismHR Event will have the fkemployeeID set to that employee. If the rule does not find any events, the system does nothing. |
53933 |
Changes to ExportLocationsToHRP Rule on Client Master This case updates the following settings for the ExportLocationsToHRP business rule:
|
Fixes
Case |
Issue summary |
Resolution |
---|---|---|
53038 |
DocuSign and Radio Button Signature Type |
This case removes the Radio Button option from the Signature Type drop-down on Step 3: Addresses for DocuSign templates. Note: It is still possible to configure Radio Buttons as a custom type within DocuSign. |
53959 |
Department Missing On New Broker Users |
With this case, when a user in the Brokers department adds a new agent, the system will now set the department to Brokers for the new agent user . |
54003 |
Exception Occurs due to the Offered Benefits Plan Business Rule when fkBenefitPlanID is Read Only and has a NULL Value |
Previously, the SetCategory method on the Offered Benefits Plan business rule could cause an exception to be thrown if the fkBenefitPlanID is not set (NULL). This can occur because sometimes fkBenefitPlanID is set to Read Only. If fkBenefitPlanID is read only, a value can not be set. This case, adds the Require Benefit Plan business rule. Now, an exception does not occur for this scenario, instead the system displays a hard error. |
54161 |
System Allows Users to Delete the Field Selected as Default Field on Dataform Properties |
Previously, the system allowed a Global Admin user to delete a dataform field when that field was set as the Default Field for that dataform. Now, the system prevents a user from deleting a Default Field and displays a message to indicate why. The following graphic illustrates this scenario:
The Global Admin user must select a different Default Field for the indicated dataform before the user can delete the field. |
54273 |
Field display issue when adding a dataform and the value for the triggering checkbox is false |
Previously, when adding a dataform, the system did not respect the field display rule setting to hide an item if the value for the triggering checkbox was false (unchecked). This case updates field display rules to respect both true and false values for checkbox triggers when adding a dataform. |
53482 |
Improve the 'Submit to Gradient' error output |
With this case, when a state-code combination fails for a user who is using Gradient AI for pricing, the user can now determine which state-code combination is failing. The system now returns the specific record that is causing the hard error. The user can use the record data to fix the error and re-submit. |
53903 |
User Expiration Date Exception |
Previously, an exception occurred when setting the Date to Expire for a user to a date that was 68 years in the future or 68 years in the past. This case resolves this issue. |