Progression Design – Completing an Exception Task

Although the Default Exception Task for your Process is automatically generated as a specialized Manual task, you should typically ensure that users of the process that originated the exception are notified. 

The Default Exception Task is “Unconnected” to the individual tasks in the process where all processing failures go on an event-driven basis.

Additional Exception Tasks that have been added to your Process need to be connected to the intended pinout exception paths.   These Exception tasks are “Connected” explicitly to specific task pinout conditions and server primarily to raise the priority of an item to a critical state.

For example a connected exception could be used to alert selected manager(s) of a missing signature on a large order that must go out immediately.