The Role of Customization Allowed Property

This blog post is aimed at developers and administrators who wish to do any design time customizations on ADF UI layer or any runtime customizations via PageComposer or AppComposer. It explains why certain artifacts may not let you perform any customizations. All the ADF artifacts have a property named “Customization Allowed” with default value set to default. By default it means the behavior is parent dependent (explained later).  If the value resolves to true then a customer can make design time customizations on the artifact e.g. hiding some of the table columns, adding additional attribute to a View Object. 

 In Fusion Applications, all the ADFbc objects have this property set to default. As a result all the ADFbc objects can be customized at design time. However, this is not the case with ADF UI artifacts like pages, page fragments, task flows etc. Some of these are restricted for customization by the development teams. If an artifact’s customization allowed property is set to default then the ability to customize that artifact is determined by its parent. And this continues until the top most parent (root) is found. If the value is non default then the value set at the child level has always the higher precedence over parent value. Taking an example of two level below is how it would work:

There is another property called “customization allowed by” this can be used to permit the customizations allowed by specific roles. This field accepts a comma separated list.  One key point about this property is that it is taken into consideration only when customizations allowed resolves to true. 

Behind the Scene

When the ‘Customization Allowed’ property is marked true in the property inspector as shown below:

 A .rdf file is created to store this information which is a W3C standard for metadata modeling. In this example it would be at <view project default path>/<page relative path>/mdssys/mdx/ViewFilePf.jsff.rdf.  The content would appear as below:

<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"><rdf:Description rdf:about="/">
    <customizationAllowed xmlns="http://xmlns.oracle.com/mds">
      false
    </customizationAllowed>
  </rdf:Description></rdf:RDF>

 These entries are imported into the MDS during deployment life cycle. At run time these properties are then merged with the artifact to determine the customizability of the artifact. This means that if customization allowed property is set to false then the artifact cannot be customized at runtime as well via PageComposer or AppComposer. 

Reference: 

http://docs.oracle.com/cd/E29505_01/fusionapps.1111/e15524/ext_customize.htm#CFHECAAJ

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
« August 2015
SunMonTueWedThuFriSat
      
1
2
5
7
8
10
12
14
15
16
21
22
23
26
27
28
29
30
31     
Today