Page History

...

• Can have a precondition: a precondition is used to infer if a task must become active. An expression can be used to create the precondition. It is needed to model a precondition on each adhoc task (if there is no need for a precondition, use TRUE).

• Can be required: an adhoc task can be made required by a condition which can be TRUE or an expression. If an adhoc task is required it must be finished before finishing a case (A case will not be finished when there is an open required task when reaching an end node). The pre-condition has a higher priority, so an adhoc task will only be required when the precondition is TRUE.

• Can be made repeatable: an adhoc task can be made repeatable so the task can be executed more than one time within a case. After finishing this task a new instance of this task will be opened. Only one instance of each task type can be active (status open)

• Can not be automated

• Case locking can be applied: when case locking is TRUE, the case will be locked and all other tasks within the case can not be executed when this task is executed.

• Can have privileges: privileges can be used to restrict users to perform tasks.

• Has events: process events are used for the mapping of processes to an implementation flow.

...

An adhoc process functions equally as the the sub-process

...

...

• Name: Autogenerated ID for the node. It can be edited but must be unique within the process module to function.

• Condition: A condition which has to evaluate to a Date or Date/Time value. If the Date is TRUE the event is caught and it will start flowing from that point. The profile of the process/case will be used for the evaluation. The node will be (re)evaluated at each change of the profile of the process/case. At evaluation a date or Date/time will be set and the event will start flowing when the moment arrives

• Repeatable: An Adhoc Timer event can be made repeatable, after evaluating the date or Date/time value to TRUE a new Date/DateTime will be set.

...