-
Notifications
You must be signed in to change notification settings - Fork 0
Input values
Values can be passed into an activity with an input parameter designated with the ^ prefix. On a data flow diagram an input parameter appears as a data flow with no source.
next destination = ^Floor
If the above example is in a state activity, the Floor parameter packaged with the event that triggered the incoming transition is assigned to the scalar variable on the LHS.
Variable types that can be passed as input parameters depend on the type of activity as follows:
State activities: Table and scalar variables only (instance references are not guaranteed to be valid during the transmission of a signal).
All non-state activities: All variable categories
Since a class method is invoked either by a domain operation or a state activity, all instance references and model data should remain valid assuming the actions are sequenced as necessary.
There must be no space between the ^ symbol and the parameter name so that it is not interpreted as the intersection operator.
Copyright 2020, 2021, 2022, 2023, 2025 © Leon Starr under MIT Open Source License
- Why they are problematic
- Instance attribute creation values
- Boolean values
- Special values
- Enumerated values
- Action block
- Statement
- Single line action
- Multiple dependent actions on a single line
- An action spread across multiple lines
- A conditional group of single line actions
- Comments
- Finding instances
- Attribute access
- Creation and deletion
- Subclass migration
- Creating a table from a class
- Creating a table with a definition
- Converting a table into a class
- Set operations on tables
- Set comparisons on tables
- Join
- Rename
- Extend
- Aggregation
- Rank
- Image
- Input values
- Signatures and name doubling
- Output values
- Execution order
- Sequential execution
- Conditional execution
- Signals
- Scrall has no for_each action
- Iteration