Controller Extension in OAF
Controller Extension in OAF
Set the values of following profiles to enable Personalization Page link in OAF Pages
Profile Name
Value
Yes
Yes
No
Oracle does not recommend that customers extend controller objects associated with regions or
webbeans in shipped E-Business Suite product pages.
Controller class (oracle.apps.fnd.framework.webui.OAControllerImpl) methods should
effectively be considered private, since their implementation is subject to change. Controller
extensions are therefore not considered to be durable between upgrades.
If it is absolutely essential to handle custom form submit events on a shipped product page,
processFormRequest() is the only method that should be overriden in a controller class,
although the risks outlined above still apply.
Now for knowing which controller to extend we click on "About This Page" Link and select
Expand All. Here we can see the Name of the controller that we need to extend
Note -- Give the Name of your Extended Class give its package path and in the extends property
vo.setWhereClauseParam(1,"val6");
}
}
}
Click on Complete View -> Expand All -> Click on personalize icon next to Page Layout
Now at site level give the path of extended controller as we are extending the controller at SITE
LEVEL
Mahi.oracle.apps.fnd.coextensiondemo.webui.ExtendedSearchCO
By defaylt it will come as Inherit
Click Apply -> Return to Application
Click Go
Note Record with Column1 value val5 and Column2 value val6 is not coming in result