.png)
The Clock In/Out screen has two buttons as follows:
These buttons are also present on the Task Tracking and Job Tracking screens when you use "Clock Mode". The text on these buttons can be changed by specifying the "in" and "out" options in the screen details. For example:
in=Start Shift, out=End Shift
The buttons can be further configured to allow you to collect data during your clock in and clock out events, using the following syntax:
in/out = <button>:<type>:<label>:<details>
where <button> is the button text, <type> is the type of data you want to capture , <label> is the name of the data field, and <details> are the type specific details.
While all data types can be used at either Clock In or Clock Out, the following data types are typically used at Clock In:
And the following data types are typically used at Clock Out:
Each of these data types is explained in detail below.
A data type of "dual" is used to capture values from two different lists, such as a project name and a work type. The "in" option should be configured with the following colon separated components:
For example:
in=Start Work:dual:Project:Work Type:Airport;Tower One;Naval Base:Design;Construction;Maintenance:Airport
If you are synchronising your users with a system that supports global lists, you can specify your list values by providing the appropriate list numbers. For example:
in=Start:dual:Project:Work Type:$1:$2
A data type of "nest" is used to capture values from two different lists, such as a project name and a work type, when the list of work types varies for each project. The "in" option should be configured with the following colon separated components:
Then, for each value in the first list, you separately define the values in the second list with the following colon separated components:
Each of the second lists is defined by the option "list1", "list2", etc, in the order of the options in the first list. For example:
in=Start Shift:nest:Project:Airport;Tower One;Naval Base,
list1=Work Type:Design;Construction;Maintenance,
list2=Work Type:Maintenance:Maintenance,
out=End Shift
Notice in this example that the Naval Base project does not have a corresponding list of Work Types, so it won't be necessary to select a Work Type for that project.
If you are synchronising your users with a system that supports global lists, and your list is hierarchical, you can specify your list values by providing the appropriate list number. For example:
in=Start Shift:nest:Work Type:$4
A data type of "tree" is used to capture values from a hierarchical list, such as a list of cost centers. Each level of the hierarchy is selected independently (one after the other), and searching is supported when a level has a large number of options. The "in" option should be configured with the following colon separated components:
Each level of the hierarchy is selected independently (one after the other). For example:
in=Start Work:tree:Project;Work Type:$1
A data type of "site" is used to capture a selection from a list, such as a work type, when the options vary by site. Employees do not need to select the site; it is determined automatically using their geolocation. This means that location capture must be set to either "Mapped" or "Fenced" in order to use site lists. The "in" option should be configured with the following colon separated components:
Then, for each site, you separately define the values in the list with the following colon separated components:
For example:
in=Start Shift:site,
Sydney=Work Type:Design;Construction;Maintenance,
Melbourne=Work Type:Design;Construction:Design,
Perth=Work Type:Maintenance:Maintenance,
out=End Shift
If you are synchronising your users with a system that supports global lists, and your list is hierarchical, you can specify your list values by providing the appropriate list number. For example:
in=Start Work:site:Work Type:$4
A data type of "type" is used to capture a selection from a list, such as a work type, when the options vary by user type. The "in" option should be configured with the following colon separated components:
Then, for each user type, you separately define the values in the list with the following colon separated components:
You can optionally specify a label and the list of options for all other user types at the end of your "in" option.
For example:
in=Start Work:type:Work Type:General,
Maintenance=Work Type:Fencing;Buildings;Machinery,
Farm Hand=Work Type:Ploughing;Planting;Picking;Other
In this example, users with a user type of Maintenance will get to select from: Fencing, Buildings, or Machinery; users with a user type of Farm Hand will get to select from: Ploughing, Planting, Picking, or Other, and users with any other user type will only have one option to select from: General.
A data type of "scan" is used to capture a value from a barcode or QR code. The "in" option should be configured with the following colon separated components:
Validation rules can be expressed as either:
The following types of alphanumeric barcode are supported:
For example, to capture 4 to 6 character job numbers, validated against a global list of job numbers, use:
For example:
in=Start Job:scan:Job Number:4:6:$1
A data type of "select" is used to capture two-option attestations at the end of a shift. The "out" option should be configured with the following colon separated components:
For example:
out=Clock Out:select:Shift Confirmation:Please confirm that you worked standard hours and that you took your required rest breaks. Otherwise please provide justification.:negative:Details:Standard Hours:Extra Time Worked:Rest Breaks Taken:Breaks Not Taken:none
A data type of "break" is used to capture the times of paid rest breaks at the end of a shift. The "out" option should be configured with the following colon separated components:
For example:
out=End Shift:break:true:10:4:2:8:6
A data type of "sentiment" is used to capture employee sentiment at the end of a shift. The "out" option should be configured with the following colon separated components:
For example:
out=Clock Out:sentiment:Clock Out:negative
A data type of "multi" is used to capture multiple selections from a list, such as shift conditions which drive additional payments. The "out" option should be configured with the following colon separated components:
For example:
out=End Work:multi:Conditions:Rain;Hail;Shine:1
A data type of "range" is used to capture a numeric value, such as the number of boxes packed during a shift. The "out" option should be configured with the following colon separated components:
For example:
out=End Work:range:Boxes:1:100:1:25
A data type of "dollar" is used to capture a dollar amount, such as tips, at the end of a shift. The "out" option should be configured with the following colon separated components:
For example:
out=End Shift:dollar:Tips:0:10:true
You can restrict which users are required to enter data by specifying either the "intype" or "outtype" option in the screen details as appropriate. For example, to require that users with a user type of "Supervisor" must select a project during clock in, you would specify:
in=Start:list:Project:Airport;Tower One;Naval Base:Tower One, intype=Supervisor
All other users can clock in just by pressing the "Clock In" button.
Similarly, to require that users with a user type of "Driver" or "Packer" must enter the number of boxes processed during clock out, you would specify:
out=Done:range:Boxes:0:100:1, outtype=Driver;Packer
All other users can clock out just by pressing the "Clock Out" button.
