Home > FAQ > Data Manipulation > Event histories (status histories)

Event histories (status histories)

An event history is a coded effective date array field, where each row in the array contains a date and a code indicating what happened on that date (e.g. hire, leave of absence, termination). Often, the provided event history includes employment events that don't change how service or salary is calculated (e.g., marriage, divorce, a new child, transfers to other locations/jobs). 

Events in the Database
Date Code Label
8/11/1999 01 Ineligible
1/10/2000 10 Hire
7/16/2007 81 Married
12/26/2009 82 New child
4/16/2010 31 Termination
5/17/2010 11 Rehire
8/3/2011 31 Termination
9/1/2011 11 Rehire
3/22/2015 41 Paid Leave
4/1/2016 42 Return from Paid Leave
10/27/2019 91 Divorced

To make event processing simpler and easier for you to review calculation results, you can adjust or cleanup the event history, removing all unnecessary rows. If you need to use the event history in an expression, then it's almost mandatory to clean it up (and add the final termination event, if appropriate) to make the expression simpler and easier to understand.

Service Events
Date Code Label
1/10/2000 10 Hire
4/16/2010 31 Termination
5/17/2010 11 Rehire
12/11/2021 31 Termination

 

Note, even if you haven't been provided with an "event history", you must be using date of hire and decrement date to calculate service/salary. ProAdmin considers those to be events, too.

Here are some topics which can help you work with an event history:

Cleaning or editing an event history
Creating a start event dates array (StartEventDates)
Creating a stop event dates array (StopEventDates)
How to determine if someone is working
Use events to count the days worked in a measurement period