Purpose

To update the Order Values and the Closed check box for the Content Type supported by each Delivery Type

Valid mappings between system message delivery types and system message content types will define the content type supported by each delivery type. For example, the delivery type EMAIL supports content types HTML, Plain Text and PDF.

A delivery priority will be assigned to each delivery type/content type combination. The default priorities (for example, the values shipped to clients) will reflect the level of "richness" of each content type. Content Types with a lower order number provide more display options than Content Types with higher order numbers. For example, PDF is a richer content type than TEXT and would therefore have a higher priority (lower number) than TEXT. An institution may update the default priorities, particularly in cases where there is a preference not to support richer (and more expensive) Content Types.

Delivery type / content type combinations will be used to determine the valid delivery 'modes' for each job or process output. For example, the following system message content type mappings may exist:

System message Content Types can be mapped to System Message Delivery Types as follows:

Consequently, if a correspondence type has a MobileXML job output, then the valid default delivery modes derived from the above mappings are:

• EMAIL/text/html
• EMAIL/text/plain
• SMS/text/plain
• Wap-Push/text/wml

If, for example, an institution does not wish to support Email/text/html or Wap-Push/text/wml messages, it could close those Delivery Type/Content Type combinations.

System Message Delivery Type Content block

• System Message Delivery Type
• Description
• System Message Content Type
• Priority
• Closed check box
• Message Content Type Description
• MIME Content Type

Rules/Notes:

Using this form, you can only update Order values and the Closed check box.