Manage Missing Out Time Events

On Tuesday, the worker reports In but forgets to report Out. The time device automatically generates an Out event 6H after the reported In and a time device rule generates an exception on the time entry to be reviewed.

The following table shows the Time and Labor configuration that applies to this scenario.

Configuration	Purpose
Time device event mappings	Maps the supplier device events to the corresponding application events.
Time device rule based on the Validate Time Event Template template	Generates an Out event exception if the worker doesn't record an Out event within 6 hours of recording an In event. The event is automatically generated on the device.
Time device rule based on the Validate Schedule Deviation Template template	Validates the time entry against the worker's schedule.
Time submission rule	Saves the time card when the worker reports an Out event on Monday, Tuesday, Wednesday, Thursday, and Saturday. Submits the time card when the worker reports an Out event on Friday.

The following table describes the application processing actions that occur for the reported In time event.

Time Event	Application Processing
On Tuesday, the worker reports in at 9:00 AM.	Imports the In time event using the REST web service. Validates the imported time event using event mappings. Creates an incomplete time card entry for the In event. An exception is attached to the incomplete time card entry as the Out time event has not been received yet.
The worker forgets to report out at 5:00 PM.	Because the worker doesn't record an Out event within 14 hours of recording the In event: The time collection device automatically generates an Out event. The application: Imports the Out time event using the REST web service. Validates the imported time event using event mappings. Completes the earlier time card entry after receiving the Out event. Runs the time device rule, which validates the time events imported from the time device. Creates an Out time entry exception for the stop time to be reviewed. Runs the time submission rule, which initiates the save process. The time card is at this point in error status.

Example URL

The following is the format of the resource URL.

POST

/hcmRestApi/resources/11.13.18.05/timeEventRequests/

Example Request for the In Event

The following is an example of the request body in JSON format.

{
         "requestNumber": "20105",
         "sourceId": "HWM_CLOCK_TIME",
         "requestTimestamp": "2015-10-13T09:01:00.000+01:00",
         "timeEvents": [
            {
               "deviceId": "111",
               "eventDateTime": "2015-10-13T09:00:00.000+01:00",
               "SupplierDeviceEvent": "HWM_CLOCK_TIME_IN",
               "reporterId": "955160008184353",
               "reporterIdType": "PERSON",
"timeEventAttributes": [
                  {
                     "name": "PayrollTimeType",
                     "value": "Regular",
                  }
               ]
            }
         ]
      }

Example Response for the In Time Event

The following is an example of the response body in JSON format.

{
    "timeEventRequestId": 300100273290765,
    "requestNumber": "20105",
    "requestTimestamp": "2015-10-13T09:01:00.000+01:00",
    "sourceId": "HWM_CLOCK_TIME",
    "timeEvents": [
        {
            "timeEventId": 300100273290766,
            "timeEventRequestId": 300100273290765,
            "eventDateTime": "2015-10-13T09:00:00.000+01:00",
            "deviceId": "111",
            "supplierDeviceEvent": "HWM_CLOCK_TIME_IN",
            "reporterId": "955160008184353",
            "reporterIdType": "PERSON",
            "timeEventAttributes": [
                {
                    "timeEventAttributeId": 300100273290767,
                    "timeEventId": 300100273290766,
                    "name": "PayrollTimeType",
                    "value": "Regular",
                    "links": [
[...] 

Example Request for the Out Event

The following is an example of the request body in JSON format.

{
         "requestNumber": "20175",
         "sourceId": "HWM_CLOCK_TIME",
         "requestTimestamp": "2015-10-13T23:00:00.000+01:00",
         "timeEvents": [

            {
               "deviceId": "111",
               "eventDateTime": "2015-10-13T17:00:00.000+01:00",
               "supplierDeviceEvent": "HWM_CLOCK_TIME_AUTO_OUT",
               "reporterId": "955160008184353",
               "reporterIdType": "PERSON",
               "timeEventAttributes":
[
                  {
                     "name": "PayrollTimeType",
                     "value": "Regular",
                  }
               ]
            }
         ]
      }
	

Example Response for the Out Time Event

The following is an example of the response body in JSON format.

{
    "timeEventRequestId": 300100273290865,
    "requestNumber": "20175",
    "requestTimestamp": "2015-10-13T23:01:00.000+01:00",
    "sourceId": "HWM_CLOCK_TIME",
    "timeEvents": [
        {
            "timeEventId": 300100273290866,
            "timeEventRequestId": 300100273290865,
            "eventDateTime": "2015-10-13T23:00:00.000+01:00",
            "deviceId": "111",
            "supplierDeviceEvent": "HWM_CLOCK_TIME_AUTO_OUT",
            "reporterId": "955160008184353",
            "reporterIdType": "PERSON",
            "timeEventAttributes": [
                {
                    "timeEventAttributeId": 300100273290867,
                    "timeEventId": 300100273290866,
                    "name": "PayrollTimeType",
                    "value": "Regular",
                    "links": [
[...]