Events

An event is a single, recorded incident. The most common example is an employee being late for their scheduled work start. Events are assigned point values. When an employee's timesheet triggers an event, those points are added to the event log.

The presence of a relevant time code on a timesheet does not automatically trigger an entry in the event log. Event logging, violation logging, and generating of workflow messages all occur through the Attendance Control Process Task.

See Setting up auto-processing.

In addition, only days that have been authorized are considered as eligible for event log entries. If an employee has a LATE time code on an unapproved day, it's not considered an event at that time. For it to be an event, it must be authorized.

See Authorizing events.

If the day is authorized and an event-related time code is present, the processing task creates the event log entry. The status of the entry is set to PROCESSED. Other information is included in the log, such as when the entry was created, when the day was authorized, and the day the event occurred (timesheet date).

Note: Event definitions can include a custom action or condition. A custom condition is a class that performs some specialized evaluation to determine if the event should be logged. A custom action is a class that runs when the event is created (for example, set an employee UDF to a particular value).