Delete Action

One or more instances of a single Class may be deleted using a single delete action.

Just like creation, deletion may be local (synchronous) or delegated (asynchronous). Only the local variation specifies an explicit Deletion Action.

In the local case, the Deletion Action is specified in a Lifecycle Activity, Method or External Entity Operation.

The action takes a set of instance references as input and deletes them. The empty set input does not trigger any error, but a non-existent instance (prior to attempted deletion) will.

In the delegated case, an event that causes a transition into a deletion state is dispatched to a target instance. If that instance is in a state where it can respond to this event with a transition into one of its deletion states, the instance will execute the final activity in that state and then implicitly trigger the MX deletion accessor. Since this happens automatically, the modeler does not specify the Deletion Action. Deletion happens automatically.