Release 104 Notes

R104 Sprint: 5/1/2021 to 5/31/2021. 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.

Click to view the R104 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 Professional Services in the Extranet.

Sprint 5/1/2020 to 5/31/2020
Upgrade groups	Date of upgrade	Tentatively occurs on
Group 1	First Tuesday of the month	June 10, 2021
Group 2	Second Tuesday of the month	June 17, 2021
Group 3	Third Tuesday of the month	June 24, 2021

Enhancement

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

Change in Functionality

Case	Enhancement
50082	Importing multi-select lookup data This case modifies the import decode logic to handle multiple lookup ImportIDs in the match process. Importing values into a multi-select field will now correctly set all multiple values provided in the import row. See Configuring the Import Map Detail.
50505	Outbound Email Size Previously when sending an email from ClientSpace with attachments over 11 MB in file size, the Email Admin indicated that the message sent with the attachment. However, the email recipients never received the email message. When the file size for email attachments was less than 11 MB, the Email Admin indicated that the message sent with the attachments and the recipients received the email messages. Now, the system calculates the total file size of email attachments before sending the email message. If attachments are within the maximum file size limits, then: The system sends the email message. The Email Admin indicates the message as SENT and the Failed column is set to No. If attachments exceed the maximum file size limits, then: The system does NOT send the email message. The Email Admin indicates the message as UNSENT and the Failed column is set to Yes.

Case

Enhancement

50082

Importing multi-select lookup data

This case modifies the import decode logic to handle multiple lookup ImportIDs in the match process. Importing values into a multi-select field will now correctly set all multiple values provided in the import row.

See Configuring the Import Map Detail.

50505

Outbound Email Size

Previously when sending an email from ClientSpace with attachments over 11 MB in file size, the Email Admin indicated that the message sent with the attachment. However, the email recipients never received the email message. When the file size for email attachments was less than 11 MB, the Email Admin indicated that the message sent with the attachments and the recipients received the email messages.

Now, the system calculates the total file size of email attachments before sending the email message.

If attachments are within the maximum file size limits, then:

The system sends the email message.
The Email Admin indicates the message as SENT and the Failed column is set to No.

If attachments exceed the maximum file size limits, then:

The system does NOT send the email message.
The Email Admin indicates the message as UNSENT and the Failed column is set to Yes.

Advanced Administration

Case	Enhancement
50037	Import Queue records stuck in In-Progress status, PrismHR ONGOING only This case enhances the PrismHR Ongoing Scheduled Process. The system now checks for import queue records stuck in the In Progress status due to an interruption in the process (for example, the process was aborted). The system will reset the status to Pending, which allows the process to retrieve current data via the PrismHR API. See The Scheduled Process.
50655	Adding items from Dataform Properties With this case, the system now defaults new business rules to the current dataform when adding new business rules by jumping to business rules from the dataform properties. For example, while viewing the dataform properties for dataform Test123, a system admin user can select the Business Rules action item from the Action Center. The system displays the Custom Logic Rules dashboard for rules associated with dataform Test123. When the system admin user adds a new business rule from the Custom Logic Rules dashboard, the new business rule defaults the Table Name field to Test123. Note: If necessary, a system admin user can select a different dataform from the Table Name field drop-down.
50705	PrismHR API Payroll Batch, no billing vouchers Previously, if no billing vouchers were found for a Payroll Batch (from an Event), the payroll batch would get stuck in 'Pending' status. Now, if no billing vouchers are found for a Payroll Batch, the system marks the record as complete (as there isn't any data to process) and creates a log entry that indicates that no vouchers were found. For example: No billing vouchers found for client ID "<api:clientId>" and batch ID "<api:batchId>." See: How Payroll Batch Data Is Updated.

Case

Enhancement

50037

Import Queue records stuck in In-Progress status, PrismHR ONGOING only

This case enhances the PrismHR Ongoing Scheduled Process. The system now checks for import queue records stuck in the In Progress status due to an interruption in the process (for example, the process was aborted). The system will reset the status to Pending, which allows the process to retrieve current data via the PrismHR API.

See The Scheduled Process.

50655

Adding items from Dataform Properties

With this case, the system now defaults new business rules to the current dataform when adding new business rules by jumping to business rules from the dataform properties. For example, while viewing the dataform properties for dataform Test123, a system admin user can select the Business Rules action item from the Action Center. The system displays the Custom Logic Rules dashboard for rules associated with dataform Test123. When the system admin user adds a new business rule from the Custom Logic Rules dashboard, the new business rule defaults the Table Name field to Test123.

Note: If necessary, a system admin user can select a different dataform from the Table Name field drop-down.

50705

PrismHR API Payroll Batch, no billing vouchers

Previously, if no billing vouchers were found for a Payroll Batch (from an Event), the payroll batch would get stuck in 'Pending' status.

Now, if no billing vouchers are found for a Payroll Batch, the system marks the record as complete (as there isn't any data to process) and creates a log entry that indicates that no vouchers were found. For example:

No billing vouchers found for client ID "<api:clientId>" and batch ID "<api:batchId>."

See: How Payroll Batch Data Is Updated.

General Enhancements

Case	Enhancement
50018	Reset Release Notes to New This case adds a new Release Notes link to the Help Center page. With this addition, a user can now quickly access the latest release notes for ClientSpace. This link will be refreshed with each sprint upgrade to indicate when a new version of release notes is available.
50111	Core Method for Auditing Deletes This case adds a new core method that the system uses to audit items deleted in the system. This method will audit the following: What item in the system that a user deleted Which user deleted the item When the user deleted the item
50112 and 51304	Where to Use New Core Method for Auditing Deletes These cases implement the new core method for auditing deletes, so that the system audits deletions from the following: areas of the system: Activities Attachment/Files Workspaces Tasks Lookups/Lookup Groups Workflow Channel/Item Email Templates ProjectTypes Dataform Fields (PAX records) Roles/ Security Entities Users Departments EPLI Claims UI Claims WC Claims
50654	Set field from Related form With this case, a system administrator user can now use the new _SetFieldFromRelatedForm method with a business rule so that the system can populate a dataform field with information from another related dataform. See Business Rule Methods.

Technical Enhancements

Case	Enhancement
49334	Imports, Email validation This case creates an Email datatype that the system uses to reject a bad email address during an import. The system uses the Default Value options to determine how to proceed when the system encounters a bad email address during import. See Configuring the Import Map Detail.
50383	Encrypt Connection Strings This case applies Advanced Encryption Standard (AES) encryption to the web.config connection strings in ClientSpace.
50653	TLS Part Deux This case evaluated all internal tools that use web services to verify functionality with Transport Layer Security (TLS).
50754	Remove RelatedData Column from PAX Table This case resolves converting related data functionality in ClientSpace and removes the RelatedData column from the PAX table.

Fixes

Case	Issue summary	Resolution
50588	Pricing Console Preload Bug	Previously, when uploading pricing codes for a state that already existed in the pricing batch, the system added a duplicate pricing state instead of adding the new code to the existing pricing state. At the end of the process, when Merge All was selected the merge appeared to succeed, but a js error was thrown. Now, when uploading pricing for a state that already exists in the pricing batch, the system adds the new code to the existing pricing state instead of adding a duplicate. See Creating Pricing.
50630	cs_datatype_s_org_contacts appears in Element Type instead of display name	Previously when a user added a new field to a dataform and the user selected the drop-down for the Element Type field, one of the element types did not display properly. The code name cs_datatype_s_org_contacts displayed in the list instead of the display name Policy Org Contact for the element type. Now the system properly displays the display name for this element type.
50637	OBP-SE_MultiplePlanTiers Messaging	This case fixes an issue with displaying the wrong rate group in an error message. Previously, when an error was found on save for a business rule with the SE_MultiplePlanTeirs method, the system would display a message with incorrect record information. Now, the system displays the correct rate group when a user attempts to save a change to the Rate Group for a business rule with the SE_MultiplePlanTeirs method.
50720	Dataform filters on File Category lookup not consistent EDIT / ADD	Previously, when adding attachments to a dataform, the File Category lookup respected the dataform filter option (displaying unfiltered lookup values and those with the gen_DataformName), but when editing existing attachments on a dataform the only File Category lookup options were those without a filter. Now, the system uses the correct filter when editing existing attachments on a dataform.
50721	WFC Item Notifications list error	Previously, when editing an existing WFC Item with one role on the Notification list, the system required a user to re-enter the role when proceeding from Step3 to Step4 of the WFC Item. This issue did not occur when more than one role existed on the notification. This case adds logic to correctly decode the existing value and not prompt the user to re-enter the role when a WFC Item uses only one role on the Notification list.
50797	Time Tracking records not moving with UI Claims, WC Claims, and Cases	This case resolves an issue with orphaned time tracking records when UI Claims, WC Claims, or a cases were moved to a different workspace. Previously, when claims, or cases were moved to a different workspace, the system did not move the associated time tracking records to the new workspace. The time tracking records were orphaned from the claims or cases. This left the records eligible for deletion when the system executed the scheduled process to clean up orphaned time tracking records. Now, when a UI Claim, WC Claim, or a case is moved to a different workspace, any items associated with the record (for example, tasks, attachments, subscribers, activities, and time tracking) are moved along with that record to the new workspace
50862	Lookup Typeahead Primary Trigger issue	Previously, when creating a new WFC Item and the Primary Trigger was set to a lookup typeahead with an equals operator, the system would generate an exception and display the following error when proceeding to Step 2: Sorry an error has occurred - Please contact your system administrator This case updates Step One of Workflow Channel Item creation to support Lookup Type-Aheads as a primary trigger source when Operator is Equals. Now, a user can continue to Step 2 without this error.
50872	ClientSpace API issues	This case resolves the following issues with the Log field: Previously, if you used the PATCH and PUT methods to insert data into the log field and that data contained an apostrophe, the system inserted apostrophes as "u0027"; now the system properly encodes apostrophes Previously the log field did not properly handle null values; Now, if the username is null or "", the the system inserts the word "null" Previously, the time stamp abbreviation appended to the end of a String reflected the server time zone EST setting; Now, the system uses the current date to determine the appropriate abbreviation to use (EDT or EST) based on the date
50956	Filter Pages Drop-Down Stored Procedure	Previously, when using a filter page with multiple custom drop-down fields that used a stored procedure as the data source, only the first drop-down procedure ran and its results displayed in all other drop-downs on the filter page. This case resolved an issue with a missing FieldID reference on subsequent drop-downs. Now, the filter page build properly supports multiple drop-downs with stored procedures.