...
- Standard: This option is selected by default. Standard message parts are based on fields that exist only in the current message source. For example, a message part for the Persons service could display a person's address.
- Script: Message parts that include information derived from outside the current message source can be set up using Visual Studio .NET scripts. For example, a message part for the Persons service could display the order history for that person as a formatted list. See "Creating a Script Part" in the Messaging Administration chapter of the Admin Guide for for more information.
- Component: This option specifies that the message part uses the object specified on the Component tab.
...
This tab is applicable for derived parts that leverage the functionality of a base part. A derived part's input map provides values for the base part's input properties. See Creating a Derived Part in the Message Administration chapter of the Admin Guide for for details.
Input Properties Tab
This tab is applicable for parts that can be used as Base Parts by another part. This tab lists the possible input properties that the base part supports. A derived part's input map provides values for the base part's input properties. See Creating a Generic Base Part in the Message Administration chapter of the Admin Guide for for details. Also, see About the Input Properties Form for information on the Input Properties sub-type form.
...
This tab contains the text of the Message Part in plain text format. This is the message part data that is inserted into a text-based message. You can also enter VBScript on this tab to define the part using a script. See Creating a Script Part in the Message Administration chapter of the Admin Guide for for details.
User Permissions Tab
...