Data Collection

This solution describes how your application can access and manage data in Attendance on Demand. It can help you determine which use case best meets your business need and guide you through the implementation.

  1. Background
  2. Data Collection Types
  3. Use Cases

Background

Attendance on Demand allows the user the ability to add a punch. The methods described below will demonstrate different scenarios and the capacity to utilize them to collect your data.

Function

Add, update, or retrieve Punch information in an Attendance on Demand system.

Data Collection Types

Punch Now

Transfers

Use Cases

Attendance on Demand has identified use case scenarios for managing employee punches (transactions).

Consult the table below to find the use case that aligns with your business needs, click the entry for a detailed explanation.

Use Case 1 - Adding a Current Punch for an Employee

Add a real-time punch to the database using the punchEmployeeNowByIDNum method

Preconditions

  • Employee ID is known/generated prior to adding

API Usage

Write punchEmployeeNowByIDNum

  • Adds the employee punch information to the database

Exception Scenarios

  • Condition: Employee ID does not exist in database
  • How to Handle: verify Employee ID number/existence of Employee

Use Case 2 - Add a Current Punch for an Employee with Location

Add a real-time punch, which includes the employee’s location, to the database using the punchEmployeeGeoNowByIDNum method

Preconditions

  • Employee ID is known/generated prior to adding
  • Employee location is known
    • Longitude
    • Latitude
    • Altitude
    • Accuracy

API Usage

Write punchEmployeeGeoNowByIDNum

  • Adds the employee punch to the database, including GPS data

Exception Scenarios

  • Condition: Employee ID does not exist in database
  • How to Handle: verify Employee ID number/existence of Employee
  • Condition: Invalid Station ID
  • How to Handle: verify Station ID is valid by using the getStationsSimple method

Use Case 3 - Adding a Timestamp While Transferring an Employee

Add a timestamp for an employee while being transferred to a different workgroup using the appendEmployeeTransferByIDNum method.

Preconditions

  • Employee ID is known/generated prior to adding
  • Workgroups employee is transferring to are known

API Usage

Read getWorkgroups

  • Retrieves a list of workgroup values and descriptors

Write appendEmployeeTransferByIDNum

  • Enters a timestamp and transfers an employee to a newly defined workgroup set

Exception Scenarios

  • Condition: Employee ID does not exist in database
  • How to Handle: verify Employee ID number/existence of Employee
  • Condition: Invalid Workgroup
  • How to Handle: Supply valid Workgroup values

Back to Top