Do you really need conditions in YAWL workflows?

Printer-friendly version

Many of the YAWL workflows consist of only tasks and the special input and output conditions. Are conditions merely a remainder of the Petri net origins of YAWL or are they really useful? The answer is: they are useful. You can model workflows where the user can start one of many offered alternative workitems and the others are withdrawn from the worklist (see also the following article).