Siebel Order Management Infrastructure Guide > Unified Messaging >

Creating Message Types

A message type stores the definition of a message, including its text, its bitmap, and its display mode. The process of creating a message type involves adding a new message type record, adding message translations, defining message type responses, and creating translations for message type responses.

To implement a new message type

1. Navigate to the Administration - Order Management screen, then the Message Types view.
2. In the All Message Types list applet, create a new message type record.
3. Complete the fields for the new message type record. Message Type fields are described in the table that follows.

   Field	Comments
   Title	Enter the title that will be displayed on the popup applet for an active message. For example: Recommendation
   Display Mode	Select the display mode. Options are: Passive. The message is displayed on the screen, but it does not demand a response from the user. Active. The message is displayed in a dialog box, and the user must select a response (such as "Accept" or "Reject") to close the message and continue.
   Group	Use this field to group related messages together. This field constrains pick applets in administration views, such as in the Administration - Product screen, then the Product Recommendations view.
   Bitmap	Select the graphic that will be displayed on this message. For example, you might display an exclamation point graphic for an alert. NOTE:  The Bitmap field applies only to messages with active display mode.
   Short Text	Enter a short message to be displayed, using text and field names. For example: We recommend [Related Product]. NOTE:  Short Text is generally not used, except by a custom message display service.
   Full Text	Enter a message to be displayed, using text and field names. For example: We recommend [Related Product] for [Net Price]. [Reason]

4. (Optional) If this text must be translated, click the Translations tab.
   • Add records to the Translations list, and enter the translation for the content of the Full Text field. You must add one record for each language being translated. Translations fields are described in the table that follows.

     Field	Comments
     Language	Enter the code for the language of this translation. For example, enter FRA for French.
     Title	Enter the title that will be displayed on the popup applet for an active message. For example: Un Recommendation
     Short Text	Enter a short message to be displayed, using text and field names. For example: Nous recommendons [Related Product]. NOTE:  Short Text is generally not used, except by a custom message display service.
     Full Text	Enter a message to be displayed, using text and field names. For example: Nous recommendons [Related Product] pour [Net Price]. [Reason]

5. Click the Payload tab, and specify the payload variables to be substituted into the Full Text field. Payload fields are described in the table that follows.

   Field	Comments
   Payload	Enter the name of the payload variable to be substituted with text. For example: Campaign Id
   Response	Choose from a picklist of values built from the fields of the UMS Response business component (which is based on the S_COMMUNICATION table). For example: Campaign Offer Id The response field is the field used to record the user response to messages.

6. Create a response for the message type.
   1. Write a custom business service to process the new response.

      For information about how to write a response-handler business service, see Attaching a Business Service to a Message Response.

      For example, the custom business service creates an activity to mail product literature to the customer.

   2. Compile a new SRF.
   3. In the Administration - Order Management screen, then the Message Types view, select the message type for which you are creating a response.
   4. Click the Responses tab.
   5. Add the new response to the message type:
      • Complete the required fields: Name, Business Service, Method.
      • Set the Log flag to indicate whether to log this response.
      • Set the Suppress Repetition flag and its corresponding field, if this response causes suppression of the message.
      • Resequence the existing responses so that buttons appear in the correct sequence on the user interface.
7. Create translations for the message type response.

   Translations for the message type response make sure that the text displayed on the actionable buttons is in the correct language.

   NOTE:  Translation records are not required if your implementation is mono-lingual. For single-language implementations, the default text in the message type and in the message type response is used.

8. Test the application by creating a situation where the message is displayed, and then clicking New Response.