NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here

Release 83 Notes

The following items have been completed in this release.

Sprint Began: 8/1/2019     Sprint Ended: 8/31/2019


ll ClientSpace release notes are now delivered in a single document. To learn about product features that you may not recognize, contact your customer success manager.

ClientSpace R83 release schedule

The following chart describes the typical release schedule for our monthly upgrades. The schedule is subject to change and will be updated as required. To determine your group number or to ask questions, please contact Professional Services via the Extranet.

Upgrade groupsDate of upgradeFor this sprint, tentatively occurs on
Group 1Second Tuesday of the monthSeptember 10, 2019
Group 2Third Tuesday of the monthSeptember 17, 2019
Group 3Fourth Tuesday of the monthSeptember 24, 2019

Product Enhancements

The following symbols apply to product enhancements:

 Denotes a change in functionality. So, when we move the cheese and change the way something works, you will know about it.

 ClientSpace Plus (ClientSpace with additional modules)

 ClientSpace Advanced Admin (ClientSpace advanced administration)

Filter Benefit Plans by Plan Category on Offered Plans (29496) ENHANCEMENT 

The Offered Benefits Plan has been enhanced. Selecting a category of benefit plan will now filter the Benefit Plan list to just the plans that are in the associated category. This can be a time saver when the system is configured with a wide range of benefit plan offerings.

Associate Offered Plans link (31553) ENHANCEMENT 

We have enhanced the Benefits Batch functionality. Previously, on Benefits Batch, if you clicked the Associate Offered Plans link, the system would only associate the offered plans with a status of Selected. Now the update associates all plans in the workspace with a status of New or Selected.

Benefit Plan premium/rate update (33564) ENHANCEMENT 

The Benefit Plan and Benefit Plan Tier dataforms have been enhanced with new business rules. 

  • SE_WarnOnCostChange: If any of the costs have changed, the system warns the user that this may affect offered rates. 
  • UpdateOfferedBenefitsPlans: Performs the update to the offered plan rates based on changes to the plan or tier costs. Only triggered if the Override Client Premiums option on the Offered Plan is cleared.

These enhancements ensure that changes to rates are carried through to the Offered plan automatically, ensuring that the offer aligns with the current plan rates and tiers.

Add Benefit Plan Tier ImportID logic (35337) ENHANCEMENT 

The Benefits system has been enhanced to update the ImportID of the Benefits Plan tier in sync with the associated Benefits Health Carrier/Plan. The Plan Tier ImportID is formatted as <BenefitPlanImportID>-<PlanTier Title>, so if a benefit plan has an ImportID of AETHMO13-20190801 and the plan tier record has a title of HP1, the ImportID for this plan tier would be AETHMO13-20190801-HP1. In instances where the Benefit Plan ImportID changes or is cleared, the associated Plan Tier ImportIDs also change to match, keeping them in sync.

Related fields on Dataform Field Properties (37562) ENHANCEMENT 

Certain datatypes allow for advanced configuration, allowing you to specify what displays in the field. The most common datatypes that support such custom configurations have fields that allow the global administrator to complete these configurations in a straight forward manner. Some configurable datatypes do not have an easy to use interface. These may be configured by a knowledgeable professional using the Field properties field (in the case of our newer cross-browser application) or through the Related Data field for the classic application. The fields used for this configuration have been exposed in the Dataform Fields admin console. PrismHR recommends consulting with professional services to configure these special properties unless you have a solid understanding of these field configurations. Mis-configuration could cause unexpected behavior of the dataform/field.

For help configuring specific datatypes, contact professional services.

Convert WCLagTime incident clone key to NEXT (37795) ENHANCEMENT 

The Workflow Channel system has been enhanced to trigger workflows in the same way as the WCLagTime Incident Clone Key from the classic Template Tasks. In the Admin Workspace, on the PEO Configuration page, the Carrier Lag Threshold field controls the triggering. On save of the Comp Claim dataform, the Check Lag Time rule checks the difference between the Injury Date and Carrier Report Date. If the value returned exceeds the lag time threshold, a hidden Lag Time Exceeded field (Yes/No lookup) on the Comp Claim form is set, which can be used to trigger workflows.

Organization security (38041) ENHANCEMENT

Org Category security has been enhanced to dynamically update organization security with changes to the associated Organization category. Changes made under System Admin > Security > Org Categories automatically propagate to the associated organizations with a related category. Changes include category, role, and access changes. If an Org Category is deleted, the security is removed from all associated organizations. For more information about security, review Organization and Workspace Security Configuration in our knowledge base.

Employment dataform (38155) and Server Data Proc (38156) ENHANCEMENT

Employment dataform: The employment dataform has been enhanced to store more information. A new fieldset, Additional Information, has been added on the gen_EmployeeEmploymentInformation. These new fields are marked as Triggerable by default. The read-only attribute is controlled from the Source on the Employee form as are most of the employment form fields.

The following fields have been added to the Additional Information fieldset:

  • Is FLSA exempt?: Yes/No lookup
  • Is FICA exempt?: Yes/No lookup

The following fields are coming soon. They are not yet functional as of R83.

  • Enrolled Benefits: Multi Lookup (Employment Benefit Types)
  • Has Retirement?: Yes/No lookup
  • Has Dependents?: Yes/No lookup
  • Has Garnishments?: Yes/No lookup

Employment server data proc: In addition, the Employee server data proc peo_server_data_employee used in workflow channel and email template configuration now includes the same employee dataform fields.

The following fields have been added to the Additional Information fieldset:

  • Is FLSA exempt?: Yes/No 
  • Is FICA exempt?: Yes/No

The following fields are coming soon. They are not yet functional as of R83.

  • Enrolled BenefitsComma space-delimited list of decode values stored in the multi-lookup field
  • Has Retirement?: Yes/No 
  • Has Dependents?: Yes/No 
  • Has Garnishments?: Yes/No

All of the fields can be used in field replacement to return the value stored in the related dataform field. The Yes/No fields can be used to configure trigger conditions by typing Yes or No in the trigger value field. Enrolled Benefits can be used for triggering by using a trigger operator of Contains and a decoded value such as Health, Dental, Vision, etc.

HRPAPI mapping: Employment benefits (38244) ENHANCEMENT

The HRPAPI has been enhanced to include new employment information. Two new fields have been added to the Employment form in the application. The Employment import configurations have been updated to include the following:

  • Is FLSA Exempt: Imports this flag from the Employee > Name > FLSA Exempt field in PrismHR.
  • Is FICA Exempt: Imports this flag from the Employee > Tax FICA Exempt field in PrismHR.

Client Service Case Due Date (38448) ENHANCEMENT

Client Service Case has been enhanced. 

The SetDueDateFromCaseTypeOffset business rule now adheres to the Save Action value in the rule configuration so it can run on Insert, Update, or Both instead of being hard-coded to Inserts only. This enhancement allows you to configure the system so that the Due Date resets dynamically if the case type changes. 

For example, a client initially logs a case on January 1 and selects a case type with a due date offset of 2 weeks. The case due date is set by the system to January 15 based on the offset. Two days later they realize the issue is worse than they initially thought, so they change the case type to one that has a default due date offset of 3 days. 

Before this enhancement, the Rule that sets the due date on the case would be ignored when updating an existing case. So the due date would still be January 15.

The enhancement allows you to configure the rule so that when the case type changes, the due date would be reset based on the new case type parameters and the update date from the case. So the case updated on January 3 with a new case type due date offset of 3 days, would have a due date of January 6.

Role Security (38454) ENHANCEMENT 

Role security has been enhanced with two new security entities that enable the system administrator to secure the Active option on Orgs, Contacts, and Tasks.

  • CRM_IsActive secures the Active option on Organizations and Contacts
  • Incident_IsActive secures the Active option on Tasks. This does not affect mass updates through the task manager. Users with rights to perform mass updates can still mark a task as Inactive by completing and archiving the task.

You need View rights on your role to see the Active option.

For more information regarding Role security, review the knowledge base article Administering Role Security.

Workflow Channels: Allow trigger conditions across single dataforms (38614) ENHANCEMENT 

The workflow channels system has been enhanced, making all active, triggerable, single forms in the application available in the Source field when configuring Workflow Channel triggering conditions (Step 4 when configuring workflows). For more information regarding Workflow channel configuration, review the knowledge base article Configuring Workflow Channels.

Email Templates: Allow trigger conditions across single dataforms (38712) ENHANCEMENT 

The Email Template system has been enhanced to allow triggerable fields from any single dataform marked as triggerable, as an additional triggering condition. Previously, only the Triggering Table (set on Step 1 of the template) and any dataform related to the triggering table through tabs, were available as additional conditions.

Workflow channel unique index (38828) ENHANCEMENT 

The Workflow Channel Name validation has been optimized, moving the database server-side validation to client-side code.

Payroll Batch Type lookup (38905) ENHANCEMENT 

Updated Payroll Batch Type lookup. The Decode for R is now set to Regular Scheduled from the previous value of Scheduled to match the values in PrismHR.

Refactor view: peo_vwPricingInfo_All (38987) ENHANCEMENT 

The view peo_vwPricingInfo_All has been refactored to optimize performance, allowing it to run more efficiently.

Refactor view: peo_vwClaimDetail (38988) ENHANCEMENT 

The view peo_vwClaimDetail has been refactored to optimize performance, allowing it to run more efficiently.

Claim Financials Legal fields (39026) ENHANCEMENT 

Three new optional fields have been added to the claim financials form:

  • Paid Legal
  • Reserved Legal
  • Incurred Legal

These fields are in a hidden fieldset on the dataform. You can activate the fields by moving them into the appropriate Paid / Reserve / Incurred fieldset on the form. When you store claim related legal cost data in these fields, they affect the financial calculations in the following way:

  • Incurred Legal = Paid Legal + Reserved Legal
  • Paid Total = Paid Medical + Paid Indemnity + Paid Expense + Paid Legal
  • ReservedTotal = Reserved Medical + Reserved Indemnity + Reserved Expense + Reserved Legal
  • IncurredTotal = Incurred Medical + Incurred Indemnity + Incurred Expense + Incurred Legal

Current Pricing Batch record (39035) ENHANCEMENT  

Pricing has been enhanced to add a Current Batch feature with the following changes:

  • A new option named Current Pricing Batch is now in the Workflow History fieldset. It is read-only.
  • A new business rule Set Current Pricing Batch has been added and is configured to run on the Default and Import pipelines. 
    This business rule:
    • Clears the current batch flag on all pricing batches in the workspace,
    • Finds the current activated batch, or in the cases where batch activation has not occurred, selects the most recently created batch that is not a comparison batch,
    • And sets the Current Pricing Batch flag.
  • This development also includes a script to set the Current Batch on existing Pricing Batch records that meet the criteria.

Defensive code to force a reload of the cache (39139) ENHANCEMENT 

Defensive code has been added to ensure the datatype cache on the webserver is refreshed automatically in the case of a datatype mismatch, thus avoiding unexpected results.

System database tables (39289) ENHANCEMENT 

System database tables have been tuned for optimization by adding a new index.

Tabbed dataforms, Pipeline dependencies (39393) ENHANCEMENT 

Default pipeline configuration has been removed from dataform administration. 

License dashboard (39401) ENHANCEMENT 

The License dashboard has been enhanced, adding the ability to search all licenses by user. 


We have begun the process of converting the PrismHR API to a REST API from the current SOAP API format. The conversion allows the application to automatically take advantage of new API methods without having to update the base API code every time. This transition from one API format to another should be seamless from a user perspective.

Email add-in Primary Contact default on Sent emails (39516) ENHANCEMENT 

The Email Add-in has been enhanced. If the FROM address of the email is the same as the add-in users email address, the system will use the first TO address to determine the primary contact/organization. The system will also now use the sent date of the email to populate the Date Sent of the email activity so the user is not prompted with whether they should send the email on save. 

External Source linking, Import enhancement (39697) ENHANCEMENT 

Users can now be imported into the External Source Linking table using the IMPORT_externalsourcelinking_*.csv import map. The ClientSpaceID value will be tested against the Users table UserGUID field. If a match is found, the record is inserted into the linking table (non-matching ClientSpaceIDs cannot be inserted into this table).

CaseIssue SummaryResolution
14637Dropdown csValue issue

Resolved an issue that could occur in a drop-down field such as a lookup where, if the selected item does not exist in the list (maybe a lookup item was inactivated), the underlying value is not set on the dataform save. 

38213 Organization category security issue on PEO

Fixed a bug in Organization category security that occurred when the AssignedTo department matched the role being added because the org category security and the department of the AssignedTo had member access set to None. In that scenario, the entity was not added to the Organization. 

38552 Adding fields with { } in field label error

Resolved an issue where field labels containing the characters {} and [] would throw an exception on page load. These characters are now stripped from field labels on dataform field save.

38640Workspace not being properly decoded on Case Type Subscription

Fixed a bug in the Case Type Subscription dashboard where the My Clients option in the workspace selector was not being decoded properly after save and would display the value -2 instead. For more information about getting automatic notifications based on case type, review the article How Do Case Type Subscriptions Work? in our knowledge base.

38713Contacts API: Related Org field

Resolved an issue with the HRPAPI_contact import configuration that would cause contacts to be imported, but not associated with an organization.

39030Workflow Channel workflow action error

Resolved an issue that could occur when adding a lookup field using the NAIC lookup group to a workflow channel with the Add Untriggered functionality, which would result in duplicated fields on the workflow configuration page.  

39083User deletion issues

Fixed a bug when attempting to delete a user that was associated with a license would cause a foreign key constraint error and not allow the user to be deleted.

39159 Report admin Save and New button

Resolved an issue where using Save and New in report admin would not work. Save and New will now save the existing record and open a new Add dialog as expected.

39303Active reports date fields on filter pages

Resolved an issue on the filter page of an active report where date field parameters were truncated, which caused unexpected results.

39427 Custom Link conditions, CRM forms

Fixed an issue during custom link configuration if the TableCode or field label data is missing for the table from which a link is triggered, neither the form nor header proc fields with missing data will be located when attempting to configure link display conditions using those fields.

39449Reports not auto-sent

Fixed a bug that caused some scheduled BI reports not to be sent.

39468Task ID link in task email does not have full websiteDefensive code has been added to ensure that the link embedded in a Task notification email does not become malformed, causing unexpected results.
39515Tab dataform and field display issue

Resolved an issue where two forms in a tab relationship with field display would cause an exception if there were fields on the related forms with the same name and field display involved one of these fields.

39641Error editing a license

Optimized the license save process that minimizes the amount of data being passed back to the database on save. The optimization resolves issues that some larger clients may experience when adding or editing licensing in the system.

39688Custom header link conditions not evaluating correctly

Resolved an issue where bit value (checkbox) flags configured as trigger conditions for link display were not being properly evaluated, causing link display to fail.

39724Contact not defaulting in prodResolved an issue where the Primary Contact field was not defaulting properly on add of the first contact to an organization.
39834Exception log: Adding untriggerable form in Email Templates

Resolved an issue when choosing an Untriggered form as a trigger in a new Email Template. An exception occurred when the modal dialogue opened, allowing the user to choose an untriggerable form.

39857kandu slackbot not workingResolved an issue with the /kandu slackbot where the system would not return results when using the /kandu task command.
40020Email Template Conditions: Added untriggered fieldChanges to Email Templates in R83 caused the Add Untriggered field list functionality to improperly include dataform fieldsets and to improperly present certain datatype trigger value fields as a blank integer field. This has been corrected.
40053Lookup and User Type ahead decode for Fields added through Add Untriggered

Resolved an issue with lookup, parent form, and user datatypes in Email Templates. When adding these types of fields through the Add Untriggered functionality of email templates, the value selector would not correctly decode the field, instead presenting an empty text box that expected an integer as input. These types of fields will now correctly present in the value selector as if they were on a dataform. For more information about email template configuration, review Administering Email Templates in our knowledge base.

NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here