Configure badging table data
Register details for a new provider, configure a badging table and import data from the source table to the target table to integrate with the badging system.
Before you begin
The Badging data table is the source table and the Employee Attendance Data table is the target table. The badging data from the source table is imported from a badging provider (for example, the attendance data from badge readers).
Role required: sn_wsd_wc.admin
Procedure
Navigate to All > Workplace Connectors > Provider Connector Configurations.
From the menu, select the application scope icon (
Application Scope icon.\).
Select Create New.
On the form, fill in the fields.
| Field | Description |
|---|---|
| Provider | Name of badging data provider. |
| Source Type | Source from where the badging data is collected and loaded into the target Employee attendance table. From the drop-down list, select Table. Note: If you’re an existing user and have selected the Import from table option in an earlier release to retrieve badging data in your Workplace Connectors instance, the Source Type field is defaulted to Table. If the Import from table option wasn’t selected in your Workplace Connectors instance, then the Source Type field is defaulted to External. The Import from table option isn’t supported in the November ServiceNow Store release. |
| Run frequency | Day and time frequency to import data from the workplace system. For example: 5 minutes.The process provider data record picks the records from the badging data table and populates the Employee Attendance table based on the run frequency. |
| Active | Option to indicate that the provider configuration is active. |
| Connector Configuration | Select the lookup list icon ( Image omitted: look-up-icon.png Lookup list icon.) and select <strong>Badging</strong>. For more information, see <a href="../workplace-connector-configuration/">Configure connectors for badging data</a>.</td></tr></tbody>
Parent Topic:Provider connector configuration Previous topic:Provider connector configuration Next topic:Configure a webhook event |