The Timeliness Check node is used to check whether the amount of time between two fields surpasses an acceptable level. The node produces a new field containing Boolean values for each timeliness check that is written. If the difference between the two chosen fields is less than or equal to the acceptable interval, the record is considered timely and a True
value is returned. Conversely, if the difference between the two chosen fields is greater than the acceptable interval, the record is not considered timely and a False
value is returned.
Properties
Check Result Field Name
This is the name of the Boolean field the node will produce for the Timeliness Check.
Start Time Field
This is the field containing start dates to be used in the Timeliness Check. Only Date, DateTime, or Time fields can be used.
End Time Field
This is the field containing end dates to be used in the Timeliness Check. Only Date, DateTime, or Time fields can be used.
Allowed Time Difference
This is the acceptable difference between the Start Time Field and the End Time Field to check for. If the difference between the Start Time Field and the End Time Field is less than or equal to the Allowed Time Difference, the Timeliness Check will return True; otherwise, it will return False.
Timeliness Check Example
You have the following data set:
orderDate |
shipDate |
---|---|
08/08/2017 |
08/10/2017 |
08/09/2017 |
08/12/2017 |
08/10/2017 |
08/14/2017 |
For this data set, we could define a timeliness check with a Check Result Field Name of ShippedOnTime.
For the Start Time Field we could use orderDate,
and for the End Time Field we could use shipDate.
For the Allowed Time Difference we could set an interval of three days, to check whether an order has shipped within three days of being placed.
The result set would be as follows:
orderDate |
shipDate |
ShippedOnTime |
---|---|---|
08/08/2017 |
08/10/2017 |
True |
08/09/2017 |
08/12/2017 |
True |
08/10/2017 |
08/14/2017 |
False |
Note that, as with other Data Quality check nodes, multiple timeliness checks may be written per Timeliness Check node.