Unable to Pre-Default the Primary Contact of a New Activity With the One of the Parent Opportunity
(Doc ID 545518.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel Tools - Version 184.108.40.206 SIA  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 220.127.116.11  Fin Svcs
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: IBM AIX 4.3.3
This document was previously published as Siebel SR 38-1026546791.
""Checked for Relevance on 28-Feb-2012""
We have a problem with pre-defaulting contacts from the opportunity to the Activity applet in the Opportunity Detail - Activities View, when we create new activities under a Opportunity.
When we create an opportunity we associate one (ore more contacts) to the opportunity. When the opportunity is created, we want to create activities related to this opportunity (in Opportunity Detail - Activities View ). When we create a record in the Activity applet som fields are pre-defaulted, e.g Opportunity Name. We also want to pre-default the contacts from the Opportunity to the created Activity. And in Siebel Vanilla it looks like this is out-of-the-box functionality (in BusComp Action the field Contact Id have a pre-default value equal "Parent: 'Opportunity.Key Contact Id'). We have tested this with a Siebel Vanilla .Srf (v7.04 and v7.52), but it doesn't work.
Pre-defaulting values to Multi Value fields are typically not standard, but there are areas where this is done (Reference to Bookshelf), e.g Service Request. (When you have a service request associated with several contacts, and create activities in relation with this service request, the contacts from the service request is populated to the activity record).
We need the Contact details from the Opportunity applet to be populated in the Contact fields on the Activity applet, the same way as in Service Request.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|