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 .

Conditional Start Tool

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

Where each state represents the following:

1. 1. • Created : the process activity is being initialized;

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 .

1. 1. • Listening : the process activity is listening for incoming events to execute the flow. Each time the expected event occurs a new flow execution is started.

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:

1. 1. • Created : the process activity is being initialized;

      • Scheduled : if the Human Activity has a date set in its Start Date property, it waits until that date before going to the Ready state;

      • Ready : the Human Activity is displayed in the end-users' Taskbox .

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 ;

1. 1. • Open : an end-user has opened the human activity in its Taskbox and is executing it.

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 ;

1. 1. • Closing : the Human Activity task was closed. However, the Human Activity cannot be closed yet because the process execution is suspended;

      • Closed : the Human Activity was closed and its execution ended.

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:

1. 1. • Created : the Send Email is being initialized;

      • Executing : the Email content is being rendered and sent;

      • Closing : the Email was sent. However, the Send Email execution cannot be ended yet because the process execution is suspended;

      • Closed : the Email was sent and the Send Email execution has ended.

Automatic Activity Tool

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

Where each state represents the following:

1. 1. • Created : the Automatic Activity is being initialized;

      • Scheduled : if the Automatic Activity has a date set in its Start Date property, it waits until that date before executing its action flow;

      • Executing : the Automatic Activity action flow is being executed;

      • Closing : the Automatic Activity action flow execution is ended. However, the Automatic Activity execution cannot be ended yet because the process execution is suspended;

      • Closed : the Automatic Activity action flow execution is ended, along with the Automatic Activity execution.

Execute Process Tool

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

Where each state represents the following:

1. 1. • Created : the Execute Process activity is being initialized;

      • Waiting : the process is being executed;

      • Closing : the execution of the process has ended. However, the Execute Process activity execution cannot be ended yet because the process execution is suspended;

      • Closed : the execution of the process has ended, along with the Execute Process activity execution.

Wait Tool

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

Where each state represents the following:

1. 1. • Created : the Wait activity is being initialized;

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 ;

1. 1. • Waiting : the Wait activity is waiting for its expected event to occur;

      • Closing : the waiting is ended. However, the Wait activity execution cannot be ended yet because the process execution is suspended;

      • Closed : the waiting is ended, along with the Wait activity execution.

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 .

Decision Tool

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

Where each state represents the following:

1. 1. • Created : the Decision activity is being initialized;

      • Executing : the Decision flow is being executed;

      • Closing : the Decision flow execution is ended. However, the Decision activity execution cannot be ended yet because the process execution is suspended;

      • Closed : the Decision flow execution is ended, along with the Decision activity execution.

See Also

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