# NotificationMessageAttachmentType (Complex Type)

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

Message attachment for notifications. The content might be provided either directly (as arbitrary object) or by referencing a file.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
contentType | property string | [1,1] | Content type for the attachment, e.
content | property anyType | [1,1] | Content of the attachment.
contentFromFile | property string | [1,1] | Name of the file that provides the content for this attachment.
fileName | property string | [0,1] | File name for the attachment.
contentId | property string | [1,1] | Value of the Content-ID header of MIME body part for this attachment.

- ### Items

  - #### contentType

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Content type for the attachment, e.g. image/png or text/html. It is required.

  - #### content

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Content of the attachment.

  - #### contentFromFile

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Name of the file that provides the content for this attachment.

  - #### fileName

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    File name for the attachment. E.g. in the case of the mail transport it should be put into Content-Disposition header field. If omitted and if contentFromFile is used, it should be derived from the name of that file.

  - #### contentId

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Value of the Content-ID header of MIME body part for this attachment.