R111 Sprint: 12/1/2021 to 12/31/2021. To learn about product features that you may not recognize, contact ClientSpace Professional Services.
A word from ClientSpace Professional Services
Happy New Year! Looking to kickstart your year and crush your 2022 goals? Enrollment for our ClientSpace Service Plans is now OPEN! Contact your ClientSpace Professional Services Team today! Learn More.
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 12/1/2021 to 12/31/2021 |
||
|---|---|---|
|
Upgrade groups |
Date of upgrade |
Tentatively occurs on |
| Group 1 | First Thursday of the month | January 11, 2022 |
| Group 2 | Second Tuesday of the month | January 18, 2022 |
| Group 3 | Third Tuesday of the month | January 25, 2022 |
Enhancement
Enhancement groups are Change in Functionality, ClientSpace Premium (ClientSpace with additional modules), Advanced Administration, and General.
Change in Functionality
|
Case |
Enhancement |
|---|---|
| 53376 |
Error Sending Email - Syntax error in parameters or arguments. The server response was: 5.5.4 Invalid Address This case adds validation for the email address on send. Previously, if an email address lacked the proper formatting (for example, an email address contained a backquote/backtick: emailaddress@gmail.com`), the system indicated a syntax error. Now, the system evaluates the email address at the time of the email send (for example, addressing an ad hoc email on an email template). If the email address is invalid, the system strips the invalid recipient from the resulting email. The system then sends the email message to any other email addresses that include valid formatting. The system logs an informational exception to indicate the email address was invalid. |
ClientSpace Premium
|
Case |
Enhancement |
|---|---|
| 49824 |
Export Fields from Multiforms to Salesforce With this case you can use a custom stored procedure to export field data from a multiform (for example, the client service case or pricing batch) to a Salesforce field. If you want to use a custom stored procedure with import / export mapping, contact ClientSpace Professional Services about configuring the Salesforce API csworkspacedataproc additional parameter with a custom stored procedure. See Import/ Export mapping and configure the Import Map Detail for fields from multiforms. |
| 51297, 54130, & 54168 |
"Current Batch" Merge Stored Procedure Change This case updates the following stored procedures:
A custom function was added to use when configuring these merges on the pricing batch - pricingBatch.runPricingBatchMerge. When running a merge configured (select Display Action of Custom Function) with one of these stored procedures from a custom link on a batch, the system returns the Comp Code numbers associated with that batch. When a user runs any of these merges from a custom link on any other dataform or from the workspace landing page (by configuring a link with Run Report), the system returns the Comp Code numbers associated with the batch that is marked as "Current Record". Note: If you have any questions or need assistance configuring, please contact the ClientSpace Professional Services Team. |
| 53234 |
Pricing Console Pre-load Caching Issue This case updates quick create pricing to resolve a data caching issue. Previously, if a user pre-loaded a list of state/code records (CSV file) during quick create pricing and canceled that pre-load, then pre-loaded a different file, the system would include properties of the first file in the States and Codes Pre-load Worksheet. Now, the system clears the cached information from a canceled pre-load before pre-loading another file. |
| 53527 |
Display all Active Locations When Maintaining a Pricing code This case updates the pricing code location and what locations are available for selection. This change allows the system to display all active workspace pricing code locations (including locations without a location code) when selecting a pricing code location during quick create pricing. See Creating Pricing. |
Advanced Administration
|
Case |
Enhancement |
|---|---|
| 53566 |
Multi-Tenant PrismHR API feeds In this case, a single ClientSpace installation can now accept data feeds from multiple PrismHR databases using the same client number ranges. The feature allows ClientSpace to differentiate client data between different PrismHR databases and import the data to the appropriate workspaces where clients from different PrismHR databases have the same client number. Note: You must contact ClientSpace Professional Services to implement this feature. 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. When Multi-Tenancy is not enabled (single-tenant mode), ClientSpace uses the PrismHR ClientNumber as the ImportID on the client master. When Multi-Tenancy is enabled, ClientSpace uses a combination of the PEOID and the ClientNumber values as the Import ID on the client master. The Import ID follows the format PEOID::ClientNumber (for example, PEOSolutions::165 signifies the PrismHR database installation for PEO Solutions and client number 165 from that database). ClientSpace uses this ImportID format to ensure that the system imports client data to the correct workspace when importing the data from multiple PrismHR databases. |
General Enhancements
|
Case |
Enhancement |
|---|---|
| 52205 |
ClientMaster.ActivationDate mapping This case updates the Activation Date mapping so that the system reflects the appropriate activation date in ClientSpace. Previously, the mapping path for CM_ActivationDate was PrismHR.contractDate for the company initial import map (HRPAPI_initial_company*.csv) and the company ongoing import map (HRPAPI_company_ongoing*.csv). The import was overriding the correct Activation Date with the incorrect Prism Contract Date. This case updates the mapping and adds the Set Activation Date on Import business rule. Now, the mapping path for CM_ActivationDate is Company/statusDate for both import maps. The system evaluates the Set Activation Date on Import business rule during import. If the Activation Date is populated, and the status equals Client, the system accepts the imported value. If the Status does not equal Client (for example, Terminated) the system reverts to the previous value. |
| 52619 |
Discussion Messages Not Moving When A Case Is Moved to Another Workspace In this case, if a user moves a client service case with a Discussion Thread from one workspace to another workspace, the system moves the existing discussion messages, open thread, and recipients to the new workspace. See Adding case discussions and Moving cases. |
Technical Enhancements
|
Case |
Enhancement |
|---|---|
| 53143 |
Optimize the speed of the system when the Delete Marked Task scheduled process runs This case updates the nw_incident_d_marked_task and nw_filemanagement_d_delete_by_entityguid procedures to optimize the system for speed when the Delete Marked Task scheduled process runs. |
| 53377 |
Exception occurring with Task Escalation Scheduled Process Previously, when running the Task Escalation scheduled process, an exception would occasionally occur. This case adds an index to the task escalation procedure to resolve this possible issue. |
Fixes
|
Case |
Issue summary |
Resolution |
|---|---|---|
| 53326 |
Sort all user lists alphabetically on the Security Role Users, Module Users, and the Ad Hoc Profile Users dashboards |
Previously when searching for users on the Security Role Users, Module Users, and the Ad Hoc Profile Users, dashboards and sorting the results by the Name column, the system did not always sort the values in the expected order (alphabetical by last name, then alphabetically by the first name). Now, when sorting by the Name column, the system sorts alphabetically by the last name then alphabetically by the first name. |
| 53491 |
The system does not load the Appointment form when selecting the Save and Create Appointment workflow link |
Previously, when a user selected the Save and Create Appointment for an activity, the system did not open the Appointment form so the user could create an appointment. Now, the system directs the user to the Appointment form so the user can create the appointment. |
| 53492 |
Resolve error caused by selecting a Fieldset for field comparison in a Field Display Rule |
Previously, when a user added or edited a field display rule with the Field Source drop-down set to This Table, a user could select a fieldset in the When this field drop-down as the field for field comparison. An error occurred when the user attempted to save the display rule for this configuration. This case removes fieldsets as available options in the When this field drop-down list. Now, a user cannot select a fieldset in the When this field drop-down as the field for field comparison and cause an error on save. |
| 52797 |
My Profile: Auto-Refresh the User Module Navigation Bar |
Previously, when a user changed the order of the modules that display in the Modules bar, the system did not update the module order in the module bar when the user selected Apply. Now, the system updates the modules in the Modules navigation bar to reflect the selected order when a user selects Apply. See User modules. |
| 53831 |
Error When a Non-developer User Adds Custom Links for the Client Service Case |
Previously, an error occurred when a non-developer user attempted to add a custom link to the Customer Service Case where a badge count procedure was configured. Now, a non-developer user can save a custom link for this scenario. |
| 53705 |
Field Display Issue When the "equals this value" Field Contains a Single Character |
Previously, if a multi-lookup field was used as the triggering value for a field display rule and the equals this value field contained a single character (for example, "K"), an error occurred on page load. This case updates field display rules to handle single character values in the equals this value field when the Trigger field type is multi-lookup. |
| 53754 |
Salesforce Import Clears ProjectName |
This case fixes an issue where in rare cases the Workspace name could be cleared when an update from SalesForce occurred and the system was using the 'updateworkspacename' parameter. This no longer occurs. |