How to model optional tasks in jBPM 3?
Issue
How do I model an jPDL <task> to be optional?
Say I have 3 tasks in a task-node, named "task-1", "task-2" and "task-3". Only "task-1" and "task-2" has to be finished before the token shall continue - even if "task-3" isn't finished. "task-3" should though not appear in any user task list after that (automatically ended?)
How can I combine the "blocking" and "signalling" attributes of the task element to achieve this?
Environment
- jBPM 3.2.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.