Release 123 Notes

R123 Sprint: 12/1/2022 to 01/10/2023. 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 R123 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 12/1/2022 to 01/10/2023
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Thursday of the month	January 12, 2023
Group 2	Third Tuesday of the month	January 17, 2023
Group 3	Fourth Tuesday of the month	January 24, 2023

Enhancement

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

ClientSpace Premium

ClientSpace API

Case	Enhancement
53552	Added New Task Methods to Version 2.0 of ClientSpace API A new Task section has been added to version 2.0 of the ClientSpace API. The Task section is not in Version 1.0 of the ClientSpace API. This section contains four new methods: GET method for searching for tasks (i.e., incidents) - Any data that can be retrieved by manual search can be retrieved using this method. It runs the same process that is run when you perform a manual More search in Task Manager. GET method for retrieving a task by ID - Note that you can use a workspace/project ID or a client ID. PATCH method for updating fields in a task record - This is different than a PUT method that replaces the entire task record. You can specify specific fields to update. POST method for creating a new task. Detailed documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding the desired method. Click Model to see model definitions as shown in the example below: Click Example Value to view and copy sample code as shown in the example below: Note: The new task methods are only available in version 2.0. Version 2.0 does not replace version 1.0. Version 2.0 is available by request. Please contact Professional Services for more information.
57530 / 59779	Added Updated File Methods and File Versioning to Version 2.0 of ClientSpace API In version 2.0 of the ClientSpace API, updated file methods have been added to improve file versioning, including new methods for inserting, updating and deleting versioned files using file or link guids as appropriate. A new method was also added for downloading a specific file by file guids. Detailed documentation for client developers can be found in the Swagger interface by expanding the File section and then expanding the desired method. Click Model to see model definitions as shown in the example below: Click Example Value to view and copy sample code as shown in the example below: Note: The updated file methods are only available in version 2.0. Version 2.0 does not replace version 1.0. Version 2.0 is available by request. Please contact Professional Services for more information.
57773	Added New Time Tracker File Methods to Version 2.0 of ClientSpace API A new Time Tracker section has been added to version 2.0 of the ClientSpace API. The Time Tracker section is not in Version 1.0 of the ClientSpace API. This section contains four new methods: GET method for searching for Time Tracker records - Any data that can be retrieved by manual search can be retrieved using this method. It runs the same process that is run when you perform a manual More search on the Time Tracker dashboard. GET method for retrieving Time Tracker records using the Time Tracker ID. PATCH method for updating fields in a Time Tracker record and linking it to a record ID - This is different than a PUT method that replaces the entire Time Tracker record. You can specify specific fields to update. POST method for creating a new Time Tracker record and linking it to a record ID. Detailed documentation for client developers can be found in the Swagger interface by expanding the Time Tracker section and then expanding the desired method. Click Model to see model definitions as shown in the example below: Click Example Value to view and copy sample code as shown in the example below: Note: The new Time Tracker methods are only available in version 2.0. Version 2.0 does not replace version 1.0. Version 2.0 is available by request. Please contact Professional Services for more information.

Case

Enhancement

53552

Added New Task Methods to Version 2.0 of ClientSpace API

A new Task section has been added to version 2.0 of the ClientSpace API. The Task section is not in Version 1.0 of the ClientSpace API. This section contains four new methods:

GET method for searching for tasks (i.e., incidents) - Any data that can be retrieved by manual search can be retrieved using this method. It runs the same process that is run when you perform a manual More search in Task Manager.
GET method for retrieving a task by ID - Note that you can use a workspace/project ID or a client ID.
PATCH method for updating fields in a task record - This is different than a PUT method that replaces the entire task record. You can specify specific fields to update.
POST method for creating a new task.

Detailed documentation for client developers can be found in the Swagger interface by expanding the Task section and then expanding the desired method.

Click Model to see model definitions as shown in the example below:

Click Example Value to view and copy sample code as shown in the example below:

Note:

The new task methods are only available in version 2.0.
Version 2.0 does not replace version 1.0.
Version 2.0 is available by request. Please contact Professional Services for more information.

57530 / 59779

Added Updated File Methods and File Versioning to Version 2.0 of ClientSpace API

In version 2.0 of the ClientSpace API, updated file methods have been added to improve file versioning, including new methods for inserting, updating and deleting versioned files using file or link guids as appropriate. A new method was also added for downloading a specific file by file guids.

Detailed documentation for client developers can be found in the Swagger interface by expanding the File section and then expanding the desired method.

Click Model to see model definitions as shown in the example below:

Click Example Value to view and copy sample code as shown in the example below:

Note:

The updated file methods are only available in version 2.0.
Version 2.0 does not replace version 1.0.
Version 2.0 is available by request. Please contact Professional Services for more information.

57773

Added New Time Tracker File Methods to Version 2.0 of ClientSpace API

A new Time Tracker section has been added to version 2.0 of the ClientSpace API. The Time Tracker section is not in Version 1.0 of the ClientSpace API. This section contains four new methods:

GET method for searching for Time Tracker records - Any data that can be retrieved by manual search can be retrieved using this method. It runs the same process that is run when you perform a manual More search on the Time Tracker dashboard.
GET method for retrieving Time Tracker records using the Time Tracker ID.
PATCH method for updating fields in a Time Tracker record and linking it to a record ID - This is different than a PUT method that replaces the entire Time Tracker record. You can specify specific fields to update.
POST method for creating a new Time Tracker record and linking it to a record ID.

Detailed documentation for client developers can be found in the Swagger interface by expanding the Time Tracker section and then expanding the desired method.

Click Model to see model definitions as shown in the example below:

Click Example Value to view and copy sample code as shown in the example below:

Note:

The new Time Tracker methods are only available in version 2.0.
Version 2.0 does not replace version 1.0.
Version 2.0 is available by request. Please contact Professional Services for more information.

Other ClientSpace Premium

Case	Enhancement
59375	Added "State Record Request ID" to UI Claims Dashboard "More" Search A State Record Request ID field was added to the "Advanced Filters" section of the More search of the UI Claims Dashboard to make it easier to find SIDES claims. Note: The entire State Record Request ID must be entered exactly in order to return a result. See Managing Unemployment Claims.

Case

Enhancement

59375

Added "State Record Request ID" to UI Claims Dashboard "More" Search

A State Record Request ID field was added to the "Advanced Filters" section of the More search of the UI Claims Dashboard to make it easier to find SIDES claims.

Note: The entire State Record Request ID must be entered exactly in order to return a result.

See Managing Unemployment Claims.

Advanced Administration

Case	Enhancement
58347	Enhanced SetfieldFromRelatedForm Business Rule to Set a Field from a Different Workspace Previously, the SetfieldFromRelatedForm business rule was used to set a field on a form with a field value from another form within the same workspace. The SetfieldFromRelatedForm business rule has now been enhanced to also set a field in one workspace with a value from a related form that is in a different workspace (such as the Admin workspace). In the case of the Admin workspace, this would allow a field such as the Expiration Date on an Offered Benefit Plan located on a Client Workspace to be set using the Expiration Date on the Master Benefit Plan located on the Admin Workspace. Multiple other use cases apply as this rule will set any field across workspaces as long as there is a parent form field connecting the two forms. See Business Rule Methods.

Case

Enhancement

58347

Enhanced SetfieldFromRelatedForm Business Rule to Set a Field from a Different Workspace

Previously, the SetfieldFromRelatedForm business rule was used to set a field on a form with a field value from another form within the same workspace. The SetfieldFromRelatedForm business rule has now been enhanced to also set a field in one workspace with a value from a related form that is in a different workspace (such as the Admin workspace). In the case of the Admin workspace, this would allow a field such as the Expiration Date on an Offered Benefit Plan located on a Client Workspace to be set using the Expiration Date on the Master Benefit Plan located on the Admin Workspace. Multiple other use cases apply as this rule will set any field across workspaces as long as there is a parent form field connecting the two forms.

See Business Rule Methods.

General Enhancements

Case	Enhancement
57503	Changed the Display of Unpublished Top-Level Workflow Channel Items to Bold, Italicized Unpublished top-level workflow channel items now display bold and italicized so you can distinguish active workflow items at-a-glance. This change applies to: Unpublished workflow items viewed from the Conditions tab of Workflow Channel Configuration (System Admin > Workflow Channels > Open Workflow Channel > Open Workflow Item > Go To Conditions tab). Unpublished Workflow items viewed from the Workflow Channels search list (System Admin > Workflow Channels > Select Workflow Channel> Click Workflow Items button located above the grid). Unpublished Workflow items viewed from the Workflow Channel Item list (System Admin > Workflow Channels > Open Workflow Channel> Items List displayed at bottom). See Viewing and publishing Workflow Channels, Searching Workflow Items, and Configuring Workflow Items.
58346	Separated Payroll Batch Processing from PrismHR Import Ongoing Scheduled Process Payroll batch processing has now been removed from the PrismHR Import Ongoing scheduled process and given its own scheduled process. The Ongoing import will still generate the Queue records in pending status, but the Payroll batch records will be retrieved from PrismHR and the Queue records completed by the new Payroll Batch Ongoing scheduled process. This change was made because the processing of a large number of Payroll batches created system performance issues (in some instances) when processed with other imports in the PrismHR Import Ongoing Scheduled Process. The new scheduled process is called PrismHR Import Payroll Batch Ongoing. Note: The PrismHR Import Payroll Batch Ongoing scheduled process has a limit of 250 payroll batch records that may be returned for processing at one time. See Configuring the Payroll Batch Scheduled Processes and Scheduled Processes.
60246	Added "Owner" Field to Client Service Case Dataform A new Owner field has been added to the Client Service Case dataform. It is Inactive by default. The Owner field was added to allow you to make a distinction between the person designated in the Assigned To field and the case Owner. The Assigned To name represents the person working on the case while the Owner represents the person taking responsibility for the outcome of a case. Info bubble text has been added to the field with the following field definition and additional guidance: "The person who is taking responsibility for the outcome of the case is the Owner. If changing this field, remember to add an Internal Note to avoid confusion for the re-assignment of the Owner."

Case

Enhancement

57503

Changed the Display of Unpublished Top-Level Workflow Channel Items to Bold, Italicized

Unpublished top-level workflow channel items now display bold and italicized so you can distinguish active workflow items at-a-glance. This change applies to:

Unpublished workflow items viewed from the Conditions tab of Workflow Channel Configuration (System Admin > Workflow Channels > Open Workflow Channel > Open Workflow Item > Go To Conditions tab).
Unpublished Workflow items viewed from the Workflow Channels search list (System Admin > Workflow Channels > Select Workflow Channel> Click Workflow Items button located above the grid).
Unpublished Workflow items viewed from the Workflow Channel Item list (System Admin > Workflow Channels > Open Workflow Channel> Items List displayed at bottom).

See Viewing and publishing Workflow Channels, Searching Workflow Items, and Configuring Workflow Items.

58346

Separated Payroll Batch Processing from PrismHR Import Ongoing Scheduled Process

Payroll batch processing has now been removed from the PrismHR Import Ongoing scheduled process and given its own scheduled process. The Ongoing import will still generate the Queue records in pending status, but the Payroll batch records will be retrieved from PrismHR and the Queue records completed by the new Payroll Batch Ongoing scheduled process. This change was made because the processing of a large number of Payroll batches created system performance issues (in some instances) when processed with other imports in the PrismHR Import Ongoing Scheduled Process. The new scheduled process is called PrismHR Import Payroll Batch Ongoing.

Note: The PrismHR Import Payroll Batch Ongoing scheduled process has a limit of 250 payroll batch records that may be returned for processing at one time.

See Configuring the Payroll Batch Scheduled Processes and Scheduled Processes.

60246

Added "Owner" Field to Client Service Case Dataform

A new Owner field has been added to the Client Service Case dataform. It is Inactive by default. The Owner field was added to allow you to make a distinction between the person designated in the Assigned To field and the case Owner. The Assigned To name represents the person working on the case while the Owner represents the person taking responsibility for the outcome of a case. Info bubble text has been added to the field with the following field definition and additional guidance: "The person who is taking responsibility for the outcome of the case is the Owner. If changing this field, remember to add an Internal Note to avoid confusion for the re-assignment of the Owner."

Staffing

Case	Enhancement
56993	Added Staffing Lookup to Contract Type Lookup Group and Moved PEO ID Field A new Staffing lookup value has been added to the Contract Type lookup group (located in the Additional Company Info field set) of the Client Master dataform. This allows you to flag that a PEO client is also a Staffing Placement client. Also, the PEO ID field has been moved to the Contract Information field set.

Case

Enhancement

56993

Added Staffing Lookup to Contract Type Lookup Group and Moved PEO ID Field

A new Staffing lookup value has been added to the Contract Type lookup group (located in the Additional Company Info field set) of the Client Master dataform. This allows you to flag that a PEO client is also a Staffing Placement client. Also, the PEO ID field has been moved to the Contract Information field set.

Fixes

Case	Issue summary	Resolution
58269	"RenameWorkspaceWithClientNumber" Business Rule Did Not Work Properly When Import Map Header Detail Did Not Specify Custom Import Class	Previously, when the Custom Import Class field on an Import Map Header Detail record was not entered, this caused the RenameWorkspaceWithClientNumber business rule to not work properly. This happened because the missing Custom Import Class prevented the business rule from accessing the organization data containing the organization name needed to translate the client number to a name value. Now, if a valid Custom Import Class is not available, the system will use the ProjectID to get the organization name.
59510	Resetting a Module Caused Page Format Issues	If you clicked the Clear button to clear default filters and then clicked Reset, the list was reformatted, pushing the list off the bottom of the page and resulting in users needing to scroll in order to access the Previous/Next navigation buttons at the end of a page. This issue has been resolved.
59751	Clicking the Calendar Resync Button No Longer Updated Events	Previously, when new events were added to or deleted from the ClientSpace calendar and ClientSpace users attempted to sync their calendars by clicking Resync, their calendars were not updated with the event changes. To resolve the issue, a program change was made to use HttpClient instead of WebClient to sync calendar events.
59795	Field Audit Trail Showed Incorrect User Information for Business Logic Updates	Previously, the system audit logs would indicate the logged in user had updated a field when it in fact had been updated by business logic. Now, the system will correctly associate the login ID with the action that triggered the business rule change on a different form.
59866	Corrected Exception Log Paging and Error Name Allowance	Previously, the exception log stored procedure did not handle paging correctly and any error name that exceeded 100 characters was cut off. Now, paging between multiple pages of exceptions works and the error name allowance has been increased to 500 characters.
60094	Manage Imports Module Stopped Working for Non-Global Admins after R122 Update	The new method added for import file chunking in ClientSpace release 122 did not respect the existing SYS_ImportManager security entity that allows Non-Global Administrators to upload and run imports in the Import Management module without having Global Admin rights. This caused an error to display when importing a large import file that triggered the import file chunking method. This issue has been corrected by a patch release in R122 and also corrected at the pre-release stage in R123.