How to delete controller extension in oaf
Controller Extension steps are quite different from the VO extensions steps. In VO extensions , we register the Custom VO in the Application through JPX importer scripts but in controller , we don't need to register this with the JPX import script. We just move the Custom Controller to required Path under the Java_Top and then copy that path and then put the same path under the Personalizations tab of the OAF region in which we want to the Controller Extension so after that , OAF page or region start taken care of this Extended Controller.
As we discussed , CO extensions is not similar Like the VO extension so in the Same way the steps to delete the Extensions in OAF are also not similar. In VO we use the standard API jdr_utils.deletedocument to delete the VO extensions and we also should know the exact name and Path of the VO extensions to put as a parameter in this API. To know more about How to delete VO extension in oaf. According to me , to delete CO Extension is quite easy and simple as compared to the VO extension because in this we don't need to delete its registrations by using API's and other stuffs.
0 comments:
Post a Comment