When a process instance is executed, it follows its flow path, creating and executing instances for each process activity found along the way. The execution of a process activity instance follows its own life cycle, which is defined by the process flow tool you used to create it. Once the process activity execution ends, the process follows on to the next activities in the flow path.

Some process activities allow you to add business rules to validate the transition to a certain stage in their life cycle. Learn more about Process Activities Callback Actions.

See the life cycle of:

Conditional Start Tool

Each process activity created with the Conditional Start Tool has the following life cycle:

Where each state represents the following:

Use On Ready action to add business rules to set up the Conditional Start before it initiates the event listening. Learn more about On Ready action.

Use On Start action to add business rules to validate whether the Conditional Start can start the execution of its flow. Learn more about On Start action.

Human Activity Tool

Each process activity created with the Human Activity Tool has the following life cycle:

Where each state represents the following:

Use On Ready action to add business rules to validate whether the Human Activity can be displayed in the Taskbox. Learn more about On Ready action;

Use On Open action to add business rules to validate whether the Human Activity can be opened by the end-user in the Taskbox. Learn more about On Open action;

Use On Close or On Skip actions to add business rules to validate whether the Human Activity can be closed, i.e., can end its execution. Learn more about On Close action and On Skip action.

Send Email Tool

Each process activity created with the Send Email Tool has the following life cycle:

Where each state represents the following:  

Automatic Activity Tool

Each process activity created with the Automatic Activity Tool has the following life cycle:

Where each state represents the following:  

Execute Process Tool

Each process activity created with the Execute Process Tool has the following life cycle:

Where each state represents the following:

Wait Tool

Each process activity created with the Wait Tool has the following life cycle:

Where each state represents the following:

Use On Ready action to add business rules to validate whether the Wait Activity can start its waiting activity. Learn more about On Ready action;

Use On Close or On Skip actions to add business rules to validate whether the Wait activity can be closed, i.e., can end its execution. Learn more about On Close action and On Skip action.

Decision Tool

Each process activity created with the Decision Tool has the following life cycle:

Where each state represents the following:

See Also

Designing Processes | Process Flow Editor | Process Flow Toolbox | Process Activities Callback Actions