DEFAULT LIST APPLET & DEFAULT FORM APPLET Impact (Doc ID 2055555.1)

Last updated on JULY 29, 2017

Applies to:

Siebel Consumer Goods - Version 8.1.1.14 [IP2014] to 15.18 [IP2015] [Release V8 to V15]
Information in this document applies to any platform.

Symptoms

BEHAVIOR
---------------
Add any file (PM/PR, theme, common, etc...) with the entries "DEFAULT LIST APPLET" or "DEFAULT FORM APPLET".
The issue is that any file included with these entries will affect the following ones:

   > DEFAULT LIST APPLET -> all list applets (correct) and all Gantt applets (not correct).
   > DEFAULT FORM APPLET -> all form applets (correct) and all Calendar applets (not correct).

For example, a custom PR for a list applet (which extents jqgridrenderer class) will be applied to a Gantt applet (which should extent fsdispatchboardrenderer) causing it not to load.
Also, extending DEFAULT APPLET FORM APPLET will destroy Save / Delete Query.

EXPECTED BEHAVIOR
-----------------------
The addition of custom files with entries "DEFAULT LIST APPLET" or "DEFAULT FORM APPLET" should not affect other applets.

STEPS
-----------------------
1. Create any PR/PM you would want to apply to all List/Form applets across application. No need for it to actually do anything.
2. Add this PR/PM to the Manifest Files
3. Add this PR/PM in the Manifest Administration view to either DEFAULT LIST APPLET or DEFAULT FORM APPLET (using a PR or PM entry as needed).
4. Log out
5. Log in again.

Cause

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