Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content UML2 Types of Pins - metaclasses 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 Activity Activity Diagram Action Pin InputPin ValuePin ValueSpecification ValuePin::value Previous snippet ValuePins and ActionInputPins are InputPins, but are not used in the determination of whether an Action is enabled for execution. If an Action has no other way to start execution, simply having ValuePins or ActionInputPins for its inputs will not enable.. Full quote A ValuePin provides a value by evaluating a ValueSpecification (e.g., this may be used as a simple way to specify constant inputs to an Action.) When the Action is enabled by other means, the ValueSpecifiation of the ValuePin is evaluated, and the result is provided as an input to the Action when it begins execution. Next snippet Related snippets An OutputPin is a Pin that holds output values produced by an Action. For each execution, an Action cannot terminate itself unless it can put at least as many values into its outputs as required by the multiplicity lower bounds on those OutputPins. Values that may remain on the OutputPins from previous executions are not... An Action may not put more values into an output in a single execution than the [upper] multiplicity of that OutputPin. An Action may accept inputs and produce outputs, as specified by InputPins and OutputPins of the Action, respectively. Each Pin on an Action specifies the type and multiplicity for a specific input or output of that Action. Action::/input : InputPin [0..*] ... The ordered set of InputPins representing the inputs to the Action. An InputPin is a Pin that holds input values to be consumed by its Action. The upper multiplicity determines the maximum number of values that can be consumed from an InputPin by a single execution of its Action. Tokens consumed by an Action are immediately removed from its InputPins when the action begins an execution (except in some cases for StructuredActivityNodes, where tokens may remain on InputPins during the Action execution ...) ValuePins and ActionInputPins are InputPins, but are not used in the determination of whether an Action is enabled for execution. If an Action has no other way to start execution, simply having ValuePins or ActionInputPins for its inputs will not enable.. Related snippets (backlinks) Visit also Visit also (backlinks) Flags
