Last updated on JANUARY 03, 2017
Applies to:Siebel CRM - Version 18.104.22.168.15 [IP2013] and later
Information in this document applies to any platform.
*** Reviewed for Currency: 03-Jan-2017 ***
On : 22.214.171.124.15 [IP2013] version, Task Based UI
The goal is to build a Task to help users create new Opportunities in the Call Center application.
The Task includes steps that call Business Services to update the newly created Opportunity.
The Task is based on the Opportunity Business Object.
There are numerous Opportunity Types based on different Business Components that have been cloned.
When calling a Business Service on a new Opportunity record created by any Business Component (BC) other than Opportunity BC, the Business Service cannot find the Opportunity record.
Calling an explicit Commit step in the Task writes the record to the database where the Business Service can then find the record.
Since this method impacts performance (slows down the process), this is not desirable; however, the method works.
How can the record context of the newly created Opportunity be passed from the Task to the Business Service?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms