Finding Code Artifacts for Customization (Part 1)

Customizations to Fusion Applications may be implemented at runtime (RT) using composers or design time (DT) using JDeveloper. In the former case locating the code artifact to be customized is implicit; we are in the context of the code artifact when we invoke the composer. The latter is more complicated as we may not know the name of the page / region to be customized. While JDeveloper allows us to search the EAR archive based on the name of the object, we are not able to search based on the content of the file (other than on the operating system level) nor are we able to view content of the page / region as it is presented through the application.

This series of documents is intended to illustrate the options that we have to map RT UIs to code artifacts and to inspect their structure.

Using composer to inspect code artifacts

The easiest way to map a RT UI to the related code artifacts is to access the RT composers; this is the recommended solution documented in the developers guide section step 1-2 :

10.2.2 Determining Which ADF Artifacts You Need to Customize
To illustrate the process this document will cover an example case where we want to customize content on a setup page. In order to customize and test the content we need to identify the region containing the content to be customized and the page that can be run to test the changes.

In the example case we want to modify the “Implementation Projects” UI. First we need to navigate to the page to be customized (Figure 1):
Page to be customized
Figure 1 Page to be customized

On top right hand corner there is an administration menu available (assuming appropriate access has been granted to the user) from where we can invoke “Manage Customizations” (Figure 2):
Menu to invoke Manage Customizations UI
Figure 2 Menu to invoke Manage Customizations UI

The manage customizations UI can be used to identify the page to be run for testing (Figure 3):
Manage Customizations UI
Figure 3 Manage Customizations UI

Next the we need to identify the region to customize. On top right hand corner there is administration menu available (assuming appropriate access has been granted to the user) from where we can invoke “Customize .. Pages” (Figure 4):
Menu to open Page Composer
Figure 4 Menu to open Page Composer

We are presented with the composer that can be used to create RT customization. On the editor we click the region that we want to customize (Figure 5):
Page Composer
Figure 5 Page Composer

A confirmation dialog may be presented, if so we choose the option to edit the component. On the page opened we highlight the region and we are presented with the name of the region (Figure 6):
Region to be customized highlighted in the Page Composer
Figure 6 Region to be customized highlighted in the Page Composer

Summary

In order for us to create customizations using JDeveloper we will need to be able to identify the code artifacts to be customized. The easiest method is to navigate to the UI and use the composers to identify the related code artifacts.

In future articles other methods of finding code artifacts such as finding the underlying ADFbc artifacts related to the UI components will be documented.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Follow us on twitter Fusion Applications Extensibility, Customizations and Integration forum Fusion Applications Dev Relations YouTube Channel
This blog offers news, tips and information for developers building extensions, customizations and integrations for Oracle Fusion Applications.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
4
5
6
8
11
12
13
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today