Setup Device Manager (InTouch)

Enable Clock Integration

To enable clock integration in this application:

• Clock Integration (IC) license is required
• System Administrator must have Device Manager granted in System > Authority Levels
• Login Policy for employees must have InTouch Timeclock Device selected.
• Employees must have their Badge ID populated specifically in the InTouch Timeclock Badges field (not Badge ID).
• The Device Manager must be configured.

Badge ID Integration

Badge ID configurations available include Simple Badge ID and Effective Dated Badge ID.

• Simple Badge ID's are always active and do not have a PIN.2 Active in the background from 12/31/1900 to 12/31/9999)
• Effective Dated Badge ID's requires a Start Date, everything else is optional.

Workforce Ready...

Workforce Ready supports simple and effective dated badge numbers. However, this application currently supports only Simple Badge IDs for Workforce Ready. Badge IDs are imported using the Workforce Ready Person Import task.

Workforce TeleStaff ...

Workforce TeleStaff supports effective dated badge numbers. This application supports only Effective Dated Bade IDs for UKG Dimensions integrations. Badge IDs are imported from Dimensions using the Workforce TeleStaff Import Employee Badges task.

Authentication and Authorization

Authentication is handled by the InTouch timeclock device. The device ID must match one that is configured in this application. This application validates that the request is actually coming from a known clock. When a Device ID match is found, then the Badge ID must match a user's Badge ID. If not, then a login failed alert displays on the timeclock.

Authorization, known as Authority in this application does not change user access controls on the timeclock. The timeclock does not provide a way to prevent button access based on the user, as such authentication is step by step. For example, in this application we check authorization based on the days that are being requested for a given action. A user may not currently have the right to add a code today, but they may have it next month.

Clock Authentication

Currently authentication is based on date. In Workforce Ready a Badge ID can be assigned to a person for the entire day. In Workforce Dimensions, a single Badge ID can be assigned to two different users for a day on different times. As such, it is possible to assign Badge ID "1234" to Person A from 4/1/2020 8:00 AM to 4/1/2020 11:00 AM and to Person B from 4/1/2020 11:00 AM to 4/1/2020 5:00 PM. The Badge ID is matched to the person based on the login time. If user logs in between 8:00 AM to 11:00 AM, then this Badge ID maps to Person A and if the user logs in to the clock between 11:00 AM to 5:00 PM, then the Badge ID maps to Person B.

Initially, Badge ID was a start and end date field in this application, and now a date and time field for Ready and Dimensions integrations. Ready displays time as 00:00 - since only the date is available in Ready at the time of writing this, and Ready does not display the time. Dimensions displays actual time. In Dimensions the time is converted from UTC to the person’s time zone.

Additionally, in a Dimensions integration timezones are not available in the People Editor where Badge IDs are managed. As a result, it is probable that the same Badge ID is assigned to two different people in different timezones. When the time input is converted in UTC, that time may conflict for both people. When this is the case, albeit rare for devices to cross timezones, it is possible, and as such this application will not be able to map the Badge ID to a specific person until the duration of the timezone offset elapses. In this case, the person will see a login fail type message. Once the duration of the timezone offset is over, the correct person will be able to log in to the Smart Views specific to this application.