Page History
...
Function | Arguments | Default | Explanation |
---|---|---|---|
isStarted | startedFrom, startedTo, count | startedFrom=0d, startedTo=0d, count=1 |
|
isCompleted | startedFrom, startedTo, completedFrom, completedTo, count | completedFrom=0d, completedTo=0d, count=1 |
|
isCompletedSuccessful | startedFrom, startedTo, completedFrom, completedTo, count | completedFrom=0d, completedTo=0d, count=1 |
|
isCompletedFailed | startedFrom, startedTo, completedFrom, completedTo, count | completedFrom=0d, completedTo=0d, count=1 |
|
lastCompletedSuccessful | startedFrom, startedTo, completedFrom, completedTo, count | completedFrom=0d, completedTo=0d, count=1 |
|
lastCompletedFailed | startedFrom, startedTo, completedFrom, completedTo, count | completedFrom=0d, completedTo=0d, count=1 |
|
Arguments
Argument | Default | Explanation |
---|---|---|
startedFrom | 0d | The workflow or job started after the given date. |
startedTo | 0d | The workflow or job started before the given date. |
completedFrom | 0d | The workflow or job completed after the given date. |
completedTo | 0d | The workflow or job completed before the given date. |
count | count |
=1 | The |
number of history items that is expected to be returned for the given period. By default a single history item is expected ( |
not correspond to the number of history items returned. Values for operator: =, <=, <, >, >= Example count > 10 ==> The CheckHistoryJob will fail if the number of history entries is not greater then 10 |
Absolute Dates
Absolute date can be specified as values to the startedFrom
, startedTo
, completedFrom
and completedTo
arguments.
...
Overview
Content Tools