NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Release 57 ( PEO )

Owned by Tony Hayes
Last updated: Jul 20, 2017 by Tim BorntregerVersion comment
3 min read

Sprint Began: 6/26/2017     Sprint Ended: 7/17/2017


The following items have been completed in this release:


Ben Recon Employee SSN Logic Change -  ENHANCEMENT

The Ben Recon MBR Import process has been enhanced to lookup associated employee and workspace records based on Employee SSN and ClientNumber.


Liability Factor Logic - ENHANCEMENT

In High Deductible policies the funding rate is usually determined by starting with a flat percentage of Manual Rate. This is known as a High Deductible Liability Factor. This factor would be used in lieu of Increased Limits, Experience Modifier, and Scheduled Credit that are used to develop the Standard Premium. However, the Standard Premium is still is needed since it is used as the basis for other assessments which are then added to the High Deductible Liability Premium. High Deductible Liability Factor has been added on the Workers' Comp Policy. This change only affects the cost side of the equation.

A new Yes/No field called "High Deductible Policy" has been added in the existing cost factors fieldset. If "Use Cost Factors to Calculate Funding Rate" is set to "Yes", then this new field will be enabled.

A new percentage field (4 decimals) called "High Deductible Liability Factor (%)" has also been added. This field is enabled if the "High Deductible Policy" field is set to "Yes".

These new fields are cloned when a policy is renewed/cloned.

The funding rate calculation logic has been adjusted to use the new High Deductible factor. This change affects the cost side of the equation only, thus affecting the pricing console profit calculation whether it be a Master or MCP policy.


New I-9 Form - ENHANCEMENT

The Form I-9 has been added as a pdf report to the Employee Dataform in ClientSpace PEO. 

This form is produced with a barcode at the top which can be used to upload the form to the I-9 document in PEO. 

The associated employee name will also display in the lower right corner of the document, to aid in insuring the appropriate employee information is used to complete the form. 

If the employee does not have an associated I-9 form the document will be produced without a barcode or employee name.


Client Master-No state in the top left hand box populating (NEXT)

Resolved an issue where the Client Info widget on the Client Master Data Form displayed City and Zipcode with no State.  The widget now appropriately displays City, State and Zipcode on the client master widget, if present on the associated organization.


Prism API upgraded to v 1.9

The PEO PrismHR code has been upgraded to utilize PrismHR API v1.9.


Salesforce Export Contact

The SF AccountId associated with the Contact's Organization is now set on the Contact before being exported.  No mapping changes are required.


PEO Case search proc throwing a NULL insert error

The case search SQL has been modified to resolve NULL insert errors that would sometimes be logged.


Remove calls to "private" NEXT grid methods

Resolved an issue where some code in the NEXT Grid widget was unavailable in the application because it was classified as "Private".


Case type search filter missing case types

Resolved an issue where when trying to filter case type search for a specific case type the case type is not available.


Moving Claims Functionality Broken Due to Location Foreign Key Relationship Enhancement

Resolved an issue where the foreign key relationship between the Comp Claim and the Employee / Employment dataforms was causing the "Move Claim" function of the WC Claims dashboard to throw a "Foreign Key Constraint" exception. 


Workspace Landing Page - GetWSInfo - ENHANCEMENT

The workspace landing page code has been optimized to help speed load times across all workspace landing page types.


SF API Field Types

Fixed an issue where empty data types would cause an error when exported to Salesforce.


Benefits Recon: Convert EDV errors

Resolved an issue in the Benefits Recon process where if an MBR which does not have an EDV Source List (when MBR is created manually), reprocessing the Convert EDV record may cause a SQL error.



NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm