Release 140 Notes

Set Effective and Expiration Dates on Benefits Batch and Associated Offered Benefit Plans

ClientSpace now sets the Effective Date and Expiration Date on:

• Renewed Benefits Batches and their associated Offered Benefit Plans.

• Expired Benefits Batches and their associated Offered Benefit Plans.

A new Expiration Date field was added to both the Benefits Batch and Offered Benefit Plan forms to support this enhancement.

You must enter the Effective Date on the Benefits Batch. Then, the Expiration Date is calculated and set on the Benefits Batch as one year from the Effective Date minus one day. The Effective Date from the Benefits Batch is set on any associated OBPs when you add the OBP to the Benefits Batch.

The Expiration Date from the Benefits Batch is set on any associated OBPs when you:

• Click the Renew link on a Benefits Batch to renew it along with any associated OBPs.

• Click the Activate link in the Action Center workflow to activate a Renewal Benefits Batch in Pending status and expire the Benefits Batch it was renewed from.

• Click the Expire link on a Benefits Batch in the Action Center workflow to expire it.

Note: 

• The Expiration Date field must be blank to be populated. Expiration Date fields with existing values are skipped.

• OBPs are updated regardless of how they were created. The OBP logic applies to:

  • Manually created OBPs that were created by clicking next to Offered Benefit Plans under Links in the Action Center.

  • OBPs created by clicking the Apply Plan Group link in the Action Center workflow.

See Renewing a Benefits Batch and Activating/ Expiring or Expiring a Benefits Batch.

Changed Money Data Type to Decimal Data Type on Benefits Forms Premium By Coverage Level Fields

Previously, on the Benefit Plan, Offered Benefits Plan and Rate Group Detail forms, the fields used to indicate the premium by coverage level were assigned a Money data type. The Money data type works for Health, Dental, and Vision plans but did not work for Life Insurance or other ancillary plans where the rates are computed as dollars per thousand of compensation (which could require more than two (2) decimal places to display a precise rate). Now, these fields have been converted to use the Decimal datatype which allows for a maximum of four (4) decimal places. By default, two decimal places are applied but you can customize the number of decimal places by editing the Mask field on the field properties.

The following fields were converted:

Benefits Plan

Offered Benefits Plan

Rate Group Detail

See Changing the Number of Decimal Places on a Dataform Field.

ClientSpace Bill Pending Comment Now Exports to Prism with Employee Last Name and Date of Injury

When the PrismHR Bill Records scheduled process runs, the export process now includes the Employee Last Name and Date of Injury along with any Bill Pending Comment entered on the ClientSpace Claim Deductible Bill. This information is prepended to the Comment on the PrismHR Bill Pending Details record as shown in the example below.

Note: The characters in the prepended Last Name and Date of Injury count toward the 40-character limit on the PrismHR Comment field.

See Using the Claim Deductible Bill Form.

Previously, the "No Plan Model" option had stopped displaying at the top of the Model Plan field lookup list by default on the Benefits Plan dataform. Now, when you click the down arrow in the Model Plan field, the "No Plan Model" option always displays at the top of the list.