The Conditional Activity helps you centralize different paths of the process into one activity and re-distribute the instances based on conditional transitions.
The following table outlines some of the considerations when using the Conditional Activity within ALBPM Studio.
| WorkSpace | Conditional activities do not appear in WorkSpace because the Conditional activity does not require any end user intervention. |
| Roles | Conditional activities can appear in either automatic roles or the user defined role types. However, if the Conditional activity is in a user-defined role, it will not appear in WorkSpace. |
| Variables | No variables are available. |
| Pre Conditions | The Conditional activity is activated by an incoming instance from another activity in the process. |
| Post Conditions | The instance flows to the next activity in the process according to transition rules. |
| Transitions | One or more incoming and outgoing transitions are required. Only Unconditional and Conditional transitions are available. |
| Tasks | No tasks are available. |
| Business Process Methods | No tasks are available. |