Searching for Clock Punches

You can search for specific clock punches, such as all the punches performed by a specific employee, among the punches the WBCS has received. You can search for punches received on certain dates and order the results by employee badge numbers or specific clocks.

To search for clock punches:

  1. Click the Journal tab.
  2. Select whether you want to search for accepted or rejected punches:
    • Click the Journal tab to view accepted punches.
    • Click the Rejected tab to view rejected punches.
  3. Specify the start of the date range you want to search for punches the WBCS received in the START DATE field.
  4. Specify the end of the date range you want to search for punches the WBCS received in the END DATE field.
  5. Select the employee badge you want to search for using the BADGES Lookup button. Leave blank to display punches preformed by any employee.
  6. Select the specific clock you want to search for using the CLOCKS Lookup button. Leave blank to display punches performed on any clock.
  7. Select which time to display for each received clock from the FOR RELOAD USE drop-down list. You can select one of the following options:
    • Server Time displays the time tracked by the WBCS.
    • Clock Local Time displays the time tracked by the clock.
    • Admin Console Time displays the time tracked by the admin console.
  8. Specify the maximum number of punches you want the search to return in the Maximum number of records field.
  9. Click Search / Reload Data from Server.

    Changing the displayed time is typically done if the clock, computer running the Admin Console, or the WBCS, is in a different time zones than the user. This setting allows the user to view the time in the Admin Console relative to different time zones

    To avoid problems with daylight savings time changes, restart the clock server every time the time zone is changed.

    The Journal page displays the punches received by the WBCS that match the search criteria. This information is displayed for each punch:

    JOURNALID

    A unique ID number assigned to the clock punch. Numbers are assigned in the order the punches are received by the WBCS, and are re-indexed whenever the journal is archived or purged.

    TYPE

    Each clock punch has a swipe type, a two-digit number. The swipe types represent what information the user is recording on the clock, such as clocking in or out. The TYPE column displays the swipe type. The following swipe types represent the most common clock punches:

    • 01 In
    • 02 Out
    • 03 Job
    • 04 Docket
    • 06 Time Code
    • 07 Department
    • 08 Project
    • 09 Timesheet
    • 11 Directionless
    • 00 Heartbeat

    For a complete list of swipe types, refer to Swipe Types.

    TIME
    The time of the swipe. For example, 6/13/2005 2:15PM America/New_York
    RDRNAME
    The name of the clock on which the punch was performed.
    BADGE
    The badge number of the employee who swiped.
    SUPBADGE

    The badge number of the supervisor that punched along with the employee. (Blank if no supervisor punched.)

    EXTRADATA

    Extra data transmitted with the swipe. This data is the additional information stored in the journal entry for the particular swipe.

    SENTTOXML

    Status on whether an XML file has been created (T) or not (F). XML files are created for each swipe, and used when passing information from the WBCS to the database and/or the system.

    A swipe status of U indicates that the swipe will be unprocessed. Swipes with a status of U will not be sent to WFM and will not affect the employee's timesheet since they have no bearing on the timesheet. An example of this is viewing the last swipe or training, both of which have no impact on the timesheet and will not be sent to WFM and will only be captured in the logs.

    If you enable the Save Unprocessed Swipe Validation, WBCS will save clock punches of the specified type with a U status and these swipes will not be sent to WFM. For more information on this type of validation, see Validations Overview.

    INERM
    Status whether the swipe/transaction was sent to the system (T) or not (F).