|Bookshelf Home | Contents | Index | PDF|
Field values from Siebel database records can be substituted into the structure of the template for each recipient of a communication that uses the template. Field substitution can apply to text entered directly into the template, to text in the subject line, and to literature items and files.
For a template item, you can use advanced field substitution, where you specify an iteration child business component from which to substitute field values for a template item. Each template item repeats, in iterative fashion, for every applicable child record.
For example, assume that the recipient group is Account Team Members and the Iteration Child Business Component field for the template item is Opportunity. In the outgoing message, the content of the template item is repeated once for each opportunity (child business component) that is associated with the account (parent business component).
Field substitution is supported in plain-text or HTML templates or in template items. (Template items that specify files in other formats, such as RTF or Microsoft Word, do not support field substitution.)
In an HTML template or a template item, for example, you can specify a row containing substitution fields in a single-row HTML table to align field data. If you specify an iteration child business component, then the tables repeat, and you can align field data from multiple records.
Field substitution functions correctly for an outbound communication request if the request specifies the same recipient group that the template specifies. If the recipient groups are different, then the field names (with enclosing brackets) might appear in each message as literal character strings without substitution. Substitution still occurs for fields that are applicable to the recipient group of the request.
The Siebel repository applicable to where you create templates must be consistent with the repository applicable to where you use the templates. Otherwise, field substitution behavior might not occur as expected.
For example, if you use the Siebel Mobile Web Client (connected to a local database), then create templates only if the applicable business objects and business components (and substitution fields) in that environment are consistent with those in the enterprise repository.
|Siebel Email Administration Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|