Tech Honey

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

How to handle the click of Submit Button?

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 handle the click of an OA Framework Submit Button dynamically.

We will learn today how to handle the click of Submit Button using OA framework code.

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

 

Note: The below code has to be written in the ProcessFormRequest method of the controller

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 capture the click of xxTrialSubmitButton

if(pageContext.getParameter(xxTrialSubmitButtonHandle!= null)

{
// perform required steps
}

 

And that’s it.
Thanks for Reading.

How to handle null value in OA Framework?

by

Well we may say that null means no value, but then on the other hand, each and every technical personnel needs to handle null value in their code, irrespective of the language that is used for coding purpose, and OAF is no exception.
So, how do we check a null value in OA framework? Well that’s very easy; just have a look at the following code.
Before we begin I assume that you have an OAF page (xxTrialPG) and a controller (xxTrialCO). Also I assume that you have created a string xxTrialString on which we will have the null value validation.

if(xxTrialString==null)
{
// your business logic goes here
}

Or you can also write

if(xxTrialString!==null)
{
// your business logic goes here
}


And it is handled.. so simple isn’t it.
Thanks for Reading.

How to call an OAF page from another OAF page with parameters?

by

Well, this is a very frequent requirement that OA Framework often have to fulfill and it’s really not very difficult to achieve.

In this post we deal with the calling of an OAF page when we have to pass parameter(s) from the calling OAF page to called OAF page

Here I assume that
A. We already have created one OAF page xxTrialCallingPG which will be the calling page
B. The location of the xxTrialCallingPG is /oracle/apps/demo/calling/xxTrialCallingPG
C. We already have created one more OA Framework page xxTrialCalledPG which will be called
D. The location of the xxTrialCalledPG is /oracle/apps/demo/called/xxTrialCalledPG
E. We have a controller attached to xxTrialCallingPG as xxTrialCallingCO

In order to pass parameters from xxTrialCallingPG to xxTrialCalledPG, we shall put these parameters in a HashMap using the code mentioned below.

HashMap xxTrialHashMap = new HashMap();
xxTrialHashMap.put(paramName1,paramValue1);
xxTrialHashMap.put(paramName2,paramValue2);

and so on.

Now, depending upon our business logic we can write the following code in the processFormRequest() method of xxTrialCallingCO

pageContext.setForwardURL(“OA.jsp?page=/oracle/apps/demo/called/xxTrialCalledPG”,// page name with complete path or called as target page
null, // not necessary with KEEP_MENU_CONTEXT
OAWebBeanConstants.KEEP_MENU_CONTEXT, // no change to menu context
null, // No need to specify since we’re keeping menu context
xxTrialHashMap, // request parameters
true, // Retain AM
OAWebBeanConstants.ADD_BREAD_CRUMB_YES, // Show breadcrumbs
OAWebBeanConstants.IGNORE_MESSAGES);

And that’s done. Whenever the business logic gets fired, xxTrialCalledPG will be called from xxTrialCallingCO of xxTrialCallingPG.

Thanks for Learning.

How to call an OAF page from another OAF page without parameters?

by

Well, this is a very frequent requirement that OA Framework often have to fulfill and it’s really not very difficult to achieve.

In this post we deal with the calling of an OAF page when we don’t have to pass any parameter(s) from the calling OAF page to called OAF page

Here I assume that
A. We already have created one OAF page xxTrialCallingPG which will be calling page
B. The location of the xxTrialCallingPG is /oracle/apps/demo/calling/xxTrialCallingPG
C. We already have created one more OA Framework page xxTrialCalledPG which will be called
D. The location of the xxTrialCalledPG is /oracle/apps/demo/called/xxTrialCalledPG
E. We have a controller attached to xxTrialCallingPG as xxTrialCallingCO

Now, depending upon our business logic we can write the following code in the processFormRequest() method of xxTrialCallingCO

pageContext.setForwardURL(“OA.jsp?page=/oracle/apps/demo/called/xxTrialCalledPG”,// page name with complete path or called as target page
null, // not necessary with KEEP_MENU_CONTEXT
OAWebBeanConstants.KEEP_MENU_CONTEXT, // no change to menu context
null, // No need to specify since we’re keeping menu context
null, // request parameters
true, // Retain AM
OAWebBeanConstants.ADD_BREAD_CRUMB_YES, // Show breadcrumbs
OAWebBeanConstants.IGNORE_MESSAGES);

And that’s done. Whenever the business logic gets fired, xxTrialCalledPG will be called from xxTrialCallingCO of xxTrialCallingPG.

Thanks for Learning.

Form Value in OAF

by

Whenever there are instances that a value has to be used in an OAF page but the same value is not supposed to be displayed to the end-user, we have to make use of formValue bean.

In Oracle Apps Framework the formValue bean is used to store a value that will be submitted with a form, but the key point to mention is that value is not displayed to the user.

I assume that the creation and mapping of formValueBean’s “ViewName” and formValueBean’s “ViewAttribute” property has already been done at design time as follows.

Id of formValueBean: xxTrialFormValueBean
Name of VO: xxTrialVO
VOAttribute: xxTrialVOAttribute

As soon as that View Object is executed the formValue get’s the value of the mapped attribute.

Now, suppose you want to get the value that has been set to the formValue we can have the following steps.

1. Import the formValueBean in Controller (xxTrailCO)

import oracle.apps,fnd.framework.webui.beans.form.OAFormValueBean;

2. Create handle of the formValueBean

OAFormValueBean xxTrialFormValueBeanHandle = (OAFormValueBean)webBean.findChildRecursive(xxTrialFormValueBean);

3. getValue from the formValueBeanHandle by converting the same to String

String xxTrialFormValueString = xxTrialFormValueBeanHandle.getValue(pageContext);

Now, you can use this value as per your business logic.
Thanks for Reading