Last updated on AUGUST 04, 2015
Applies to:Siebel CRM - Version 15.1 [IP2015] and later
Information in this document applies to any platform.
Most of the time you can use Manifest administration and get the results you expect without incident. When you add a custom UI object against an applet, the simple rule "customer wins" goes into play and ensures that the applet specified will use the specified renderer or model. But there's a gotcha in store for those trying to implement system wide changes by overriding global defaults such as DEFAULT LIST APPLET.
This is the evaluation process behind the scenes:
1 Is there a custom applet-specific renderer/model
2 Is there a custom default renderer/model
3 Is there a seeded applet-specific renderer/model
4 Is there a seeded default renderer/model
In IP2015 we deliver 269 seeded physical renderers. Not all of those will be list applets, but quite a few will be. If you, or a custom/partner want to implement a global DEFAULT LIST APPLET renderer, all seeded renderers for list applets will be killed off by step 2 in the manifest evaluation. The only solution for that will be for the customer to create copies of every manifest record where they wish the delivered functionality to work properly. There's probably a similar story for models and, as time goes on, the list will increase. The customer will upgrade and new functionality will not work due to the customer record on DEFAULT LIST APPLET.
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