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 64 ( PEO )

Owned by Tony Hayes
Last updated: Feb 01, 2018
3 min read

Sprint Began: 1/3/2018     Sprint Ended: 1/31/2018


The following items have been completed in this release:


Employer Contribution % allows invalid values to be generated 

Resolved an issue where in some cases the system would allow greater than 100% to be entered into contribution (percentage) fields during calculation.


Ee Document Search - ENHANCEMENT

Added the ability to search for an Employee and get a listing of all their file attachments using the Employee Document Search.

This search can be enabled at the workspace level from the WSL and Client Master,and has the ability to search at the workspace level and get a listing of all file attachments for all employees in that workspace.

The Employee Document Search provide an option to download the file or open the dataform that contains the file.


Case Discussion recipients - ENHANCEMENT

Case Discussion recipient selection has been enhanced:

The Client Contact from the case will be Auto selected as a recipient on a new discussion - if present and if they have an email
A Soft error (warning) will appear if there is no Contact or Employee recipient selected.


Auto Populate Hourly Wage on Comp Claim Claimant (Claimant Info) - ENHANCEMENT

A new "Hourly Rate" field has been added to the Comp Claim Claimant form. This field is automatically populated when a claim is added using the information from the Hourly Rate field on the associated Employment Information form.


OSHA Reports are not Working with Inactive Claims or Locations 

Resolved an issue which occurred when running an OSHA 300A or 300 where you need to report on archived/inactive WC Claims and inactive Locations.

The underlying query for the PEO 300A and 300 have been enhanced so inactive WC Claim and Locations will still be included in the output.


PrismHR API - Ongoing import handling data for a missing Client 

Resolved an issue where if Clients are created in PrismHR, but the client record does not exist in ClientSpace the system would produce queue records that would continuously fail due to the missing client workspace.

The system has been updated for all Ongoing API import events (except User and Company), if the associated Client Number cannot be located in ClientSpace, an import queue record will not be created and therefore will not be included in the import file.

An event will be logged in the API Log Scheduled Process History table


PRismHR API Automation - ENHANCEMENT

A "Reset Process" link has been added to the PrismHR Import Automation dataform in the Admin Workspace.

This Reset Form link will:
- delete all initial import queue records
- set all process statuses (on automation form) to "Pending"
- clear the log field (on automation form)
- set the scheduled processes as follows:
- PrismHR import users: inactive, next run date: current time
- PrismHR import queue initial clients: inactive, next run date: current time
- PrismHR import initials: inactive, next run date: current time
- PrismHR import auto: active, next run date: current time + 1 year


PrismHR Employee and Employment Ongoing Imports not working 

Corrected a bug in employee and employment api process causing incorrect Client Number's to be associated with Employees and causing those records to not import properly.


OSHA 300A optimization - ENHANCEMENT

The peo_rpt_OSHA300A stored procedure which creates the data for the OSHA 300A report has been optimized to make it run more efficiently, this is most evident when the report is run for all clients.



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