Using Substitution Fields In Siebel Email Response Templates (Doc ID 1475200.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Email Response - Version 8.0.0.9[20433] and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jan-2014***

Symptoms

On : 8.0.0.9[20433] version, Comms Server & Email Response

ACTUAL BEHAVIOR
---------------
Using Substitution Fields in Siebel Email Response Templates

Siebel Email Response Administration Guide, Version 8.1 -> Chapter 4, Setting Up Siebel Email Response ->
section Using Substitution Fields in Siebel Email Response Templates - > Setting Up Additional Business Components for Substitution Fields

on page 61, it states

Setting Up Additional Business Components for Substitution Fields
Recipient groups are based on business objects. When you create a template, you associate it with a recipient group. Siebel Email Response checks the recipient group that you assign to the template to determine the associated business object. For example, the Service Request Contact recipient group is based on the Service Request business object, and the Opportunity Sales Team recipient group is based on the Opportunity business object. You can use fields from any business component as substitution fields in a template.

Siebel Email Response looks at the user properties in the Communications Outbound Email business component for a record that describes the relationship between the Communications Outbound Email business component and the Target business component. The following user property record shows
that the Communications Outbound Email business component is related to the Account business component, using the Account Id field as the foreign key:

Source Id Field: Account=Account Id

To set up other business components for substitutions
1. In Siebel Tools, associate the Target business component (for example, Quotes) with the
Communications Outbound Email business component.
2. Add a new user property to the Communications Outbound Email business component.
For example, add the following user property to the Communications Outbound Email business
component:

Source Id Field: Quotes=Quote Id

In this example, Quotes is the name of the business component, and Quote Id is the name of the foreign key between Communications Outbound Email and Quotes.

Using the same approach, customer enabled additional business components for substitutions by adding below user property in the "Comm Outbound Email" BusComp.
1) 

Source Id Field: Quote AT =  Quote Id

Substitution for Quote works as expected.

2)
Subistitutions was not working for BC "Order Entry - Orders".

Source Id Field: Order Entry - Orders = AT Order Id


EXPECTED BEHAVIOR
-----------------------
Customer should be able to use substitution from "Order Entry - Orders" BusComp fields.

TEST STEPS
-----------------------
1. In Siebel Tools application, navigate to:
Comm Outbound Email BusComp - > Business Component User Prop.
2. Create the following records with the following values (they were using custom business components)

Source Id Field: Order Entry - Orders = AT Order Id.

3. Compile SRF.
3. Test field substitutions from "Communication Detail - Response View" view.


BUSINESS IMPACT
-----------------------
Due to this issue, users cannot achieve desired functionality.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms