Siebel Communications Server Administration Guide > Defining Outbound Communication Requests >

Fields for Outbound Communication Requests

This section describes the fields for outbound communication requests. Several fields are read only, and can be referenced for tracking purposes:

NOTE:  Not all fields appear on all of the outbound request views. Check the application user interface for the specific views on which a particular field appears.

  • Description. Enter a description for the request.
  • Request #. (read only) A unique ID for each request, which is generated when the request is created.
  • Recipient Group. Select from a picklist the group of intended recipients for the communication. The recipients might be, for example, all contacts associated with an opportunity—this group is identified as Opportunity Contacts.

    After you specify the Recipient Group here, the Recipient Sources list in My Outbound Request Overview changes to reflect the business object representing the source from which the recipients are derived, such as Opportunities. The recipient source business object is identified using a label displayed 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 will be sent—such as the Opportunity Contacts for each opportunity.

    NOTE:  The Recipient Group picklist 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 the recipient group, see Predefined Recipient Groups.

    You can customize which values appear in the Recipient Group picklist. 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 individual recipient if Only Send Preference is checked for the request, but no communications preference is specified for the recipient.

    For more information, see the description for Only Send Preference.

  • Only Send Preference. Check this option to send to each individual recipient only the templates that match the recipient's communications preference, if it is specified, or that match the channel preference specified in the Default Preference field.

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

    The communications preference field affected by the Only Send Preference check box 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 this user property is not defined, then the preference is retrieved from the Preferred Communications field, if the business component includes such a field. For more information, see Applications Administration Guide.

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

  • Start Time. (read only) The time that the Communications Outbound Manager server component started processing the request.
  • End Time. (read only) The time that the request was fulfilled.
  • Created. (read only) The time that the request was created.
  • Created By. (read only) The user who created the request.
  • Status. (read only) The current status of the request. For more information, see Monitoring Outbound Communication Request Status.
  • Status Message. (read only) Status message text generated by the Communications Outbound Manager server component for the request, if such text was generated. For more information, see Monitoring Outbound Communication Request Status.
  • Comments. Enter comments about the request.
  • Component Name. Displays the name of the server component that is to process the outbound communication request.

    The default component name is CommOutboundMgr (for Communications Outbound Manager). If you have configured any new server components based on CommOutboundMgr, you can specify another component name here.

    For example, if you have created and configured the server component CommOutboundMgr2, and want the current request to be processed by an instance of this component, specify this new component name in this field.

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

    For more information, see Administering Communications Outbound Manager. Also see Global Deployment Guide.

    NOTE:  Subrequests specified for a request may be processed by more than one server task for the server component designated to handle the request, according to how your environment is configured. For more information about subrequests, see Configuring Subrequests.

Siebel Communications Server Administration Guide