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

Owned by Tony Hayes
Last updated: Jun 08, 2018
4 min read

Sprint Began: 5/1/2018    Sprint Ended: 6/6/2018

The following items have been completed in this release:

We moved the cheese!

Mmmmmm - Cheese!  The cheese icon  denotes a change in functionality so when we move the cheese and change the way something works in the system you will know about it.  

Date Uploaded Search Parameter ENHANCEMENT

The employee document search dashboard has been enhanced to make it easier to use:

  • Added 'Date Uploaded' to More search criteria as a Date range filter
  • Added Description to Quick Search as a  'contains' filter


Workflow Channel Replace Field Options (Server Data Procs) ENHANCEMENT

The workflow channels functionality has been enhanced, including three new server data stored procedures to be used when merging Employee and Employment type data.  These stored procedures and the available merge fields are as follows:

Employment (peo_server_data_employment)

  • FirstName
  • LastName
  • MiddleInitial
  • EmployeeIdentifier
  • Address1
  • Address2
  • City
  • State
  • ZipCode
  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate

Employee (peo_server_data_employee)

  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate


PrismHR Event (peo_server_data_prismhrevent)

Schema = Employee:

  • FirstName
  • LastName
  • MiddleInitial
  • EmployeeIdentifier
  • Address1
  • Address2
  • City
  • State
  • ZipCode
  • EmploymentStatus
  • EmploymentType
  • HireDate
  • ClientNumber
  • ContractType
  • ContractEffectiveDate

Schema = Company:

  • ClientNumber
  • ContractType
  • ContractEffectiveDate


Joinder - Add the ability to push locations into Prism ENHANCEMENT

The PrismHR API has been enhanced, allowing the system to push location information into PrismHR.  If a ClientSpace location does not exist in PrismHR, that location will be created in the Prism System.  Two new business rules have been added to accomplish this:

Client Master - CM.ExportLocationsToHRP

  • Creates all locations in a workspace in PrismHR
  • Not on Add, and CM.ClientNumber must exist
  • Updates the Export Status and Export Log fields on each Location form, saves via Biz Logic ("HRP" pipeline)
  • Will NOT set the ImportID on the Location(s), Import ID setter proc should be used


Client Location - LOC.ExportLocationToHRP

  • Creates the current location in PrismHR
  • Not on Add, and CM.ClientNumber (on associated Client Master) must exist
  • Will NOT set the ImportID on the Location(s), Import ID setter proc should be used
  • In rule configurations
    • Provide the AppCode of the PrismHR API Configuration form to use
    • Must be active and meet the requirements of v1.12+

General Info

  • Locations must have Location Code provided or an error will occur
  • Client must exist in PrismHR
  • Exports the following fields:
    - Location.ClientNumber
    - Location.LocationCode
    - Location.LocationName
    - Location.GeoCode (PrismHR derived from ZipCode)
    - Location.AddressLine
    - Location.AddressLine2
    - Location.ZipCode
    - Location.ZipSuffix (not in ClientSpace, set to empty)
    - Location.State (sets PrismHR Location WorkCompState field)
    - If successful:
    • Export Status set to "Location Export Complete"
    • Export Log set to "Successfully created Location 'LOC4212' in PrismHR"

- If unsuccessful:

  • Export Status set to "Location Export Failed" or other API related lookup value
  • Export Log set to the error message from PrismHR, e.g.  "You cannot create another location with an existing code for the client 254"

Benefit tier validation rule - change from HE to SE ENHANCEMENT

Converted hard error rule HE_MultiplePlanTiers to soft error SE_MultiplePlanTiers. This allows multiple Offered plans which share a Benefit Plan to have different tiers, preventing exceptions when saving Offered Benefit Plan forms.


New PrismHR Code Tables ENHANCEMENT

The HRIS system has been enhanced, adding Employment code tables to match the Employment records in PrismHR

New 'Job Code' Dataform:

  • Job Code as Text
  • Job Name as Text

New 'Division Code' Dataform:

  • Division Code as Text
  • Division Name as Text

New 'Department Code' Dataform:

  • Department Code as Text
  • Department Name as Text

New 'Shift Code' Dataform:

  • Shift Code as Text
  • Shift Name as Text

New 'Pay Group Code' Dataform:

  • Pay Group Code as Text
  • Pay Group Name as Text 
  • Pay Group Frequency as Lookup (use Pay Frequency lookup group)

On Employment the following parent form fields have been added, to take advantage of these new code tables:

  • new "Job" (parent field). Drop list should show the Job Name.
  • new "Division" (parent field). Drop list should show the Division Name.
  • new "Department" (parent field). Drop list should show the Department Name.
  • new "Shift" (parent field). Drop list should show the Shift Name.
  • new "Pay Group" (parent field). Drop list should show the Pay Group Name.

All parent fields are filtered to the current workspace only.


Performance tune peo_cs_employee_s_dashboard_search ENHANCEMENT

The underlying stored procedure for the employee search dashboard has been performance tuned to optimize performance.


PrismHR Events, error when an employee CREATE event is processed

Resolved an issue where PRismHR Event creation would cause errors due to "Create" Events being sent for an Employee that did not exist in the system yet due to the timing of the PrismHR_Ongoing import and the Event scheduled process.


NAICS/SIC Swapped Around on OSHA 300A 

Resolved an issue where the NAICS and SIC codes were being swapped on the OSHA 300A report due to configuration in the system. The system will now place the SIC code value in the SIC field and the NAICS code value in the NAICS field on the report regardless of configuration.


Unhandled Exception on Case Escalation creation

Resolved an issue in the SetCaseCategory business rule where attempting the add a Case escalation without a case category or type would cause an exception to be created. The SetCaseCategory rule will now only be triggered on Add if the Case Type is not blank.


Icon on Case Discussion page is tiny

Icon size for attachments on the Case Discussion form has been increased to increase visibility.



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