Tech Honey

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

Items

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.

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

Export Button Item in OA Framework

by

In Oracle Application Framework the ExportButton is used to:

Export the displayed data of a particular region or for all regions on an OAF page to a comma separated value (csv) file.
o Only the regions that are displayed on the OA Framework will be exported.
o Each region on the exported file will have a row of column names followed by the results.

In Windows:

Clicking on the ExportButton will open a dialog according to which
o You can open the exported file and then save the same, or,
o You could save the file and then open it.

exportButton can be used as follows:

1. Exporting the data of all regions on a page.
2. Exporting data of a specific region on a page.

1. Exporting the data of all regions on a page:
A. Create a contentFooter region under the pageLayout region of that OAF Page.
B. Add an “ExportButton” to the contentFooter region.
C. If there is more than one button which needs to be added to the contentFooter, then all the buttons should be put under a flowLayout region, and this flow layout should then be added to the contentFooter.

2. Exporting data of a specific region on a page:
A. Create an “ExportButton” under the region whose data needs to be exported.
B. Now, in the container object, position this ExportButton and set a view usage name for this ExportButton. The data of the attached VO will be exported to a CSV file.

It extends the OA Framework’s submitButton and inherits all the properties from it.

Corresponding web bean: OAExportBean

Import Path: import oracle.apps.fnd.framework.webui.beans.form.OAExportBean;

Flex Field Item in OA Framework

by

Oracle Application has two types or styles of flex item styles. In other words you can say that there are two types of flex fields in Oracle Application, they are:

1. Descriptive flex field.
2. Key flex field.

1. Descriptive flex fields: It provides a customizable “expansion space” which can be used to track additional information, important and unique to a customer’s business, which would not otherwise be captured by the form.
2. Key flex fields: They are the key building block for the business group and are made up of meaningful segments identifying business entities like Position, Job, and Grade etc.

By using flex item style, we create the complete structure of key flex field and descriptive flex field as it is declared in Oracle Applications.

Corresponding web beans: OADescriptiveFlexBean, OAKeyFlexBean

import oracle.apps.fnd.framework.webui.beans.OADescriptiveFlexBean;

import oracle.apps.fnd.framework.webui.beans.OAKeyFlexBean;

Formatted Text in OA Framework

by

You may have guessed from the name itself that a formattedText item style will accept a string. In OAF the FormattedText accepts the string in one of its attribute named as “Text” and contains a very limited set of HTML markup and outputs formatted results.

Oracle Apps Framework developers, who need more of HTML functionality must use the rawText bean. E.g. formattedText bean won’t support the use of HTML tables or HTML links; hence OAF developers have to use either tableLayout and link beans or use just the rawText bean.

formattedText bean provides a limited ability to use a single source for translated or user-provided FormattedText without parsing or filtering. It supports more attributes than the rawText bean; e.g. it supports styleClass.

HTML markups supported by FormattedText are:

br
hr
li
ol
ul
p
b
i
tt
big
small
pre
span
a

Also the FormattedText supports the following entities:

< >
&
?
?
”
In the CSS attributes “class”, “style” and “href” are the only attributes that are supported; all the other CSS attributes others are ignored.
Corresponding web bean: OAFormattedTextBean
Import Path: import oracle.apps.fnd.framework.webui.beans.OAFormattedTextBean;