# NotifyActionExpressionType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/model/scripting-3

Supertype: ActionExpressionType
Statically-typed "notify" action.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
type | property string | [0,1] | Action to execute.
parameter | property ActionParameterValueType | [0,-1] | Action parameters.
subtype | property string | [0,1] | Subtype of the event created: Free-text information about category (type) of this custom event.
operation | property EventOperationType | [0,1] | Operation to be put into event (add, modify, delete).
status | property EventStatusType | [0,1] | Status to be put into event (success, failure, inProgress, alsoSuccess, onlyFailure).
handler | container EventHandlerType | [0,1] | Ad-hoc event handler that should be used to process the event.
forWholeInput | property boolean | [0,1] | Whole input (i.

- ### Items

  - #### type

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Action to execute.

  - #### parameter

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Action parameters.

  - #### subtype

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Subtype of the event created: Free-text information about category (type) of this custom event.

  - #### operation

    Flags: RAM,runtime,AVals:3

    Multiplicity: [0,1]

    Display order:

    Operation to be put into event (add, modify, delete). Default is "add".

  - #### status

    Flags: RAM,runtime,AVals:5

    Multiplicity: [0,1]

    Display order:

    Status to be put into event (success, failure, inProgress, alsoSuccess, onlyFailure). Default is "success".

  - #### handler

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Ad-hoc event handler that should be used to process the event. If not specified, system configuration is used to determine the handler(s).

  - #### forWholeInput

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Whole input (i.e. all items in the pipeline) should be sent as event object. The default behavior is to generate one event for each input object.