Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content UML Event types for triggering Transitions uml101 - StateMachines - NOTATION REFERENCE CARD 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 Event MessageEvent CallEvent Trigger Trigger::event Message Operation object CallEvent::operation Previous snippet Full quote A CallEvent models the receipt by an object of a message invoking a call of an Operation. Next snippet Related snippets An Event is the specification of some occurrence that may potentially trigger effects by an object. A MessageEvent specifies the receipt by an object of either an Operation call or a Signal instance. A trigger for an AnyReceiveEvent is triggered by the receipt of any message that is not explicitly handled by any related trigger. A CallEvent is denoted by the name of the triggering Operation, optionally followed by an assignment specification: <call-event> ::= <name> [‘(‘ [<assignment-specification>] ‘)’] <assignment-specification> ::= <assigned-name> [‘,’ <assigned-name>]* NOTE. Operation referenced in the CallEvent of an AcceptCallAction should not have an associated method Behavior. Otherwise, a call to the Operation will have the immediate effect of executing the method and will not be placed into the event pool ... If the triggers of an AcceptEventAction are all for ChangeEvents and/or CallEvents, then the AcceptEventAction has no result OutputPins (unless the AcceptEventAction is an AcceptCallAction ...) Related snippets (backlinks) A SignalEvent represents the receipt of an asynchronous Signal instance. Visit also Visit also (backlinks) Flags
