A complex activity is made of atomic activities. Complex activities can end normally, after a timeout event, or after a fault event. The complex activity catches exception events (exception, compensation, or timeout) by using exception handlers, compensation handler and timeout handler.
In Sybase WorkSpace Business Process, a complex activity defines a sub-process element that includes context variables: one default exception handler and optionally one handler per fault, one compensation handler, and several timeout handlers. These handlers are complex activities executed when the corresponding event happens.
|
Sybase WorkSpace Business Process concept |
PowerDesigner concept |
|---|---|
|
Complex activity |
Composite process. If you want to visualize the atomic activities of the complex activity you have to open the composite process sub-diagram. |
|
Timer |
Event with <<Timer>> stereotype. To associate a timer event to a composite process you have to attach events to flows coming from the composite process. |
Complex activity exits are designed as flows outgoing from the composite process:
If you right-click the composite process, you can see different menu commands for creating these exits: Add Compensation Handler, Add Exception Handler, Add Timeout Handler, and Add Default Exception Handler.