Release 151 Notes

Updated Benefit Batch Billing Rules Export Merge Minimum Age Field

The Benefit Batch Billing Rules Export query (peo_merge_client_benefit_billing_rules_export) has been modified to update column "Q" with the Minimum Age (OBP.MinimumAge) if available. If no Minimum Age is available, 0 is inserted in the field.

Added Fieldset Expand/Collapse Functionality to Field Display Configuration

You can now configure dynamic field display Expand/Collapse functionality on fieldsets. The image below illustrates a "When this field is not empty, expand this fieldset" scenario.

See Configuring Dynamic Field Display.

Added Ability to Specify #Empty and #NotEmpty in "equals this value" Field Display Configuration

You can now configure a field to display on a dataform (System Admin > Advanced > Dataform Admin) when another field is empty or is not empty by using the new #Empty or #NotEmpty field display rule in the equals this value field. The image below illustrates a "When this field equals this value (#NotEmpty, in this case), this item will display" scenario.

See Configuring Dynamic Field Display.

Removed Log Field Overwrite and Append Capability on _ModifyFieldValue Business Rule Method Configuration

Previously, you could use the Overwrite and Append Modification values when configuring the _ModifyFieldValue business rule method (System Admin > Advanced > Manage Business Rules) to replace log field information or append information to the end of a log field. Now, you can only use the Prepend Modification value to add a log file entry to the beginning of a log field. If you enter an Overwrite or Append Modification value, the following error message displays upon clicking Save or Apply on the business rule record: "The Modification value for log fields may only be Prepend and cannot be Overwrite or Append."

You must correct the Modification value to proceed with saving the rule.

See Business Rule Methods.

Updated Lookup Details Filter to Disallow Special Characters Except Comma

Previously, you could type any special character, such as an ampersand (&), into the Filter field of a Lookup Detail record and save it (System Admin > Lookups). The special characters caused the affected dataforms not to load. Now, the Filter field will not accept special characters (except for commas).

Note: Commas are used to create a comma-separated list of multiple filter values in the Filter field. This change respects this pre-existing functionality.

SeeConfiguring lookups.

Modified _ModifyFieldValue Business Rule Method Validation

Previously, when configuring a _ModifyFieldValue business rule method (System Admin > Advanced > Manage Business Rules) a soft error message always displayed when configuring a business rule using any Modification value, including Overwrite if you did not specify a Separator . The Separator is only applicable when making an Append or Prepend modification to a long text field (such as Editor, Log or Text Area field datatypes) where you want an addition to appear on a separate line, but is not required. The validation is now is follows:

• If the Modification value is set to Append or Prepend and no Separator is specified, the following soft error message displays upon clicking Save or Apply on the business rule record: "The Separator is not filled out."

  However, you can click Save Anyway to continue.

• If the Modification value is set to Overwrite, no error message displays.

See Business Rule Methods.

Added ESL Management to Action Center for Organizations, Contacts and Tasks

Previously, you could manage External Source Linking (ESL) records (used by the Salesforce API to link records in ClientSpace and Salesforce) from Action Center > More options > External Source Linking of dataforms but not from relevant CRM forms such as Organization Detail, Contact Detail, and Task Detail records. Now, you can manage ESL records from the Action Center > More options > External Source Linking of Organization Detail, Contact Detail, and Task Detail records.

The ClientSpace TableName and ClientSpaceID fields auto-fill and cannot be edited. Therefore, the fields are always inaccessible. If you are a Global Administrator or Developer User, you can edit the following fields:

• API Configuration

• External Object

• External Object ID

• Export Status

• Integration Log

Note: You can only append to the Integration Log. You cannot modify or delete prior entries.

See External Source Linking.

Added Ability to Enter International Phone Numbers on CRM Dataforms

Previously in ClientSpace Release 150, we added a setting to Dataform Administration to allow international phone number entry on Phone datatype fields (see Case# 70867). This did not include CRM forms (i.e., Contact and Organizations) as these forms are treated differently in the system. Now, an Allow International Phone Numbers on CRM forms checkbox has been added to App Settings (System Admin > Advanced > App Settings). When checked, the system does not apply the default input mask (### - ### - ####) that is normally applied on Save or Apply.

The affected fields are:

Organization

• Phone

• Fax

• Secondary Phone

Contact

• Business Phone

• Mobile

• Fax

• Pager

Note: 

• Please be aware that when Allow International Phone Numbers is enabled, the phone number field functions as a free text entry field with no validation of the data.

• Only Developer Users can access App Settings. If you need this feature, please contact your ClientSpace representative or log an extranet ticket.

SeeConfiguring Your Dataform Datatypes.

Added "Completed By" to Task Manager "More" Search

A Completed By filter option has been added to the Task Manager dashboard More search option on the Advanced Filters section. This allows you to filter tasks completed by a specific user.

Previously, if you did not provide the entire document (i.e., all fields) for the ClientSpace API Dataform PUT /api/dataform/v1.0/{tableName}/{id} method, a 200 error code was returned instead of a 400 error code. Now, a 400 error code is returned. This correction was made to versions 1, 2, and 3 of the ClientSpace API Dataform PUT /api/dataform/v1.0/{tableName}/{id} method.

Previously, if you collapsed the "Benefits Documents" fieldset on the Collateral dataform (Client Master > Go to Workspace > Action Center under Links) and later expanded the fieldset again, all of the file upload fields were cut off so that none of field values were visible. Clicking an area where the rest of one of the missing fields should have been displayed resulted in all of the fields to displaying properly again. This issue has been corrected.

Previously, if a multi-lookup field value was imported with bad data, the page load functionality could not handle the bad data on the affected page and the page would not load. Page load functionality has now been updated to handle data in a bad state that is stored in a multi-lookup field.

Previously, when the PrismHR Import OSHA Location Data CLIENT was updated to support multi-tenant environments, it did not handle multi-tenant environments properly as all locations set to sync locations were not being updated. Now, when multi-tenancy enabled and the client has multi-tenant locations set to sync locations, those locations will be included for the scheduled process to update.

Previously, when you configured a field display rule to Clear Field On Disable/Hide and the state of the field matched the defined conditions, if the target field specified in this item was a decimal datatype, the field was appropriately hidden or disabled according to your selection in the will field, but it was not cleared. This issue has been corrected.