Using Oracle Forms I know…

And in OA Framework…

With Oracle Forms I can create custom Apps modules and modify seeded Apps Forms.

JDeveloper is the development tool for creating custom Apps web pages and modifying seeded Apps web pages.

Using Oracle Forms I know…

And in OA Framework…

I use TEMPLATE.fmb as the starting point for any custom Apps forms.  TEMPLATE.fmb contains references to libraries, property settings, and menus that will help make custom forms look-and-feel like Oracle-provided forms.

OA Framework is a development and deployment platform presented through JDeveloper.  The seeded objects and settings give custom web pages the same look-and-feel as Oracle-provided web pages

Using Oracle Forms I know…

And in OA Framework…

I use SQL and PL/SQL in Oracle Forms

We will still use SQL statements, specifically in View Objects.  We can execute PL/SQL, but within Java code.  If you’re Java skills are nil or weak, now might be a good time to plan a training program.  See What To Do Next for more information.

Using Oracle Forms I know…

And in OA Framework…

An Oracle Forms file (.fmb) contains screen design and custom procedures and functions.

Reusable code, that’s the mantra for JDeveloper and OA Framework.  In Oracle Forms a data block references a table or view, and that definition is contained within the .fmb.  With JDeveloper, we create view objects or entity objects that can be reused by other web pages.

Using Oracle Forms I know…

And in OA Framework…

I can use triggers (e.g. Key-Next-Item) in Oracle Forms to validate data.

Web pages developed within the OA Framework do not have triggers.  Validation takes place after a user completes a page, or portion of a page, and submits that page to the server.

Using Oracle Forms I know…

And in OA Framework…

In Forms, I can reuse forms, libraries, and menus by referencing.

OA Framework is an assembly of reusable objects.

Using Oracle Forms I know…

And in OA Framework…

In Forms I create and use canvases:

*Forms requires a root canvas

*I use stacked canvases for controlling access to groups of items

*Fields and buttons appear on a canvas

*Properties control the appearance of canvases and items

In OA Framework we use the concept of a region:

*A web page requires a root region

*Regions can be nested

*Widgets (fields, buttons, images, etc) appear in a region

* Properties control the appearance of widgets