Listing of input and output data.
The data that the Clocking Event 2.0 | HCM uses can be divided into input data and output data. That is, the data that is imported and the data that is exported by the app.
Input
So the app works correctly, some input data is required.
| Data | Usage |
|---|---|
| CPF | It is the employee's legal identifier, used to display on the clocking event receipt |
| PIS (Social Integration Plan) | It is also a legal identifier of the employee, used to be displayed on the clocking event receipt. |
| Name | Employee's identifier, used to present on the clocking event receipt and on the app screens. |
| Email address | Another way to identify the employee. |
| External ID | Identifier used if the data were imported from another system. |
| Registration Number | Employee registration number. |
| Employee Type | Defines the type of employee (Employee, Third Party and Partner). |
| Platform user | Used to link platform users with employee information. |
| Managers | Identifies who the employee's managers are. |
| Company | Company information, business unit or branch to which the employee is linked. |
| Data | Usage |
|---|---|
| Email address | Used to identify the manager. |
| Platform users | Used to link platform users with manager information. |
| Data | Usage |
|---|---|
| CNPJ | Used to present in the clocking event receipt. |
| Name | Used to present in the clocking event receipt. |
| Data | Usage |
|---|---|
| User's name | Used to identify platform user authentication and link with managers and employees. |
Output
Output data is generated for tracking and efficient management of employee information.
| Data | Usage |
|---|---|
| Date | The date collected in the application to register the employee's clocking event. |
| Time | The date collected in the application to register the employee's clocking event. |
| CNPJ | Employee information at the time of the clocking event. |
| PIS (Social Integration Plan) | Employee information at the time of the clocking event. |
| Device | Device on which the clocking event was made. |
| Geolocation | The geolocation collected in the app at the time of the clocking event register. |
| Employee | The employee who performed the clocking even. |
| Usage | Clocking event usage information, to determine the type of clocking event. |
| Virtual perimeter status | Information on whether the clocking event was made inside or outside the virtual perimeter determined for the employee. |
Controls whether or not the device can be used for clocking events.
| Data | Usage |
|---|---|
| Situation | Situation in which the device activation is (pending, authorized or rejected). |
| Device | Device on which activation is being applied. |
| Employee | Employee who requested activation. |
| Request date | Date on which activation was requested. |
| Requisition code | Time when activation was requested. |
| Date of change | Date on which the request undergoes a status change. |
| Time of change | Time at which the request undergoes a status change. |
| Data | Usage |
|---|---|
| Name | Device name collected from the device the employee uses. |
| Model | Model name collected from the device the employee uses. |
| Device ID | Device IMEI collected from the device the employee uses. |
Clocking event location information.
| Data | Usage |
|---|---|
| Latitude | Location latitude. |
| Longitude | Location Longitude. |
Perimeter grouping.
| Data | Usage |
|---|---|
| Name | The name of the virtual perimeter that will group the locations, later used in the application to determine the locations that the employee must make his clocking events. |
Location control.
| Data | Usage |
|---|---|
| Radius | Radius that will be used to determine where the employee can make the clocking events. |
| Data | Usage |
|---|---|
| Date | Date the overnight was registered. |
| Geolocation | Geolocation used at the time of register. |
| Employee | Employee who overnighted. |

English
Español


