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

Owned by Tony Hayes
Last updated: Nov 28, 2016
5 min read

Product Version: PEO – Release 44 Notes - The following Tasks have been completed/fixed in this release.

 

Task 36523                                                                                                                                      

Employee Name on Comp Claim Treatment Record    

Resolution:                                                                                                    

The comp claim dataforms have been enhanced in NEXT - the Employee data panel widget has been added to all tabbed dataforms of the Comp claim. 

 

Task 36527  - ENHANCEMENT                                                                                                                                          

Soft Error on Admin Workers Comp Policy    

Resolution:                                                                                                    

The Risk management system has been enhanced - changing the "Use Cost Factors to Calculate Funding Rate" to "Yes" on a Workers comp policy will now prompt the user with the following soft error:

"Setting the Policy to calculate the funding rate using cost factors will overwrite existing factors such as the Experience Modifier" - Save Anyway?  Previously the system would apply the changes without prompting, overwriting the funding rate with the new calculated rate with no chance of backing out before applying the changes.

 

Task 36528                                                                                                                                      

Error executing child request for handler 'System.Web.Mvc.HttpHandlerUtil+ServerExecuteHttpHandlerAs    

Resolution:                                                                                                    

Resolved an issue where if a Workspace got into the state where there are associated claims, but the Workspace does not have an associated Org record, the contact widget would throw a generic 'Error executing child request' error.

 

Task 36640                                                                                                                                      

Case Types in NEXT    

Resolution:                                                                                                    

Redundant gen_AdminCaseType fields have been removed from PEO - the following fields:

  • isBillable
  • luBillType
  • BillForContractTypes

Have been removed as they have been replaced by

  • Billable
  • luBillUnit
  • mluBillForContractTypes 

 

Task 36589                                                                                                                                      

MailMerge IsSystem flag    

Resolution:                                                                                                    

PEO merges have been identified and marked as System level merges, securing the Stored procedure and template fields.  This item only affects NetWise, system level merges. 

 

Task 36593                                                                                                                                      

Changing Related User on Contact and then changing it back alters the original user record    

Resolution:                                                                                                    

Resolved an issue where removing a related user from an Organization contact would reset values on the user account you were disassociating the contact record from.  System will now only update User values On add, or in the case of switching related users, the new user record will be updated.  Example - Contact has a related user of User 1, you edit the contact record, change the email address and phone number and change the related user to User 2.  User 2 records will be updated with FirstName, LastName, contact info including new email address and phone. 

User 1 will not be updated with new email and phone as the contact record is no longer associated.

 

Task 36628                                                                                                                                      

"SUTA Discount"     

Resolution:                                                                                                    

Resolved an issue where the pricing logic had a hard coded 25% maximum SUTA discount.  The system now respects Discount thresholds stored in the Admin Workspace.

 

Task 36652                                                                                                                                      

Clients dashboard in Next not returning results    

Resolution:                                                                                                    

The Client Search dashboard in NEXT has been optimized to more quickly return large datasets.

 

Task 36651                                                                                                                                      

Employment form    

Resolution:                                                                                                    

Resolved an issue where if an employee's location was not set, the employment link in the header of the NEXT employee record would jump to an employment record in the "Add" state. 

 

Task 36709                                                                                                                                      

Refactor peo_pricingcode_u_reprice    

Resolution:                                                                                                    

The Pricing code reprice action has been updated to handle the unlikely case where a Pricing code is missing either a state or code and the system missed the fail-safes which disallow this situation.  In the unlikely case this happens, an exception will be thrown and repricing will stop.

 

Task 36675                                                                                                                                      

Pricing Console Dirty    

Resolution:                                                                                                    

Resolved an issue where under certain circumstances, creating pricing and generating a workspace from the Pricing Dashboard would leave the Pricing Console in a "Dirty" state where the system would think there were unsaved changes. 

 

Task 36690                                                                                                                                      

Census Import / PT EEs    

Resolution:                                                                                                    

The Employee census import process has been updated to properly manage full time and part time employees when generating pricing comp codes from an employee census upload. 

 

Task 36725                                                                                                                                      

Terrorism Surcharge Calculation    

Resolution:                                                                                                    

Corrected an issue with the Terrorism Surcharge calculation - the calc is now (TerrorSurch*(1/ManualRate)*100). 

 

Task 36761                                                                                                                                      

peo_merge_csa needs to be refactored    

Resolution:                                                                                                    

Refactored the merge stored procedure - peo_merge_csa to optimize the code and update the method in which legal entity is selected to match the current method used by the pricing process. 

 

Task 36739                                                                                                                                     

Comp Claim Import Bug    

Resolution:                                                                                                    

The comp claim import process has been updated to correct an issue where under certain circumstances the Employee or Policy link could be cleared from an existing claim by an update.   

 

Task 36789                                                                                                                                      

Employee Header link to employment record should be disabled if no Employment record present    

Resolution:                                                                                                    

Resolved an issue where the employment jump link on the employee record was available even if the system did not contain an employment record for that employee.  System will now present a message stating "No active employment record found." if there  is no current employment record available.

 

Task 36836                                                                                                                                      

Current Record flag not set by Employee Census upload on Employment record    

Resolution:                                                                                                    

The Employee Census process has been updated to set the "Current Record" flag on the Employment records created during the census upload process. 


Task 36570                                                                                                                                      Click here for the Video

Loss History     

Resolution:                                                                                                    

The Workers' Comp Claim system has been enhanced with updates to the Loss Development Factors system:

Loss Development Factor Dataform Configurations:  

  • Loss Data Factor Dataform has been renamed Loss Development Factor  
  • Loss Data Factor field has been renamed  to Loss Development Factor  
  • A "State" Lookup has been added to the form to make calculations configurable by state.

Loss History Dataform Configurations (Chocolate):  

  • An "As of Date" as a Date field has been added, required.  
  • An "LDF State" has been added as a lookup of States, derived  (Set from Organization.State on SAVE)
  • An "LDF field has been added as a decimal, derived (see below), editable.

Business Logic (Chocolate):

  • The system will default the LDF State field on the Loss History to the Org State when the field is empty. 
  • If the Org State is not filled in the system will leave this blank.
  • The system will default the Loss Development Factor field on the Loss History only when adding a new record. This value is looked up from the Loss Development Factor admin form using the LDF State and the calculated number of days since the As of Date. 
  • If the State is not provided then the factor is looked up  just on the As of Date. If a value still can't be determined then default to 2.0. NOTE: We compare Start Date and As of Date to find the correct LDF record
  • If the State, Start Date, As of Date, incurred value, or LDF are dirty on a subsequent update, then the system will provide a Soft Error letting the user know the Loss Development Factor will be updated.
  • The Projected Incurred Value on the Loss History form will also be defaulted when the form is saved.  Projected Incurred Value = Incurred Value * LDF.

 

 

Task 36789                                                                                                                                    

Employee Header link to employment record should be disabled if no Employment record present   

Resolution:                                                                                                    

Previously the link on the employment panel of the Employee dataform in NEXT would link to a dataform in "Add" mode if no employment record existed for the employee, unfortunately it the add would not automatically link the new Employment record to the employee from which it was created. 


 

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