Release 120 Notes
R120 Sprint: 9/1/2022 to 10/07/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 9/1/2022 to 10/07/2022 |
||
---|---|---|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
Group 1 | First Tuesday of the month | October 13, 2022 |
Group 2 | Second Tuesday of the month | October 18, 2022 |
Group 3 | Third Tuesday of the month | October 25, 2022 |
Enhancement
Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, General, and Staffing.
Advanced Administration
Case |
Enhancement |
---|---|
55222 |
Added Delete Message Enhancement for Secured Fields When you attempt to delete a dataform field that has been flagged Secured in the dataform properties, the following warning message now displays:
"Are you sure you want to delete this secured field? By doing so, it could impact your Widgets, Custom Links, etc."
The message may also include a list of places where the field is being referenced if the field is used in a workflow condition, link condition, email template condition, or business rule parameter. If the field is referenced in a business rule parameter, OR if the field is NOT being referenced at all, you can proceed with deleting the field by clicking the Delete button on the warning message. If the field is referenced in a workflow condition, link condition, or email template condition, you cannot proceed with deleting the field until the reference is removed. |
55871 |
Added _AddUserToWorkspace Business Rule Method When triggered, the _AddUserToWorkspace business rule method adds a user from a specified form and field to the workspace user list. The trigger form can be any single dataform in a workspace. The source field can be any user field on the source form. |
57184 |
Added HE_ExistingWorkspace Business Rule Method A new HE_ExistingWorkspace business rule method has been added. When triggered, if there is a workspace associated with the triggering organization, the following hard error displays: "This organization already has a Workspace associated with <WorkspaceName>. Please contact your system admin if you believe this is in error." Note: This rule must be activated before use in Custom Logic Rules System Admin > Advanced > Manage Rules. To activate, submit a case to ClientSpace Professional Services. |
57185 |
Added _RequireFieldOnForm Business Rule Method A new _RequireFieldOnForm business rule method has been added. This method allows you to make a core form field required for data entry. (Core forms, also referred to as CRM forms, are system-level forms that comprise the foundation of ClientSpace basic customer relationship management functionality. Unlike dataforms, they cannot be modified by a system administrator. You can identify core forms by their associated table names. To locate them in Custom Logic Rules, conduct a More Search and search for the following table names: Organization, Contact, Task, Calendar Event, and Users.) Once the business rule is configured and a field on a core form is specified as "required", if a user attempts to save the form without entering a value in the field, the following hard error displays: "<Field Name> is required to save this form."
Note:
|
57619 |
Enhanced the Business Intelligence Admin Dashboard The following changes have been made to the Business Intelligence Admin Dashboard. Most changes were added to support the new "Auto Archive BI Reports" scheduled process:
|
59861 |
Added Server Data Proc Secondary Trigger Fields The Secondary Trigger Field lookup on the Rule Details page (System Admin > Advanced > Manage Rules) has been updated to include Server Data Proc 1 (SDP1) and Server Data Proc 2 (SDP2) field. The SDP field names appear at the bottom of the Secondary Trigger Field list prefaced with SDP1 or SDP2.
Note:
|
General Enhancements
Case |
Enhancement |
---|---|
56667 |
Added Additional Security to Delete Secured Surcharges Previously, to delete a surcharge from the Pricing Console, a user was required to be in a role with Delete rights to the gen_surcharges security entity. If the surcharge type was secured, this access level was sufficient to delete secured surcharges. Now, if a surcharge type is secured, to delete that surcharge, a user must have Delete rights to gen_surcharges AND Delete rights to the entity generated when a surcharge type is secured.
Note: By default, Global Administrators can delete surcharges regardless of whether the surcharge is secured. Other users requiring access to delete surcharges must be assigned appropriate Delete rights. |
56810 |
Added Info Bubble Text to "Use Multi-tenancy" Field and Set Default Value Info bubble text was added to the Use Multi-tenancy field in System Admin > Administrative Data > PEO Configuration to describe how the field is used. Additionally, the field now has an initial default value of No. Previously, the initial value was empty.
Note: Contact ClientSpace Professional Services to implement multi-tenancy configuration. Do NOT try to implement this feature without ClientSpace Professional Services. Attempting to implement this feature on your own can lead to major problems with ongoing imports. |
57307 |
Increased Search Library Saved Search Limit Previously, the Search Library on ClientSpace search dashboards allowed you to create up to ten saved searches per dashboard. The new limit has been increased to twenty saved searches per dashboard.
Note: The System Default search does not count toward the twenty user-defined searches that you can create and save. See Search dashboards. |
57338 |
Added Ability to Add Duplicate Lookup Decode Values You can now add duplicate Decode values to a Lookup Group for filtering purposes. The Code values must remain unique. When adding a duplicate Decode value (with a unique Code value), the following soft error displays: "The chosen Decode value already exists for the specified Lookup Group." Click Save Anyway to add the duplicate Decode value. See Configuring lookups. |
Staffing
Case |
Enhancement |
---|---|
57664 |
Added OSHA 301 (Staffing) Merge Report A new OSHA 301 (Staffing) merge report has been added. The report is generated by clicking the OSHA 301 (Staffing) link on the Comp Claim dataform. This feature must be configured by Professional Services. If you are interested in Staffing Placement functionality in ClientSpace, please contact Professional Services. |
Fixes
Case |
Issue summary |
Resolution |
---|---|---|
56924 |
Unable to Select from Drop Down Fields on Android Mobile |
An issue was corrected in the ClientSpace mobile application on Android devices where drop down fields did not recognize the touch action and therefore did not allow value selection. |
57343 |
Dataform Fieldset Caused Text Field on Same Row to be Hidden |
When a dataform fieldset was added to Dataform Properties using the same row number as a text field on the dataform, the text field became hidden. A change was made to now display the text field directly beneath the fieldset grouping of related fields. Additionally, the following changes were made:
|
57404 |
OAuth Process Artificially Expired Tokens |
The OAuth process was artificially expiring tokens which caused ClientSpace Office 365 integration users to have to re-authenticate repeatedly. A change was made to the "refresh token" logic to automatically retrieve a new access token to connect to the Office 365 mailbox each time the email integration service is run. |
57529 |
Workflow Channel Execution Pipeline Selections Not Persisting |
When adding a new workflow channel and moving back and forth through the tabs of the Workflow Channel configuration wizard, any edits made to Execution Pipeline field were sometimes returned to default values. Now, the configured values are held (unless deliberately deleted) until the workflow channel is saved. |
57761 |
Staffing Placement Form Not Loading |
The Staffing Placement form did not load when the Comp Claim record was missing values in the Employee and Date of Injury fields. Now, if Employee and Date of Injury are not filled in and a user clicks in the Staffing Placement field on the Comp Claim Claimant tab, the following message displays: "Employee and Date of Injury are required fields for the Staffing Placement datatype. Please fill in the required fields." |