Release 98 Notes
R98 Sprint: 11/1/2020 to 11/30/2020. 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 11/1/2020 to 11/30/2020 |
||
---|---|---|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
Group 1 | First Thursday of the month | December 3, 2020 |
Group 2 | Second Tuesday of the month | December 8, 2020 |
Group 3 | Third Tuesday of the month | December 15, 2020 |
Enhancements
Enhancements groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.
Change in Functionality
Case |
Enhancement |
---|---|
47938 |
Replace Fields: Filter by name For Workflow Channels and Email Templates, you can now search the available replace fields. Additionally, the source sections are collapsible and display a counter. This enhancement saves you time using Filter by name versus scrolling for fields. See Replacement Fields. |
46614 |
Client Master: Terminate logic moved to Save pipeline The Terminate link on the Client Master now creates the client Termination form through a Save pipeline. This enhancement means that you can trigger tasks when the Terminate link is activated to trigger workflow off the form creation. That workflow is then attached to the Termination record. |
45776 |
OSHA 300 & 300A: Locations and Location Totals The Location dataform has two new fields: Related to Another Location? and Related Location. This enhancement enables users to associate locations with other primary locations for OSHA reporting needs. For example, a user can associate a work from home location with the physical company location. Related Location is not an API managed field. It is maintained manually in ClientSpace.
Claim information (for the 300 report) and claim OSHA location totals (for the 300A report) for locations with a related location are added to the OSHA reports' related locations. To run a report for a location with a related location, manually select the location on the filter page. Keep in mind these totals are already included in the related locations report. See OSHA 300 Report Details and OSHA 300A Report Details. |
46560 |
DocuSign: Fail notification A new System Email Template now triggers when a DocuSign send fails. The failure initiates a notification to the user with a brief explanation. The email template is Active by default. See Notifying users of status. |
General Enhancements
Case |
Enhancement |
---|---|
46840 |
Case Discussions: Date-time stamp When viewing case discussions in the discussion thread, messages from the reply above the line functionality now show a date-time stamp. |
47736 |
Surcharge Type: Field renamed The field Is Cloned with Pricing Batch was renamed to Is Cloned with Pricing Renewal. The new name better matches the functionality of the field. Additionally, an info bubble was added: Check this box to copy this Surcharge to the new Pricing Batch during the renewal process, but only if it exists in the current pricing batch. |
47459 |
Business Intelligence: Delete from BI Admin Developer users can now delete items directly from BI Admin, making it easier to remove items that are no longer needed. This enhancement eliminates the need for development to perform deletes. See Business Intelligence Admin. |
48633 |
File upload hard error methods New methods were added for configuring rules:
See Business Rule Methods. |
|
ClientSpace Help ClientSpace Help topics now indicate:
|
Technical Enhancements
Case |
Enhancement |
---|---|
47247 |
Email Integration: Communication Method On case creation, your values for the Communication Method field are now used. If the field is has a value, the mapped value is used. If the field is empty, it is set to Email Integration. See Case creation methods and Step 3: Field Mapping. |
48374 |
Dataform API: ProjectID On Dataform saves, if the ProjectID does not exist or is not valid, ClientSpace does not create the record and issues an error message. |
48262 |
JavaScript: Moved JavaScript Pages now load correctly due to moving a JavaScript method for Email Templates and Workflow Channels. |
47842 |
Dataform: Save error Resolved an error when retrieving a dataform record through the web service when ProjectType and TableName were empty. |
46981 48645 48607 |
Performance Performance indices were added for Projects.fkTemplateID. The stored procedure peo_clientteam_u_teamrole_users was refactored to improve performance. Search was enhanced to improve performance. |
43381 |
Core rule parameter validation A validation was added to _SetFieldValue to verify the field exists on the targeted form. Additionally, the value is trimmed to remove trailing spaces. |
48461 |
PrismHR API: Initial Employee Sync scheduled process The Initial Employee sync scheduled process was refactored. This process now correctly functions when there are multiple API Configurations (of type PrismHR API) active on an install. It now processes all ClientSpace Clients for all API Config records. The process stays active until all associated Employee queue records are completed. See Scheduled processes. |
48271 |
Deprecated Template Task Triggering Template task triggering was removed from the dataform pipeline. |
45918 |
Deprecated ProjectUserGroup table Multiple procs were refactored to remove references to ProjUserGrp and ProjectUserProjUserGrp. |
Fixes
Case |
Issue summary |
Resolution |
---|---|---|
47446 |
Foreign key constraint error |
When importing loss runs, comp claims now update when there is no associated Workers’ Comp Policy. When the import is an update and a policy is not found, an error message is issued. |
48719 | Contact ID value not extracting |
Resolved an issue for Clients with SyncWithPrismHR enabled. When the Import Initial Sync scheduled process runs, Contacts for those Clients are now correctly imported into ClientSpace. |
48842 | Scheduled WFC triggering and attaching Tasks where they do not belong | Resolved an issue where scheduled Workflow Channels triggered extra items that share the same channel. This now works as expected, triggering the required workflow items. |