Release 112 Notes

R112 Sprint: 1/1/2022 to 1/31/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.

Enhancement

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

ClientSpace Premium

Case

Enhancement

53427

Batch in repricing override

Occasionally, when pricing is running, an error can occur that leads to locking the Batch in Repricing checkbox in the selected position. This case adds a new link on the Pricing Batch called Override 'Batch in Repricing'. By selecting this option, the system will clear the Batch in Repricing checkbox bypassing any rule validation. This is secured to the can_override_batchinrepricing entity and will need to be added to a role to utilize this function.

53594

Quick Create - Location/State Code Error

Previously, a validation error occurred when adding the same state and code combination, during quick create, in the pricing console. Now, users can add multiple versions of the same state and code combinations (both before and after generating pricing).

Advanced Administration

Case

Enhancement

53643

Cannot Inactivate or Deactivate Field Due to Field Style Settings

Previously, a user could not delete or inactivate a field on a dataform if that field included Default Style configuration settings at the field level. Now, a user can delete or inactivate a field for this scenario.

General Enhancements

Case

Enhancement

52240

Display a User's Department

This case adds the new Department Code field to the Department Details.

Configuring this field setting will force display of the department code in user datatypes for any user that has a default department configured. For example, user datatype fields will now display the Username [DeptCode] in the drop-down. A ClientSpace user can also search the user drop-down for a department code (using %DeptCode) so that assigning items to a user of a specific department is easier.

53151

Home Page - Task Refresh

With this case, tasks and task information that display in the Task Manager widget on the Home page update after a user selects a task from the list and saves a change to the task. For example, if the user updates the subject or due date, the system updates the subject and due date that display in the Task Manager widget. Also, if a user selects a task from the Task Manager and completes the task, the system removes the task from the Task Manager widget.

53698

Display Links When Using Lookup Values Without Metadata as the Status on an Organization or Client Master

With this case, if a lookup value is selected as the status on the organization or client master, and metadata does not exist on that lookup for the CRMOrganizationStatus or ContractStatus groups, the system displays the Create Prospect and Create Client links by default.

53797

Reply Template field on Email Integration Displays the Template ID and not the Template Name

Previously, when you added a new email integration and selected the Reply Template on step 2 - Action, the Reply Template field displayed the name of the template. But, when you advanced to step 3 - Field Mapping and then returned to step 2 - Action, the Reply Template field displayed the email template ID, not the name of the template. Now, the system displays the name of the template in the Reply Template field when this scenario occurs.

53885

Email Integration Oauth Button Displays Instead of Password Button

Previously, the system displayed the Oauth button when an Admin User set the type for an email integration to Office 365, even if the type was later changed to Other. This prevented the admin from changing the authentication type of an Outlook account when the user wanted to return to using BASIC authorization. Now switching the authentication Type allows the user to freely switch between the following:

  • Other, the system displays the Password button

  • Office 365, the system displays the Oauth button

Technical Enhancements

Case

Enhancement

53588

Update Pricing Code Location field from "One to One" to "One to Many"

This case changes the One to One parent form details setting on the Pricing Code Location field of the Pricing Comp Code dataform. Now the default setting for the One to One check box is unchecked (which means that the field is now set as One to Many). This change allows a Global Admin user to add a link to the Client Location to display all associated codes.

Fixes

Case

Issue summary

Resolution

52466

Saving Dataforms with Hidden Tabbed Forms

With this case, when a tabbed form is saved the system does not create dataform records for hidden tabs. If a hidden tabbed form contains required fields, the system does not enforce requiring those fields since the tabbed form is hidden. If a record already exists for the hidden tabbed form, the system excludes that record from consideration during the save process.

See Configuring Dynamic Field Display.

53465

Exception: Conversion from string to type 'Date' is not valid

This case resolves an issue that caused an exception due to the event time when creating a calendar event from the Client Visit form. Now the system properly handles the conversion of time values in the "VisitDateTime" field.

53644

User Profile Display a Save & New Button

Previously when a user selected My Profile and clicked Apply to save changes to the user profile, the system refreshed the page and displayed a Save & New button. The Save & New button is not necessary when a user edits their user profile. This case updates the system to no longer display the Save & New button on the user profile page after the user applies an edit to their profile.

53901

No subjects with the CSCDISCNEW template

Previously, the system did not populate the subject line for an email sent to an internal user notifying them that an external user replied on a Discussion Message. This case resolves this issue and displays the subject as expected.

54253

PrismHR API No Error Message for Failed Client Export

Previously, exporting a client sometimes resulted in a failure without displaying a reason in the Export log. This case adds additional error messaging to the Export Client business rule. The system now displays a reason in the log.