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

Owned by Tony Hayes
Last updated: Nov 06, 2017
7 min read

Sprint Began: 10/09/2017     Sprint Ended: 11/03/2017

The following items have been completed in this release:


User Field - Case Escalation  ENHANCEMENT

A new field has been added to the User Other Info tab called "Immediate Supervisor" - This is a User datatype.

The Case escalation process has been enhanced to include "Next Priority", "Next Assigned to User" and "Escalation Notification Recipient" (includes "Immediate Supervisor").  When a case with a matching priority and an Escalation Time value less than or equal to now the case will be escalated, Setting the Priority to "Next Priority", the Asssigned To User to "Next Assigned To User" and notifying the "Escalation Notification Recipient" 

These escalations can then be cascaded - Low to Medium, then Medium to High and so on changing the escalation hours, assigned to or notification recipient as required.  For help configuring case escalations, contact your account manager.

The following system changes have been completed for this development:

New fields have been added to the Case Type Escalation
   • Next Priority (Lookup)
   • Next Assigned To User (User filtered by Role, PEO Employee role)
   • Send Escalation Email (checkbox)
   • Escalation Notification Recipient (Lookup)
   • Role
   • Department Manager
   • Immediate Supervisor
   • Escalation Email Role (role selector)

Field Display Rules were added:
  • When "Send Escalation Email" = True Then enable "Escalation Notification Recipient"
  • When "Escalation Notification Recipient" = RoleThen enable "Escalation Email Role"

  • Added a new field to User Other Info tab called "Immediate Supervisor" - User selector datatype.

  • Added metadata to Case Status for "Exclude from Escalation"

  • Created a new Schedule Process called Process Case Escalations.
  • When this process runs, it checks the Case Escalation 1 fields to determine if the case should be escalated, if so, then it checks for the "Exclude from Escalation" flag, Next Priority, Next Assigned To User, and the Send Escalation Email flag.
  • If "Exclude from Escalation" is checked, then end, if unchecked we proceed to the next step.
  • If Next Priority is set, then change the Case Priority. This triggers a business rule to reset escalation fields.
  • If Next Assigned To User is set, the system changes the Case Assigned To User.
  • If Send Escalation Email flag is checked the system then sends a new Case Escalation email. This email should use Email Templates with the same Field Replace logic as the existing case notification email template.

  • A new business rule has been added to the Client Service Case that will recalculate the Case Escalation fields any time the Case Priority changed.


Convert Landing Pages and Headers to Widget Layouts  ENHANCEMENT

The Workspace Landing Page headers have been Widgetized - allowing for the items displayed at the top of the Workspace Landing Page to be customized by Contract Stage.  By default, our PEO system has been configured with three unique landing page "styles" -

Client:  Contract Stages of "Client" and "Terminated"

Implementation: Contract Stage of "Implementation"

Prospect: Contract Stages of "Prospect", "Declined" and "Dead"



Add Client Number to Case Emails ENHANCEMENT

The code which provides data for the Client Service Case notification has been enhanced to add Client Number from the Client Master as an optional replacement field. This information can be added to Client Service Case notifications using the replacement code of {ClientNumber}.


Email Template Stored Procedures ENHANCEMENT

Field replacement SQL has been added which returns Employee and Employment fields designed for automating email template workflow driven by the termination of an employee.   The stored procedures 'peo_employment_emailtemplate_merge' and 'peo_employee_emailtemplate_recipient_proc'  which return the following values for field replacement:

  • EeFirstName
  • EeMiddleInit
  • EeLastname
  • EeFullName
  • EeAddress1
  • EeAddress2
  • EeAddress
  • EeCity
  • EeState
  • EeZip
  • EeCSZ
  • EeCounty
  • EeIdentifier
  • DOTEmployee
  • EeSalutation
  • EeMedCard
  • EeNickname
  • EePhone
  • EeMobile
  • EeFax
  • EeEmail
  • W2Address1
  • W2Address2
  • W2Address
  • W2City
  • W2County
  • W2State
  • W2ZipCode
  • W2CSZ
  • EeifkEmployeeID
  • EmployeeEmploymentID
  • EmploymentStatus
  • EmploymentType
  • HireDate
  • HomeDept
  • JobCode
  • JobTitle
  • LastDateWorked
  • LastPayrollDate
  • LastPayrollUpdate
  • ClientLocationID
  • OriginalHireDate
  • PayFrequency
  • PayMethod
  • ReasonForTerm
  • SeniorityDate
  • EeShift
  • HoursPerPeriod
  • StartDate
  • StatusChangeDate
  • SutaState
  • TermDate
  • WageRate

peo_employee_emailtemplate_recipient_proc returns the following recipient values:

From: Default admin email from App Settings

To: Terminating Employee and Client Contact from that employees' default location

CC: None

For information on how to use this new functionality to streamline your employee termination workflow, contact your account manager.


Employee Benefits Detail dataform ENHANCEMENT

A new PEO multi dataform has been added - "Employee Benefits Detail" designed for tracking individual employee benefits.  The dataform contains the following felds:
  - Related Employee (Parent Form; Employee Demographic; Multi)
  - Status (lookup; new lu group "Employee Benefits Detail Status"; Pending, Active, Expired)
  - Group Number (Text)
  - Subscriber Number (Text)
  - Effective Date (Date)
  - Expiration Date (Date)
  - Plan Type (lookup; Same as on Benefits Plan)
  - Offered Benefits Plan (Parent Form - Offered Benefits Plan)
  - Coverage Level (lookup; same as on Employee Benefits)
  - Plan Tier (Parent Form - Benefits Plan Tier)
  - Employee Premium (Money)
  - Employee Cost (Money)
  - Dependent Premium (Money)
  - Dependent Cost (Money)


Case Discussion Email Template issue

Resolved an issue where unpublished email templates were available when creating or replying to case discussions. Email Templates are now hidden on the Case Discussion if no Email Templates are configured or published.


Corrected the Workers' Compensation and Unemployment Insurance  widget dashboard search SQL to utilize the ProjectUser table to filter the results to only workspaces to which a user has access.


Performance Tuning - Pricing Matrixes ENHANCEMENT

The code which generates the data for the Pricing console matrixes which display aggregate pricing data have been optimized to improve performance on sites with many states and codes within a batch.


WC Code Marked Review when WC Carved Out

Resolved an issue where Pricing Codes would be continuously marked as "Needs Review" even if the associated Pricing State was set to not offer Workers' Compensation. Unchecking the "Needs Review" flag for states that do not offer comp will now persist after code save and not get re-set.


FEIN editable and should not be 

Resolved an issue in the pricing console where Org fields were locked on the Client Master, but remained unlocked on the same fields when displayed in the pricing console, allowing the fields to be editable when they shouldn't. These Organization fields now properly mimic their behavior on the Client Master dataform.


Cost Adjustment Factor Issue

The Cost Adjustment Factor on the new Policy State Cost Factor dataform includes logic to respect the High Deductible Factor on the related WC Policy. When the High Deductible Factor on the Policy was changed the system did not refresh the Cost Adjustment Factor value on the related Policy State Cost Factor Dataform.

As a result the Funding Rate was not getting re-calculated.

A change was made so that when the High Deductible Value is changed on the policy the system refreshes the Cost Adjustment Factor on the related Policy State Cost Factors and in turn runs the logic to refresh the Funding Rates for the Codes in that State.


PrismHR API upgrade to version 1.10 ENHANCEMENT

Upgraded the PEO services to the API code v1.10
Added implementation of  Location Code when creating Clients - Main location will be created on initial Client Export

New Voucher summation field mappings have been added - The API Paths are:
- Payroll/SUMAdministrativeFee
- Payroll/SUMFICAMedicare
- Payroll/SUMFICAOASDI
- Payroll/SUMFUTA
- Payroll/SUMGrossWages
- Payroll/SUMSUTA
- Payroll/SUMWorkersCompensation


Client Policy Rates not Defaulting

Resolved an issue where Client policy rates would not get reset properly if initially overridden.


OSHA 300A Average EE Logic 

Corrected an issue with OSHA 300A report where employee totals and payroll period counts would not match up properly if employees were in multiple pay cycles. Also adjusted the report to use Period End Date instead of PayDate for date calculations


Pricing Console excessive pricing matrix requests ENHANCEMENT

The method by which the pricing matrix acquires data to populate the fields has been re-factored to make it more efficient, only refreshing overall pricing when there is a change to the underlying data that would affect all of the data - switching states in the pricing state grid for example no longer refreshes all of the page data, merely the pricing state matrix.


Overall Breakdown does not display Data 

The Pricing Matrix has been converted to a 'widget' and the input data requirements changed. This caused the link to become non-functional.  This has been corrected and the Pricing Breakdown now works corectly.


Minimum Premium not being cloned

Resolved an issue where during WC Policy renewal, the related WC Rates are cloned. During this process the Minimum Premium field was not getting cloned this has been corrected and Minimum premium is now appropriately cloned to the new policy rates.


PrismAPI - Contact Import - Phase 1 ENHANCEMENT

Our PEO system has been enhanced to use the newly available Contact Information in the PrismHR API. Initial Contact imports are available to synchronize Contact information from PrismHR to ClientSpace.


Case Category on Case Type Escalation ENHANCEMENT

A new business rule has been created to enhance the case escalation process - "SetCaseCategory" will automatically set the appropriate category based on the Case Type for which the escalation record is being created. Previously Category would default to blank, allowing for an unusable escalation record to be created as Category is not a required field on the form. This new rule guarantees the appropriate category will be set every time.


PrismAPI - Company Initial Enhancements - Create Legal Entities ENHANCEMENT

The Company initial import has been enhanced to now create legal entity records in the Admin workspace for PrismHR clients where the associated Legal Entity does not already exist in ClientSpace.  Previously these records would be skipped with the error "A matching legal entity record cannot be found for client XXXXX"

This process creates a very basic record, it is recommended that a ClientSpace Admin update this record with data from PrismHR as soon as possible after the stub record is generated.  For Non-PEO clients if a matching record is not found the system will create a "GENERIC ASO" legal entity.  This will be used by all subsequent non-PEO clients where a matching legal entity cannot be found.


PrismHR subscription forms

Resolved an issue of the PrismHR subscription log files growing too large on installations using the PrismHR API with large data sets. Instead of appending data to the Notes field, the system now will replace existing data with the current Subscription information.


Client Master SetLegalEntity rule exception

Resolved an issue where the CM SetLegalEntity rule might cause an exception if the workspace is not using pricing (i.e. no batch). The exception was a foreign key constraint violation because the value of '0' is being set on the fkLegalEntityID field.



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