Siebel Email Administration Guide > Defining Outbound Communication Requests >

Fields for Outbound Communication Requests

This topic describes the fields for outbound communication requests. Several fields are read only, and you reference them for tracking purposes.

NOTE:  All fields do not appear in all of the outbound request views. Check the application user interface for the specific views in which a particular field appears.

The following fields apply to outbound communication requests:

• Description. Enter a description for the request.
• Request #. (read only) A unique ID for each request. This ID is generated when you create the request.
• Recipient Group. Select from a drop-down list the group of intended recipients for the communication. The recipients might be, for example, all contacts associated with an opportunity. This group is Opportunity Contacts.

  After you specify the recipient group, the Recipient Sources list in My Outbound Request Overview changes to reflect the business object, such as Opportunities, that represents the source from which the recipients are derived. The source business object for the recipients is identified using a label that appears on the right side of the applet header area.

  You add records to the Recipient Sources list, which is renamed to reflect the specified business object, to specify one or more instances of the primary business component for this business object, such as particular opportunities.

  The read-only Recipients list, which appears below the Recipient Sources list, shows every individual recipient to whom a separate instance of the communication is sent, such as the Opportunity Contacts for each opportunity.

  NOTE:  The Recipient Group drop-down list displays recipient group types for many major business objects and business components. For a list of the predefined values and the business object and business component associated with each recipient group, see Predefined Recipient Groups.

  You can customize the values that appear in the Recipient Group drop-down list. For more information, see Configuring Recipient Groups for Requests and Advanced Templates.

• Default Preference. Specify a default delivery type to use for communication requests to each recipient if the Only Send Preference check box is selected for the request, and no communications preference is specified for the recipient. For more information, see the description for Only Send Preference.
• Only Send Preference. Select this option to send to each recipient only the templates that match the recipient's communications preference, if this preference is specified, or that match the channel preference in the Default Preference field.

  If you construct a communication request that contains templates of more than one channel type, and you select this option, then a recipient can receive communications only for a single channel type.

  The communications preference field that the Only Send Preference check box affects generally corresponds to the setting of the Recipient Preferred Medium Field user property for the business component.

  For example, for both employees and contacts, the Preferred Communications field is the default field containing the channel preference. (For contacts, the caption for this field is Contact Method.) If you do not define this user property, then the preference is retrieved from the Preferred Communications field if the business component includes such a field. For more information, see Siebel Applications Administration Guide.

  If the communications preference is not specified for a recipient, and the Only Send Preference check box is selected, then the preference in the Default Preference field is used for that recipient.

• Start Time. (read only) The time that the Communications Outbound Manager server component starts to process the request.
• End Time. (read only) The time that the request is fulfilled.
• Created. (read only) The time that the request is created.
• Created By. (read only) The user who creates the request.
• Status. (read only) The current status of the request. For more information, see Monitoring Outbound Communication Requests.
• Status Message. (read only) Status message text, if any, that the Communications Outbound Manager server component for the request generates. For more information, see Monitoring Outbound Communication Requests.
• Comments. Enter comments about the request.
• Component Name. The name of the server component that is to process the outbound communication request. For more information, see Administering Communications Outbound Manager and Siebel System Administration Guide.

  The default component name is CommOutboundMgr (for Communications Outbound Manager). If you configure any new server components that are based on CommOutboundMgr, then you can specify another component name in this field.

  For example, if you create and configure the CommOutboundMgr2 server component, and you want an instance of this component to process the current request, then specify this new component name in this field.

  NOTE:  If your Siebel application deployment involves different SRFs (Siebel Repository Files), then run differently named server components that are based on CommOutboundMgr for each different repository file used by one or more Siebel Server. Otherwise, field data might not be correctly substituted in your communications templates.

  NOTE:  According to your environment configuration, more than one server task (for the server component designated to handle a request) might process subrequests for the request. For more information about subrequests, see Configuring Subrequests.