Top of COR | Index | Table of Contents | Feedback | ![]() |
CORF2630 - Maintain System Communication Delivery Type Content
Purpose |
To update the Order Values and the Closed check box for the Content Type supported by each Delivery Type |
|
SubSystem | Correspondence | |
Normally Run By | Admission/Assessment Specialist | |
Anticipated Frequency | As required | |
Structure | Block | System Communication Delivery Type Content |
Valid mappings between System Communication Delivery Types and System Communication Content Types will define the content type supported by each delivery type. For example, the delivery type EMAIL supports content types TEXT/HTML, XML, TEXT/PLAIN, PDF and RTF. 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/PLAIN and would therefore have a higher priority (lower number). An institution may update the default priorities, particularly in cases where there is a preference not to support richer (and more expensive) content types. System Communication Delivery Types are mapped to System Communication Content Types as follows:
If an institution does not wish to support any of these, then it should close those delivery type/content type combinations. |
System Communication Delivery Type Content block
|
Rules/Notes: Using this form, the user can only update the Priority values and the Closed check box. |
Last Modified on 18 May, 2010 3:21 PM
History Information
Release Version | Project | Change to Document |
12.1.0.2 | 1580 - Correspondence | Changed 'Message Content' to 'Communication Content' and updated list of combinations. |