Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

Tokens arriving at a control InputPin have the same semantics as control tokens arriving at the Action, except that control tokens can be buffered in control Pins.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Starting an Action that has a ControlPin
Starting an Action that has a ValuePin - LIMITED SUPPORT
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
InputPin
control Pin
Pin::isControl
ObjectNode::isControlType
control token
Action
Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...).
Full quote
Tokens arriving at a control InputPin have the same semantics as control tokens arriving at the Action, except that control tokens can be buffered in control Pins.
Next snippet
Tokens are placed on control OutputPins according to the same semantics as tokens placed on ControlFlows coming out of an Actions.
Related snippets
A ControlFlow is an ActivityEdge traversed by control tokens or object tokens of control type, which are use to control the execution of ExecutableNodes
ObjectNode::isControlType : Boolean [1..1] = false Indicates whether the type of the ObjectNode is to be treated as representing control values that may traverse ControlFlows.
If isControlType=true for an ObjectNode, ControlFlows may be incoming to and outgoing from the ObjectNode, objects tokens can come into or go out of the ObjectNode along ControlFlows, and these tokens can flow along ControlFlows reached downstream ...
isControl : Boolean [1..1] = false Indicates whether the Pin provides data to the Action or just controls how the Action executes.
object_nodes ControlFlows may not have ObjectNodes at either end, except for ObjectNodes with control type.
A control Pin (with isControl=true) must have a control type (isControlType=true), so that they may be used with ControlFlows.
Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...).
Control Pins are shown with the textual annotation {control} placed near the Pin symbol.
Related snippets (backlinks)
Tokens are placed on control OutputPins according to the same semantics as tokens placed on ControlFlows coming out of an Actions.
Visit also
Visit also (backlinks)