Tech Honey

The #1 Website for Oracle PL/SQL, OA Framework and HTML

How to hide or show a region dynamically in OA Framework?

by

There often arises a situation where an OA Framework technical personnel needs to hide or show an OAF region at runtime. We will learn today how to hide or show a region at runtime using OA framework code.

Before we begin I assume that you have an OAF page (xTrialPG) and a controller (xxTrialCO). Also I assume that you have created a pagelayout region and have a OAMessageComponentLayoutBean (xxTrialMsgCompLayoutRN) region on xxTrialPG.

Let’s take this in steps for easy understanding.

Step 1: Import the OAMessageComponentLayoutBean region in your controller

import oracle.apps.fnd.framework.webui.beans.layout.OAMessageComponentLayoutBean

Step 2: Create a handle or reference of the xxTrialMsgCompLayoutRN region in our controller so that we can control the properties of xxTrialMsgCompLayoutRN via our controller.

OAMessageComponentLayoutBean xxTrialMCLayoutHandle = (OAMessageComponentLayoutBean) webBean.findChildRecursive(“xxTrialMsgCompLayoutRN”);

Step 3: Now using the xxTrialMCLayoutHandle handle created in step 2 we can hide/show the xxTrialMsgCompLayoutRN

xxTrialMCLayoutHandle.setRendered(false);

And that’s it. You can hide show any of the region at runtime depending upon the business requirement.

Thanks for Reading.
Until next post
Keep Learning 🙂

How to put validation in OAF Page?

by

Validation is the basic and the most important aspect of software development. If you are a software developer, working in any language or domain, then validating the data entered should not be a new thing to you, even there arises multiple situations while working with oracle apps where you need to put validations on the OA Framework page. So let’s see how this is done as far as OA Framework is concerned.

Suppose you have an OAF page and on that page you have a text box (OAMessageTextInputBean) and a button (OASubmitButtonBean). Now suppose that on the click of the button you want to add some validation logic, in order to achieve this we need to capture the click of the button event and within that event we can add the required business logic.

To capture the click of the submit button we need to follow the following steps.

Step 1: import the OASubmitButtonBean to the controller

import oracle.apps.fnd.framework.webui.beans.form.OASubmitButtonBean;

Step 2: capture the submit button click event in the processFormRequest() method of the controller

if(pageContext.getParameter(“xxTrialSubmitButton”)!=null)
{
}

Step3: Add the require validation logic within the captured event

if(pageContext.getParameter(“xxTrialSubmitButton”)!=null)
{
The validation logic goes here…
}

Make sure that you throw appropriate exceptions whereever mentioned as per the Functional and Technical Documents.

Thanks and Keep Learning

Types of Pages in OA Framework

by

Well this is a question that can be asked in any of the interviews and the answer that you can give for this question will be that there are two types of pages in OAF.

1. Seeded Pages
2. Custom Pages

Seeded Pages: All the OAF pages that come with the Oracle Application e-business suite are called seeded pages, these pages perform a particular business operation and hence come with the required business logic implemented in them.

Also seeded pages can be modified and the process of modification can be called as
a. Personalization
b. Customization

The process of changing a seeded page is called personalization when we are personalizing the page e.g. we are changing the label of a text box from “Employee Name” to “Name of Employee” or when we add a new item to the seeded page e.g. we are adding a new OAMessageTextInputBean to the seeded page. Personalization has got its own limitations e.g. we can add an item to the seeded page but we cannot and any business logic to the newly added item.

The process of changing a seeded page is called customization when we are changing the underlying business logic of the OA Framework page. For doing customization on a seeded page one has to be very careful. By doing customization we can add any of the required business logic to a seeded OA Framework page. To do customization we need to take the controller file attached with the OAF page (this file will be present in .class format in server) then we need to decompile the file and make necessary changes. Also remember that all the customizations done of a seeded OAF page will vanish once a patch or upgrade has been applied to the oracle apps instance. In order to save the customization work I suggest that you should create a copy of the original controller file with some name (say xxTrialPGCO) and then place the new file in the server. Once you put the new controller compiled file in the server, using personalization change the controller of the page from original controller file to xxTrialPGCO and save the personalization to a flat file.

Custom Pages: All the pages that are developed from scratch are called custom pages or bolt on pages. A page or a group of pages that perform a complete business operation is commonly called a Bolt-On Component or Custom Component. In order to create a custom page the developer should have clearly understood the MD50 and even the MD70 documents.

That’s all for this post.
Take Care

Testing OA Framework Applications

by

It’s always better to test the work that we have done before we submit the same to our senior level in our organization.
The oracle apps framework supports developer to test the application that he/she has created, there are a number of modes in which a developer can test his/her work.

The various number of test modes that OAF offers are
1. Developer test mode
2. Back Button test mode
3. Passivation test mode
4. Connection test mode

Before we start testing our work we should make sure that the FND:Diagnostics profile value is set to “YES” for our development environment so that we have the access to the error stack directly in our page whenever any unexpected error occurs. If the value for the FND:Diagnostics profile is set to “NO” then a generic error message will be displayed on the OAF page with no access to the error stack. While running the OA Framework pages in JDeveloper, enabling the Developer Test Mode, ensures that the developer will see a detailed error message if an exception is met.

Now, let’s discuss Developer test mode in detail.

1. Developer Test Mode: The developer test mode will check the code compliance with numerous coding standards.

Enabling the Developer Test Mode: Enabling of the Developer Test Mode can be done in 3 ways

a.Set the cookie value in test.jsp file e.g. setting the OADeveloperTestMode to 1 will ensure that the Developer Test Mode is on and the developer will be able to see the detailed error messages for unexpected exceptions. Whereas the 0 value for the OADeveloperTestMode ensures that the OADeveloperTestMode is turned off.

b.Set the FND:Developer Mode (FND_DEVELOPER_MODE) profile option mode to “YES”.

c.For Jdeveloper just shuttle the OADeveloperTestMode option from the list of Avaliable Options to Selected Options in the run options page in Project Settings.

To check if the OADeveloperTestMode is turned on or not you can call OAPageContext.isDeveloperTestMode, this returns 1 if the mode is on else 0.

I will discuss other test modes in next posts.
Till then
Keep Learning

How to Disable Submit Button in OA Framework?

by

Submit button is a very important component of every OAF page and there often arises a situation where an OA Framework technical personnel need to disable (not hide) OA Framework Submit Button dynamically.

We will learn today how to disable OA Framework Submit Button at runtime

Before we begin I assume that you have an OAF page (xxTrialPG) and a controller (xxTrialCO). Also I assume that you have created a submit button bean OASubmitButtonBean(xxTrialSubmitButton)

 

Let’s take this in steps for easy understanding.

Step 1: Import the OASubmitButtonBean bean in your controller xxTrialCO

import oracle.apps.fnd.framework.webui.beans.form.OASubmitButtonBean

 

Step 2: Create a handle or reference of the OASubmitButtonBean bean in controller

OASubmitButtonBean xxTrialSubmitButtonHandle = (OASubmitButtonBean) webBean.findChildRecursive(“xxTrialSubmitButton”);

 

Step 3: Now using the xxTrialSubmitButtonHandle handle created in step 2 we can disable the xxTrialSubmitButton

xxTrialSubmitButtonHandle.setDisabled(true);

 

And it’s done.
Thanks for Reading.