Manifest Administration Execution Order
(Doc ID 2362452.1)
Last updated on DECEMBER 23, 2019
Applies to:Siebel CRM - Version 15.17 [IP2015] and later
Information in this document applies to any platform.
Customer has a custom vertical scroll bar (file1) implemented using a PR file and registered in Manifest administration with Usage Type as 'Physical Renderer' and Name as 'DEFAULT LIST APPLET'. This is working as expected across the application.
As part of a new change request in one of the list applets, customer created another PR file(file2) and is this is registered in Manifest with Usage Type as 'Physical Renderer' and Name as 'NNEU SETC Activity List Applet With Navigation'.
On implementation, it is observed that the PR file (file1) registered for 'DEFAULT LIST APPLET' is not working for the applet 'NNEU SETC Activity List Applet With Navigation'.
1. Why is the custom DEFAULT LIST APPLET PR file(file1) not working when the applet PR is also registered for the list applet? Is this an expected behavior? Are we missing any steps?
2. Does the applet PR file (file2) override the Default List applet PR in this case?
3. On registering file1 along with file2 in manifest with sequence as 1 and 2 respectively with Usage Type as 'Physical Renderer' and Name as 'NNEU SETC Activity List Applet With Navigation', both functionality seems to be working as expected. If we follow this step to resolve our issue will there be any impact since the file1 is also registered for 'DEFAULT LIST APPLET'.
4. Are there any other resolution for this?
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