-
Notifications
You must be signed in to change notification settings - Fork 1
Internal Transition
Internal Transition is the way to consume an Event within State without changing current State.
Internal Transitions are not causing State to exit and enter again - if their Guard evaluates to true, their Effect is executed and that completes Event consumption.
Internal Transition consist of:
- Source State,
- Guard, a predicate logic (that returns boolean value) that is evaluated in order to check if Transition can happen or not,
- Effect, logic that is executed when Transition is happening.
In UML, Internal Transition is represented by textual description within the boundary of State:
stateDiagram-v2
SomeState: SomeState<br/>Trigger [Guard] / Effect
Equivalent Stateflows notation of Internal Transition:
/* fragment of State Machine definition */
.AddState("SomeState", b => b
.AddInternalTransition(b => b
.AddGuard(async c => true /* bool-returning logic here */)
.AddEffect(async c => /* logic here */)
)
)Using lambda style here means that States are referred by string name and each bit of Transition logic is implemented as lambda function passed as parameters to
Add*methods in Transition definition.
public class SomeState : IState
{ }
public class MyInternalTransition : ITransitionGuard<Trigger>, ITransitionEffect<Trigger>
{
public Task<bool> GuardAsync(Trigger @event)
{
/* bool-returning logic here */
return true;
}
public Task EffectAsync(Trigger @event)
{
/* logic here */
}
}
/* fragment of State Machine definition */
.AddState<SomeState>(b => b
.AddInternalTransition<MyInternalTransition>()
)Using typed style here means that States and Transitions are classes that is referenced in typed overloads of
Add*methods in State Machine definition.
Class can be used as Internal Transition if it implements at least one interface from ITransition*<TEvent> family:
-
ITransition<TEvent>- simply represents Transition, -
ITransitionGuard<TEvent>- represents Transition with Guard logic implemented asGuardAsync()method, -
ITransitionEffect<TEvent>- represents Transition with Effect logic implemented asEffectAsync()method, -
ITransitionDefinition<TEvent>- represents Transition with additionalBuild()method that allows to extend its definition, for example to define Guards and Effects in Transition class.
Note: interfaces for typed versions of regular Transitions and Internal Transitions are the same.
Transition logic may also be split into several classes like in the example:
public class SomeState : IState
{ }
public class MyInternalGuard : ITransitionGuard<Trigger>
{
public Task<bool> GuardAsync(Trigger @event)
{
/* bool-returning logic here */
return true;
}
}
public class MyDefaultEffect : ITransitionEffect<Trigger>
{
public Task EffectAsync(Trigger @event)
{
/* logic here */
}
}
/* fragment of State Machine definition */
.AddState<SomeState>(b => b
.AddInternalTransition(b => b
.AddGuard<MyInternalGuard>()
.AddEffect<MyInternalEffect>()
)
)
.AddState<AnotherState>()This technique enables reusing of Internal Transition's logic.
If Internal Transition logic does not rely on Trigger Event data and is suitable to be reused in other Transitions, Internal Transition classes may be created by implementing at least one interface from ITransition* family:
-
ITransitionGuard- represents Transition with Guard logic implemented asGuardAsync()method, -
ITransitionEffect- represents Transition with Effect logic implemented asEffectAsync()method, -
ITransitionDefinition- represents Transition with additionalBuild()method that allows to extend its definition, for example to define Guards and Effects in Transition class.
Such classes are called Generic Transitions and may be used to declare all types of Transitions.
Home page Support Code licensed under an MIT-style License. Documentation licensed under CC BY 4.0. © by Mikołaj Milewski, 2025
Overview
Installation
Behaviors
State Machines
Building blocks
States
State
Composite State
Orthogonal State
Final State
Pseudostates
Choice
Junction
Fork
Join
Transitions
Transition
Default Transition
Internal Transition
Concepts
Evaluation of Transitions
Activities
Building blocks
Nodes
Action Node
Decision Node
Merge Node
Initial Node
Final Node
Input Node
Output Node
Fork Node
Join Node
Accept Event Action Node
Send Event Action Node
Data Store Node
Structured Activity Node
Iterative Activity Node
Parallel Activity Node
Flows
Data Flow
Control Flow
Concepts
Implicit fork and join
Actions