Configuring Recipient Sources Applets

This topic describes how to configure the Recipient Sources applet and associated applets. For more information about configuring applets, see Configuring Siebel Business Applications and Siebel Developer's Reference.

To configure Recipient Sources applets

1. Start Siebel Tools.

   If the Comm Source bus_obj_name List Applet applet is defined, where bus_obj_name is the name of the business object that serves as the recipient source, then you do not need to create the applet in Step 2 and Step 3.

2. As necessary, create a new applet, or copy and modify an existing applet.

   For example, you can copy the Comm Source List Applet applet, which appears as the Recipient Sources applet.

3. Provide a name for the new applet in the form Comm Source bus_obj_name List Applet, where bus_obj_name is the name of the business object that serves as the recipient source.

   Note: You must specify the Comm Source bus_obj_name List Applet for recipient groups for communication requests. The recipient groups listed for communication requests are only those recipient groups for which applets with this naming convention are defined. For recipient groups to use only for communications templates, this naming convention is not required.

   The class of the new applet must be CSSFrameListCommSrc.

4. Specify the business component associated with your new applet. If you copied Comm Source List Applet or another existing applet, then you must also modify the business component that your new applet is associated with.

5. Add the new applet to the Applet Toggle list for the Comm Source List Applet.

   When a user selects the corresponding value from the Recipient Group drop-down list, as configured in the previous procedure, the Recipient Sources applet automatically functions like the new applet you define in this procedure. You define the recipient source business object using a label that appears on the far side of the applet header area.

6. Create a new association applet for the new recipient source, or use an existing association applet, and set it into the new list applet.

   An association applet is the applet that appears in a dialog box when you add a new record in a fixed applet that allows association. For example, an association applet might be for associating an account with a communication request. Every list applet has an Assoc Applet property that you can set to an association applet.

7. Create a link between the Comm Request business component and the new recipient source business component, and use S_COMM_REQ_SRC as the intersection table.

   For examples, refer to the existing links defined for the Comm Request business object.

8. Add the new recipient source business component to the Comm Request business object, and specify the link from Step 7.

9. For outbound communication requests for email, fax, or page, define the following user properties on the business component to use as the recipient group:

   • Recipient First Name Field. The business component field containing the recipient’s first name.

   • Recipient Last Name Field. The business component field containing the recipient’s last name.

   • Recipient Preferred Medium Field. The business component field containing the recipient’s communications channel preference.

     If the Only Send Preference setting is specified for a communication request, then a communications template is sent to a recipient if the template channel type corresponds to the value in the field that this user property indicates. For more information about the Only Send Preference, see Fields for Outbound Communication Requests.

     If you do not set this user property, then the preference is retrieved from the Preferred Communications field if the business component includes such a field.

   • Recipient Email Address Field. The business component field containing the recipient’s email address data.

     For example, in the Contact business component, your application might use the Email Address field for email address data. In this scenario, Recipient Email Address Field must specify the Email Address field. (This field is specified by default.)

   • Recipient Fax Address Field. The business component field containing the recipient’s fax address data.

     For example, in the Contact business component, your application might use the Fax Phone # field for fax address data. However, the Recipient Fax Address Field must specify the Fax Address field. (This field is specified by default.) Fax Address is a calculated field that prepares fax addressing data obtained from the Fax Phone # field for use with your fax server.

     The formatting for fax-related fields depends on your fax server requirements. By default, the calculated field value for the Fax Address field contains fax formatting that applies to OpenText RightFax and specifies the email account that the fax server monitors. You must modify all such field values as appropriate for your specific fax integration. For more information, see Integrating with Fax Products and Configuring Fax Integration Elements in Siebel Tools.

   • Recipient Fax Address Prefix. An optional prefix string for the recipient’s fax address.

   • Recipient Fax Address Suffix. An optional suffix string for the recipient’s fax address.

   • Recipient Pager Address Field. The business component field containing the recipient’s pager address data. For more information about this field, see the Recipient Pager Address Field in the Employee business component for the correct pager address format.

For outbound communication requests that use wireless messaging, the listed user properties are not used. Each recipient’s mobile device address data is obtained from the Mobile Device Address business component using the recipient’s ID stored in the S_PARTY table. System administrators enter mobile device address data in the Mobile Devices view of the Administration - Communications screen, and users enter mobile devise address data in the Mobile screen. For more information about wireless messaging, Using Wireless Messaging