A transition is a true-false test, evaluated during activity execution, that determines whether the flow of control in an activity continues with the next numbered step.
A transition is a reference to a when condition (Rule-Obj-When rule type) or an expression that evaluates to True or False. After the method referenced in an activity step executes, but before processing continues with the next numbered step, the system evaluates the when condition or expression. The resulting value (True or False) can cause the activity execution to continue, end, or continue at a higher-numbered step.
On the activity form Steps tab, the
icon identifies the
transition column. When a row is not selected, a
indicates that this step has a transition defined. When the row
is activated, click
to add a transition or the
to
access the details of the transition.
TURBT 1/21/02 When a method in an
activity step affects the value of a property computed by a Declare
Expression rule, the declarative rule execution occurs before the
system evaluates the transition. For example, if the method updates the
value of a Diameter property, and a Declare Expression rule computes a
CircleArea property from Diameter, only the updated CircleArea value is
available to the transition.
The transition phase is the final phase in the Pegasystems Implementation Methodology, during which the application is placed into production use with the appropriate IT infrastructure.
![]() |
activity, implementation methodology, precondition |
![]() |
Activity
form — Completing the Steps tab — Transitions How to test method results using a transition |