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


Sprint Began: 9/11/2017     Sprint Ended: 10/6/2017


The following items have been completed in this release:


OSHA 301 Merge - Comp Claim dataform - ENHANCEMENT


A PDF based merge of ClientSpace Claim information to the OSHA 301 form has been added to PEO. The merge will run from the Comp Claim dataform.   The merge uses the following fields:

NEW FIELD(S) ON COMP CLAIM INJURY:
 - Describe Injury or Illness as Text Wide
 - Treated In Emergency Room as Lookup type (Yes, No)
 - Hospitalized Overnight as Inpatient as Lookup type (Yes, No)

FROM EMPLOYEE DATAFORM:
 - FirstName
 - LastName
 - Address1
 - Address2
 - City
 - State
 - ZipCode
 - DOB
 - crGender (code value)

FROM CURRENT EMPLOYMENT DATAFORM:
 - OriginalHireDate
 - HireDate

FROM COMP CLAIM DATAFORM
 - CarrierClaimNumber
 - SystemClaimNumber
 - DateInjury
 - DateReported
 - TimeWorkdayStart
 - TimeInjury
 - DateDeath
 - ClaimSpecialistName (fkClaimSpecialistUserID, decode to User's Firstname Lastname)
 - ClaimSpecialistTitle (fkClaimSpecialistUserID, decode to User's Title)
 - ClaimSpecialistPhone (fkClaimSpecialistUserID, decode to User's Phone)

FROM COMP CLAIM INJURY DATAFORM:
 - PreInjuryActivity
 - InjuryAccidentDetails
 - CauseInjuryDetail
 - InjuryOrIllnessDetails (new field as Text Wide)
 - TreatedInER as Lookup type (new Yes, No lookup field)
 - HospitalizedOvernight as Lookup type (new Yes, No lookup field)

FROM TREATMENT DATAFORM:
Get Provider details for the oldest active treatment record using the Treatment.fkProviderID
 - ProviderName
 - ProviderAddress 1 & 2 (insert a comma and space if there is an address 2)
 - ProviderCity
 - ProviderState
 - ProviderZip
 - Physican (new 'text' field on treatment dataform)


Display WC Code on Work Item - NEXT -  ENHANCEMENT


NEXT has been enhanced to display the Comp Code and State in the Work Item when on the Pricing Comp Code.   The system will now display 8810FL for a code of 8810 in the state of FL.  For more information on Work Items read "Navigating ClientSpace NEXT".


Update Logic to Throw Error "Data Will be Lost" if Navigating to a Required Form - ENHANCEMENT


Enhanced the business logic when clicking the Required Forms link so that the system will warn you that navigating away from the page may cause data loss, as it does when you close a dataform without saving changes.

Surcharge Security 


Updated Surcharge Security to resolve an issue where a ClientSpace user that did not have access or had limited access to the Surcharges dataform was still able to access and edit surcharges through the pricing console. Pricing console now respects the View / Add / Edit rights maintained in Role administration.

Client Reinstate rule exception


Resolved an issue where under certain circumstances if the Pricing comp code or pricing State records become inactivated the system would throw an error when attempting to reinstate the terminated client. System will no longer throw an error.

Approval Process enhancement - ENHANCEMENT


Enhanced the underwriting approval process to remove the ability to mis-configure business rules on approval creation that could cause the pricing workflow to break.

"Override Pricing" defaults issue


Resolved an issue where when "Override Pricing for this batch" is ticked the Minimum Admin Per Account and Minimum Admin Per Head fields were re-defaulting back from the Admin Workspace, overriding any changes that had been made.

Pricing Locked issue


Resolved an issue where when Recalculate Pricing logic runs on the Batch, State & Codes a BatchRepricing checkbox on the batch is ticked and then unticks when pricing is finished to prevent multiple users from making pricing changes at the same time. If the logic doesn't fully run or an exception is created the checkbox would remain checked. The logic has been changed so the box will be unchecked regardless.

PrismHR API Import Gray List Clients - ENHANCEMENT


Added the ability to specify which Client Numbers should not import specific Employment data or Payroll/Billing Vouchers from PrismHR via the API. No payroll/billing vouchers will be imported, and the following Employment fields are set to "0" during the initial and ongoing employment import:
- HourlyRate
- AnnualPay
- WageRate
- AnnualPayPctChange
- AnnualPayrollAmountChange

To configure graylist clients, add the following to the Additional parameters section of the Prism API configuration in ClientSpace:  graylistclients=### (### to be replaced with the actual client number of the client to be listed.  be sure to include leading zeroes if your prism installation utilizes this numbering format)

Database Performance Tuning - ENHANCEMENT


Database performance tuning has been done to enhance performance for some commonly used dataforms such as the Client Master and Policy Comp Codes.


Widget Drill Down Issues


Resolved an issue with some widgets where when drilled into to get the underlying dataform search the appropriate Key was not being passed so the system would return an unfiltered list of records by default.


Sales Force triggering changes - ENHANCEMENT


The stored procedure that monitors the field change audit table changes was missing basic Organization fields.  Updated the code which monitors the field changes and triggers events.  The following fields are now included in the Update to Salesforce triggering process (PEO):

Org Trigger Fields

  • 'Name',
  • 'AKA',
  • 'Phone',
  • 'Fax',
  • 'crStatus',
  • 'Address1',
  • 'Address2',
  • 'City',
  • 'State',
  • 'PostalCode',
  • 'Country',
  • 'luCurrentPEO',
  • 'crSource',
  • 'crBusinessType',
  • 'Website',
  • 'IndustryCode',
  • 'EmployerIDNumber',
  • 'crCategory','DoNotCall',      

Org Other Info Fields
'EmployeeCount','GrossPayroll',                 


Contact Trigger Fields

  • 'fkOrganizationId',
  • 'fkAssignedToUserID',
  • 'FirstName',
  • 'LastName',
  • 'Title',
  • ‘Category',
  • 'BusinessPhone',
  • 'Email1',
  • 'CellPhone',
  • 'Fax',
  • 'Address1',
  • 'City',
  • 'State',
  • 'PostalCode',
  • 'Country',
  • 'Active',


Contact Other Info Trigger Fields
'mluContactType',

Client Master Trigger Fields

  • 'ClientNumber',
  • 'Status',
  • 'Dateof1stPayroll',
  • 'ContractEffectiveDate',
  • 'CorporationType',
  • ‘luAltIndustryCode',
  • 'SalesRegion',
  • 'fkParentCompanyID',
  • 'luKillReason'

 

Unable to close case


Resolved an issue where the HE_ValidateIncidents business rule on Cases was triggering even though there are no active tasks, because the tasks were a different status than 3-Complete.

This rule has been adjusted to ignore Tasks that are inactive.


NEW POLICY STATE COST FACTORS DATAFORM -  ENHANCEMENT


A child dataform has been added to the WC Policy dataform to manage and track cost factors by state. This new table has a parent form field to the WC Policy that is read-only and a State lookup field that is required.


  • When adding a new Policy State Cost Factors record from the policy, default all field values from the policy.
  • When determining which Cost Factors to use for calculating a funding rate or defaulting on the pricing state, the system will use the Policy State Factors if they exist for that state otherwise will use the Policy cost factors.
  • A link has been configured to open the Policy State Cost Factors dataform from the WC Policy and secure to this dataform's security entity. The link is only visible if the "Use Cost Factors" is set to "Yes".
  • The Policy State Cost Factors form is cloned when a policy is renewed. This applies to Policies in either the Admin Workspace or in the Client's workspace.
  • A HE Rule "HE_HasDuplicate" has been created to prevent duplicate Policy State Records. 
  • All pricing calculations which take Cost factors into account have been re-factored to use this new dataform if available.




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