Task preconditions
For manual and automatic tasks, you can specify preconditions that must be met before the task is ready to start. Tasks can start automatically after all preconditions are met or manually by a user after all preconditions are met.
If the preconditions for a task are not fully satisfied and if the task has a trigger, such as a case property is updated or a document is filed, the task remains in waiting state until the next trigger occurs to reevaluate the preconditions.
A task with preconditions is complete after all of the preconditions are met, but will not start until the trigger you defined has all of the preconditions met, such as when a second document is added.
- No precondition, start task
- A task can have no preconditions, that is, no precondition must be met for this task to start.
- A property condition is met
- You can design a task that starts only if the conditions are met.
You specify the conditions by building expressions that contain case
properties. For example, you can build a property expression that
contains the following conditions: one of the case properties must
equal a value, a second property value must be true, and a third property
must begin with a value before the task can begin.
You can join the conditions by using the Boolean ALL or ANY operators.
The operators in the expression change depending on the property type.
- A case property is updated
- You can design a task to start only when one or more case properties
are updated.
Optionally, you can specify additional property conditions. If you specify additional property conditions, the property conditions must also be met for a task to start.
You can also mark the task as repeatable when the precondition is satisfied.
- A document is filed in the case
- You can design a task to start only when documents of one or more
document types from the choice list are added to the case folder.
Or you can design a task to start when documents of any document type
are added to the case folder.
Optionally, you can specify additional property conditions. If you specify additional property conditions, the conditions must also be met for a task to start.
You can mark the task as repeatable, to repeat when the precondition is satisfied. For example, if your task is to review an automobile accident claim estimate, you can define the task is repeatable. A new task will be created and work added to the in-basket of the case worker that reviews the claim estimate each time that a repair estimate document is added to the case.
You can update the preconditions for a task at any time, including on deployed solutions. If you change the expression of a property condition for a deployed solution, for task types that have the A property condition is met precondition, run the precondition checker utility after you redeploy the solution.
