# RegistrationConfirmationNotifierType (Complex Type)

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

Supertype: ConfirmationNotifierType
TODO

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
name | property string | [0,1] | Symbolic name, used either as a comment or (in the future) maybe to reference the filter.
description | property string | [0,1] | A note about the notifier and its filters, e.
documentation | property string | [0,1] | Technical documentation for a particular object or construct.
category | property EventCategoryType | [0,-1] | Event categories supported by this handler.
operation | property EventOperationType | [0,-1] | Operations supported by this handler.
status | property EventStatusType | [0,-1] | Result statuses supported by this handler.
objectKind | property ShadowKindType | [0,-1] | Resource object kinds supported by this handler.
objectIntent | property string | [0,-1] | Resource object intents supported by this handler.
focusType | property QName | [0,-1] | Focus types supported by this handler.
expressionFilter | property ExpressionType | [0,-1] | Expression that returns true (if the event is to be processed and passed further) or false (if it has to be thrown off).
fromExpression | property ExpressionType | [0,1] | from address overwrites notificationConfiguration/mail/defaultFrom
recipientExpression | property ExpressionType | [0,-1] | Recipient(s) that should get the notifications.
ccExpression | property ExpressionType | [0,-1] | cc Recipient(s) that should get the notifications.
bccExpression | property ExpressionType | [0,-1] | bcc Recipient(s) that should get the notifications.
messageTemplateRef | reference ObjectReferenceType | [0,1] | Reference to the message template that produces the content of the message.
subjectExpression | property ExpressionType | [0,1] | How to construct the subject of the message that is to be sent.
subjectPrefix | property string | [0,1] | Simpler alternative to subjectExpression: the subject itself will be constructed by the notifier, but it will be prefixed by value specified here.
bodyExpression | property ExpressionType | [0,1] | How to construct the body (text) of the message that is to be sent.
contentType | property string | [0,1] | Body content type, e.
contentTypeExpression | property ExpressionType | [0,1] | Body content type, e.
attachment | property NotificationMessageAttachmentType | [0,-1] | Message attachment(s) to be sent out.
attachmentExpression | property ExpressionType | [0,1] | An expression that returns message attachment(s) to be sent out.
watchAuxiliaryAttributes | property boolean | [0,1] | Whether to send a notification when only auxiliary attributes (namely: validityStatus, validityChangeTimestamp, effectiveStatus, disableTimestamp, modifyChannel, modifyTimestamp, modifierRef and maybe others) are modified.
showModifiedValues | property boolean | [0,1] | Whether to show modified values (or only names of changed attributes).
showTechnicalInformation | property boolean | [0,1] | Whether to show technical information (e.
transport | property string | [0,-1] |
notificationSendingStrategy | property NotificationSendingStrategyType | [0,1] | How to send notification to individual recipients, e.
confirmationMethod | property RegistrationConfirmationMethodType | [0,1] |

- ### Items

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Symbolic name, used either as a comment or (in the future) maybe to reference the filter.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    A note about the notifier and its filters, e.g. for the administrator.

  - #### documentation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Technical documentation for a particular object or construct.

    The purpose of this element is to document system configuration and behavior. The documentation will not be presented to end users. In fact, it will probably not be presented at all in midPoint user interface. This documentation element is supposed to be a part of the technical documentation of midPoint deployment. The tools than generate deployment configuration will look for these elements and combine them to compiled documentation document.

    AsciiDoc formatting is assumed for this element. Any leading or trailing whitespace is skipped. Indentation equivalent to he indentation of the first non-blank line of text is also skipped.

  - #### category

    Flags: RAM,runtime,AVals:18

    Multiplicity: [0,-1]

    Display order:

    Event categories supported by this handler. (Default: all) Categories not listed are filtered out: not handled by this handler nor any of its successors.

  - #### operation

    Flags: RAM,runtime,AVals:3

    Multiplicity: [0,-1]

    Display order:

    Operations supported by this handler. (Default: all) Operations not listed are filtered out: not handled by this handler nor any of its successors.

  - #### status

    Flags: RAM,runtime,AVals:5

    Multiplicity: [0,-1]

    Display order:

    Result statuses supported by this handler. (Default: all) Statuses not listed are filtered out: not handled by this handler nor any of its successors.

  - #### objectKind

    Flags: RAM,runtime,AVals:4

    Multiplicity: [0,-1]

    Display order:

    Resource object kinds supported by this handler. (Default: all) Kinds not listed are filtered out: not handled by this handler nor any of its successors. (Relevant only for account-related events.)

  - #### objectIntent

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Resource object intents supported by this handler. (Default: all) Intents not listed are filtered out: not handled by this handler nor any of its successors. (Relevant only for account-related events.)

  - #### focusType

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Focus types supported by this handler. (Default: all) Types not listed are filtered out: not handled by this handler nor any of its successors. (Relevant only for model-generated events.)

  - #### expressionFilter

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Expression that returns true (if the event is to be processed and passed further) or false (if it has to be thrown off).

  - #### fromExpression

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    from address overwrites notificationConfiguration/mail/defaultFrom

  - #### recipientExpression

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Recipient(s) that should get the notifications. Expression should preferably return a focus object that can be later used by a transport to extract the address and also to determine language for multi-language message templates. Alternatively, an address as a string can be returned directly - mail address, phone number, etc. Obviously, this is not flexible enough for notifiers sending messages with multiple different transports. Expression can return multiple values and multiple expressions can be specified. The results of all the values are merged and message for each recipient (or address) is sent.

  - #### ccExpression

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    cc Recipient(s) that should get the notifications.

  - #### bccExpression

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    bcc Recipient(s) that should get the notifications.

  - #### messageTemplateRef

    Flags: RAM

    Multiplicity: [0,1]

    Display order:

    Reference to the message template that produces the content of the message. If other content related expressions are used they override the ones from the message template.

  - #### subjectExpression

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    How to construct the subject of the message that is to be sent.

  - #### subjectPrefix

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Simpler alternative to subjectExpression: the subject itself will be constructed by the notifier, but it will be prefixed by value specified here.

  - #### bodyExpression

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    How to construct the body (text) of the message that is to be sent.

  - #### contentType

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Body content type, e.g. text/plain (the default), text/html, and so on.

  - #### contentTypeExpression

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Body content type, e.g. text/plain (the default), text/html, and so on - specified as expression. If `contentType` element is used, this one is ignored.

  - #### attachment

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    Message attachment(s) to be sent out. Can be combined with `attachmentExpression`. If message template is used, its `attachment` are also added to the final list of attachments.

  - #### attachmentExpression

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    An expression that returns message attachment(s) to be sent out. Returned objects should be of type NotificationMessageAttachmentType. If message template is used, its `attachmentExpression` is ignored.

  - #### watchAuxiliaryAttributes

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Whether to send a notification when only auxiliary attributes (namely: validityStatus, validityChangeTimestamp, effectiveStatus, disableTimestamp, modifyChannel, modifyTimestamp, modifierRef and maybe others) are modified. If set to false (default), these attributes are hidden from list of modified attributes as well.

  - #### showModifiedValues

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Whether to show modified values (or only names of changed attributes). Default: true. (NOT IMPLEMENTED YET. THE NAME MIGHT CHANGE.)

  - #### showTechnicalInformation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Whether to show technical information (e.g. model context or account operation details).

  - #### transport

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

  - #### notificationSendingStrategy

    Flags: RAM,runtime,AVals:2

    Multiplicity: [0,1]

    Display order:

    How to send notification to individual recipients, e.g. one message to all recipients, or separate message to each one?

  - #### confirmationMethod

    Flags: RAM,runtime,AVals:3

    Multiplicity: [0,1]

    Display order: