A timer node is used within a process sequence. The process will get into a waiting situation when the timer node is reached. The process will continue when timer condition is TRUE.
The condition must result in a Date/time or Date condition which can end up TRUE
When Re-evaluation event is set to "On creation only", the timer node is set once it will not be re-evaluated at a change of the case domain. If the Re-evaluation event is set to "On domain change", the timer node will be updated and rescheduled in case the evaluated expression value has changed. Re-evaluation happens during the handling of domain updates.
When a timer node results in unknown at first initialisation (its condition evaluates to unknown), the timer will evaluate into TRUE. The process will continue in this situation.
At runtime, is possible to trace timer nodes: Process Traceability |
It is not advised to use a timer condition based on the values of NOW or TODAY. When the re-evaluation event "on domain change" is used, the date will be different at each domain change, and therefore changed at each domain change. This could lead to strange behaviour, like conditions which are never met. |
Re-evaluation of timer conditions only occurs when the case profile has been altered. When the process definition is changed, it will not re-evaluate automatically until the case profile has been changed somehow. Take this into account when publishing an altered process definition. |