Purpose

To define the valid message service transformations that can be applied to each source Content Type in order to produce derived Content Types

System-defined mappings between System Message Content Types define the valid message service transformations that can be applied to each source Content Type in order to produce derived Content Types.

For example, the message service can transform the content type MobileXML to HTML, WML, Plain Text and PDF.

It should be noted, however, that an institution can choose not to support the full suite of content transformations. Unsupported transformations will be set to 'closed'.

The form is populated with system data and only allows maintenance of the Closed check box.

Mappings

A 'From System Message Content Type' can be mapped to many 'To System Message Content Types'.

A 'From System Message Content Type' can be mapped to itself. For example, Acrobat PDF to PDF

System Message Content Type Transformation block

• From System Message Content Type
• Spread table
• Closed check box
• From MIME Content Type
• To MIME Content Type