Tech Honey

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

How to handle add more rows event in Advanced Table in OAF?

by

Well handling the add_rows_event is a bit peculiar but important requirement and we are going to learn how to achieve the same 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 an Advanced Table OAAdvancedTableBean(xxTrialAdvancedTable).

Let’s take this in steps for easy understanding.

Step 1: Import the OAAdvancedTableBean in your controller

import oracle.apps.fnd.framework.webui.beans.table.OAAdvancedTableBean

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

OAAdvancedTableBean xxTrialAdvancedTableHandle = (OAAdvancedTableBean) webBean.findChildRecursive(“xxTrialAdvancedTable”);

Step 3: Now using the xxTrialAdvancedTableHandle handle created in step 2 we can capture the add_row_event on xxTrialAdvancedTable.


if (xxTrialAdvancedTableHandle.getName(pageContext).equals(pageContext.getParameter(SOURCE_PARAM))
&& ADD_ROWS_EVENT.equals(pageContext.getParameter(EVENT_PARAM)))
{
// perform required steps
}

< em>

Mission Accomplished 

Thanks for Reading.
Until next post
Keep Learning 🙂

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;

Form Paramter in OA Framework

by

In Oracle Apps Framework the formParameter item style provides the functionality to act as a placeholder for submission parameters. Suppose you want a user to fill his credit card details and then you want to call a payment gateway by passing his credit card information, then you will use the formParameter bean to hold the values of the credit card filled by the user in the OAF page.

Oracle Application Framework also provides the formValue bean for holding the values, but there are differences between formParameter and formValue beans of OAF, these are listed below.

1. formParameter won’t support a “value” attribute. Instead, the value is set only at form submission time.
2. A formParameter with a particular name can be added N number of times to a form without ill effects; only one instance will appear. This is noticeably different from the formValue, where reuse will cause the same value to appear multiple times in the form submission.

Corresponding web bean: OAFormParameterBean

ImportPath: import oracle.apps.fnd.framework.webui.beans.form.OAFormParameterBean;