Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!

However, in addition, an AcceptEventAction with no incoming edges remains enabled after it accepts an Event occurrence.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Activity example: send and catch Signal
TIP: SysMLv1: Cameo Simulation Toolkit®: HOWTO handle receiving multiple Signal events in parallel within a repeated loop [with mini video]
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
SEMANTIC
UML keywords
AcceptEventAction
Activity
Event
If the AcceptEventAction has no incoming edges, by the usual rules, it is enabled when its immediately containing Activity (or StructuredActivityNode) begins execution.
Full quote
However, in addition, an AcceptEventAction with no incoming edges remains enabled after it accepts an Event occurrence.
Next snippet
That is, it does not terminate after accepting an Event occurrence and outputting any values (as described above), but continues to wait for another Event occurrence.
Related snippets
If an AcceptEventAction is used in an Activity, there are special rules for when it is enabled ..
Related snippets (backlinks)
Visit also
Visit also (backlinks)