Siebel Email Administration Guide > Configuring User Interface Elements > Configuring Recipients for Send Commands >

Configuring Joined Generic Recipients

To configure joined generic recipients for a business component, specify values for the following business component user property:

• Recipient Id Field N (where N is an integer). A comma-delimited list of three required values, and an optional fourth value, that points to records in the joined business component. The Send Email, Send Fax, and Send Wireless Message commands use this user property.

  For example, the Service Request Contact joined generic recipient type is defined for the Service Request business component using the Contact Id, Contact, Service Request Contact value. The value for this user property includes the following elements:

  • The foreign key field in the parent business component that points to records in the joined business component. In this example, this field is Contact Id, a field in the Service Request business component that corresponds to the Id field in the Contact business component.
  • The joined business component. In this example, the joined business component is Contact.
  • The text of the label to appear for this generic recipient in the Recipient field. In this example, this text is Service Request Contact.
  • An optional fourth element that identifies the primary key field in the target business component to join to. By default, the field name is assumed to be Id. Include this element in the user property value if the field name is other than Id. (In this example, this element is unnecessary because the Contact business component uses the Id field.)

You can specify multiple joined generic recipients for a business component. That is, you can define the Recipient Id Field 1 user property to specify one joined generic recipient (such as Service Request Contact), Recipient Id Field 2 to specify another recipient (such as Service Request Owner), and so on. The order of the integers in the user property names determines the order in which the joined generic recipients are listed in the Recipient field.

Additional Requirements for Joined Generic Recipients

When you configure joined generic recipients, also consider the following requirements:

• For Send Email and Send Fax, the user properties of the nonjoined type must be set in the joined business component, such as in the Contact business component, joined from the Service Request business component. For information about the user properties of the nonjoined type, see Configuring Nonjoined Generic Recipients.
• The joined business component, such as Contact, must belong to the Messaging Recipient business object. (The Contact and Employee business components already belong to this business object.)
• If a business component has user properties defined to specify both nonjoined and joined generic recipients, then the joined recipients take precedence.
• If any user property definitions of Recipient Id Field N are specified as inactive in Siebel Tools, then all such definitions with higher numbers are also inactive.