Siebel Communications Server Administration Guide > Configuring User Interface Elements > Configuring Recipient Groups for Requests and Advanced Templates >

About Recipient Groups

This section describes concepts that will help you in either using or configuring recipient groups used with advanced templates and outbound communication requests.

For more information about working with business objects, business components, links, and other elements mentioned here, see Configuring Siebel Business Applications and Siebel Developer's Reference.

Each recipient group specifies a source business object, called the recipient source—such as Opportunity, Account, Action, Internal Division, and so on. The recipient group also specifies a recipient group business component, which must be a direct child of the primary business component for the recipient source business object.

The actual recipients for a communication request come from the recipient group business component, such as Contact, Employee, and so on. The link between the primary and child business components defines these recipients. For example:

  • A recipient group could be based on a recipient source specifying one or more accounts and the contacts of these accounts (Account Contacts).
  • A recipient group could be based on a recipient source specifying one or more opportunities and the sales-team members of these opportunities (Opportunity Sales Team Members).
  • A recipient group could be based on a recipient source directly specifying one or more employees (Employees).

NOTE:  Make sure that you select Link Specification for the Primary Contact ID field in the parent business component.

Recipient groups directly determine actual recipients only for outbound communication requests. For advanced communications templates, they determine which fields are available to be substituted with Siebel application data when the template is sent to each specific recipient for the request.

NOTE:  If you create a new recipient group using a custom business component, and set the Create Activity flag for an advanced template that uses this recipient group, then you must create a System Activity object on the custom business component in order to specify fields that can be logged with activity logging. See also the description of the Create Activity flag in Fields for Templates.

Siebel Communications Server Administration Guide