Setting up events

  1. Select Maintenance > Optional Modules > Attendance Control > Event Setup.
  2. Click Create New Entry.
  3. Specify this information:
    Event Name
    Specify the name of the event.
    Description
    Optionally, specify a short description of the event.
    Time Codes
    Select the time codes to which the event applies. Time codes indicate how a particular segment of time was recorded such as WRK or LATE. Within an event definition, time codes identify segments of an employee's timesheet that are noteworthy when it comes to a company's attendance control policies.
    Pay Groups
    Optionally, select the pay groups to which the event applies. If left blank, this field defaults to all pay groups.
    Calc Groups
    Optionally, select the calculation groups to which the event applies. If left blank, this field defaults to all calculation groups.
    Minimum Duration
    Optionally, specify the minimum length, in minutes, the conditions of the event must last for Attendance Management to count the event as having occurred. When blank, the event does not have a minimum duration. For example, an event tracking lateness with a minimum duration of ten minutes only counts employees as late when they start work ten or more minutes after their shift started. An employee who was eight minutes late would not trigger this event.
    Maximum Duration
    Optionally, specify the maximum length, in minutes, the conditions of the event can last for Attendance Management to count the event as having occurred. When blank, the event does not have a maximum duration. For example, an event tracking lateness could have a maximum of 240 minutes because after four hours the employee is considered absent for their shift and a different event is triggered.
    Points
    Specify the number of points that are added to the event log when the event is triggered. Decimal values are accepted. To assign the minutes function to this field, leave the default as V. This sets the points to equal the minutes that are associated with LATE time codes. For example, one minute late equals one point.
    Priority
    Specify a number to represent the order in which the system registers the event (priority 1 indicates that the event is highest priority).
    Condition
    Optionally, specify the customizable condition that applies to the event.

    You can populate this field with any custom condition that implements the com.workbrain.app.modules.ac.testevent.TestEvent interface, as defined below:

    public interface TestEvent {
      /**
      * Executes a customized testing logic and returns
      * true if the given employee, work summary, work detail and 
      * event pass the test.
      *
      * @param conn database connection
      * @param employee employee
      * @param summary work summary
      * @param detail work detail
      * @param event attendance control event
      * @return true if the parameters pass this test
      * @throws ACException
      */
      public boolean test( DBConnection conn,
        EmployeeData employee, WorkSummaryData summary, 
        WorkDetailData detail, ACEventData event )
        throws ACException;
    }
    Action
    Optionally, specify the customizable action that is assigned to the event. The action is triggered when the event occurs. The action can be any Oracle procedure.
    Acevt Flag1-10 (Event Flag1-10)
    Optionally, select flag options for a set of customizable event property flags. These user defined flags are linked to the EMPLOYEE record flags. If the user defined Flag1 in the EMPLOYEE table is defined, then Event Flag1 can be used to filter employees with Flag1 defined.
    Acevt Udf1-10 (Event UDF1-10)
    Optionally, specify field options from a set of customizable event property fields. These user defined fields (UDFs) are linked to the EMPLOYEE record UDFs. If the UDF1 in the EMPLOYEE table is defined, then Event UDF1 can be used to filter employees with UDF1 defined.
    Teams
    Optionally, select the teams to which the event applies. If left blank, this field defaults to all teams.
    Apply to SubTeam
    Optionally, select this check box to include the sub teams of the teams to which the event applies.
    Employees
    Optionally, select the employees to which the event applies. If left blank, this field defaults to all employees.
    Note: Because of the way the application processes events and violations, these lookups should not be configured with the optional ALL button. If left blank, the lookup defaults to all values, so the button is unnecessary.
  4. Click Save.