Transitions

Copyright © Cloud Software Group, Inc. All Rights Reserved

Transitions

Transitions describe the flow of processing in a process definition. A transition is represented by an arrow between two activities. The arrows are unidirectional, and you cannot draw a transition to a previously executed activity. Control flow in a process definition must proceed sequentially beginning with the Start activity (or a process starter) and ending with the End activity.

A transition can optionally specify a condition. The condition determines if the transition is taken when an activity completes processing. After an activity completes, all transitions whose conditions are met are taken. You can have transitions from one activity to many other activities. Therefore, you can have several branches of activity processing in your diagram.

Having multiple branches in a process definition does not imply that each branch is processed concurrently. Transitions describe control flow of the process definition, not the concurrency of execution of activities. Process execution is controlled by the process engine. See TIBCO ActiveMatrix BusinessWorks Administration for more information about configuring the TIBCO ActiveMatrix BusinessWorks process engine.

Each activity in a process definition must have a transition to it, or the activity is not executed when the process executes.

Chapter 5, Transitions and Conditions describes transitions and conditions.