Performance Issues While Constraining Associate Applet
Last updated on FEBRUARY 09, 2016
Applies to:Siebel CRM - Version 18.104.22.168.11 [IP2013] and later
Information in this document applies to any platform.
Customer have following requirement:
Under Action BO, the primary BC = Action, Secondary BC = Opportunity.
The primary BC applet is Normal Activity Form Applet (which contains the Account mapped to the activity)
The Child BC Applet is where we can add already existing opportunities using "Add" button invoking the "Associate Applet". The Associate Applet is based on Opportunity BC.
The requirement is to filter the Opportunities in the Associate applet where the "Account" of the Opportunity is the same as the Account mapped to the activity.
What will be the best way to implement this?
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