|
Http Verb |
GET |
|---|---|
|
Url |
/scheduling/r1/clocking-types/{clockingTypeId} |
|
Permissions required |
|
|
Personally Identifiable Information (PII) |
No |
|
Sensitive Information |
No |
|
Last Modified Version |
r1 |
|
Released since |
2024 W2 (FSM 17.0) |
|
Deprecated since |
|
|
Removed since |
|
|
Tech Tags |
|
Business Logic
This API returns the requested Scheduling Clocking Type.
A scheduling clocking type defines whether a resource has to clock in/out and what happens if it does not. It can be assigned at three levels:
-
the resource
-
the work shift type, as a default
-
the single work shift
It does not represent a single clocking event (e.g., a resource clocking in/out etc.) or what a single clocking event represents (e.g., shift start, shift end, lunch break, etc.). It only states the clocking obligation of the resource or shift.
Available values:
-
NO STAMPING → The resource is not required to clock in/out. No clocking-related checks are applied.
-
STAMPING NO MOBILE OPERATION → The resource must clock in/out. Without a valid clock-in, the resource cannot operate from the mobile app.
-
STAMPING NO ASSIGNMENT OF INTERVENTIONS → The resource must clock in/out. Without a valid clock-in, no interventions can be assigned to the resource.
Path Parameters
|
Field |
Note |
|---|---|
|
clockingTypeId |
|
Query String Parameters
Fields ℹ️
Default.
Header Parameters
Default.
Response documentation
Response payload fields
|
Field |
Note |
|---|---|
|
id |
|
|
description |
|
|
code |
|