Message Type Fields
Here is a description of the fields that make up message types.
Key: * – Mandatory field. The number indicates the number of characters that are allowed in this text field.
| Field | Description | ||
|---|---|---|---|
| Developer Name | * | 255 | This uniquely identifies the developer reference. |
| Name | * | 80 | Name of the message type. |
| Description | 255 | Description of the message type. This field is optional. | |
| Message Retention | 10 | Number of months for which to retain messages belonging to this message type. To specify a number of months, enter a value between 1 and 99 with the suffix m. If you do not want messages of this type to be retained, enter 0 with no suffix. Enter - if you want messages of this type to be retained indefinitely. Leave this field blank if you want the value to be inherited from the parent message type or the root message type. |
|
| Parent | The parent message type to which this message type belongs. If the message type is to inherit from the root message type, leave this field blank. |
Buttons
| Button | Description |
|---|---|
| Messaging Export | Displays the Export Publications and Subscriptions page, which enables you to export the Foundations Publications and Subscriptions on your Salesforce org Salesforce organization to a JSON JavaScript Object Notation. A lightweight format based on a subset of JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. This is a text based format that is easy for both humans and computers to read and write. file. You can then import the publications and subscriptions to another Salesforce org using that file. |
| Messaging Import | Displays the Import Publications and Subscriptions page, which enables you to import Foundations Publications and Subscriptions from another Salesforce org using a JSON file. |