4 Converting an Oracle Forms Application

This section describes the steps to convert applications from Oracle Forms to Oracle Application Express.

4.1 How to Convert Your Application

To convert applications from Oracle Forms to Oracle Application Express, you must perform the steps described in this section in the exact sequence in which they are presented.

4.1.1 About the Process of Converting Oracle Forms

The following illustration outlines the entire process of converting applications from Oracle Forms to Oracle Application Express.

Description of forms_to_apex.gif follows
Description of the illustration forms_to_apex.gif

The conversion process consists of the following steps:

Important:

You must follow the steps in the exact sequence presented in this section.

4.2 Converting Oracle Forms to XML

In order to convert Oracle Forms to Oracle Application Express, you must convert the Forms modules to formats the Create Migration Project wizard can consume.

4.2.1 Converting FormModules, ObjectLibraries, or MenuModules to XML

You can convert Oracle Forms FormModule, MenuModule, and ObjectLibrary files to Extensible Markup Language (XML) using the Oracle Forms to XML conversion tool, Forms2XML.

Note:

The Forms2XML utility must generate an XML file in English only. If the generated XML tags are not in English, then the file will fail to load. The conversion of synonym-based data blocks is not supported. Only data blocks based on tables or views is supported by the conversion process. Please ensure that the application you want to convert is based only on tables and views.

4.2.1.1 About the Forms2XML Conversion Tool

The Oracle Forms to XML conversion tool, Forms2XML was introduced in Oracle9i Oracle Developer Suite and is also available in Oracle Developer Suite 10g. This tool should also work on files from earlier releases of Oracle Forms. If the Oracle Forms to XML Conversion tool does not work for a specific file from an earlier version of Oracle Forms, then you must upgrade the file to Oracle Developer Suite 9i or 10g and then convert to XML

Forms2XML produces an XML file that has the same base name as the Forms file with an .xml extension. The extension _fmb, _mmb, or _olb is added to the base file name to indicate whether the original file was a Forms Modules, a MenuModule, or an Object Library. The following table displays a few examples of the changes the tool makes to the name of the file being converted:

File name before conversion File name after conversion
myForm.fmb myForm_fmb.xml
myMenu.mmb myMenu_mmb.xml
myLibrary.olb myLibrary_olb.xml

4.2.1.2 Using the Forms2XML Conversion Tool From a Command Line

The Forms2XML command takes one or more Forms Module files as an argument. The files can be FormsModule (.fmb), ObjectLibrary (.olb), or MenuModule (.mmb) files. The output is placed in the current folder. The command has the following syntax:

frmf2xml [options] file1 [file2...]
java oracle.forms.util.xmltools.Forms2XML [options] file1 [file2...]

The following table describes available options.

Options Description
USE_PROPERTY_IDS=YES/NO Setting USE_PROPERTY_IDS to YES causes the Forms to XML conversion tool to write the internal ID for Real or Character into the XML file.

The default value (NO) generates property value names as before.

Note: The Forms2XML utility must be run with USE_PROPERTY_IDS=NO.
OVERWRITE=YES/NO Valid values are YES or NO.

If OVERWRITE=YES, the tool overwrites any XML files with the same name that exist in the output directory.

If OVERWRITE=NO, (default) the tool does not overwrite any XML files with the same name that exist in the output directory. The tool will stop processing and return the message:

If the file file 1 exists, use argument OVERWRITE=YES to replace.
DUMP=ALL/OVERRIDEN If DUMP=ALL, the tool dumps all properties.

If DUMP=OVERRIDEN, the tool dumps only those properties that are overridden.

4.2.1.3 Using the Forms2XML Conversion Tool in a Java Program

You can pass the Forms2XML tool a JdapiModule Java object (class oracle.forms.jdapi.JdapiModule) and dump its objects and properties to an XMLDocument (class oracle.xml.parser.v2.XMLDocument). For example:

...
 // get the modules in the session
 JdapiIterator mods = Jdapi.getModules(); 
    // ... and iterate round them 
    while(mods.hasNext())
      {
        JdapiModule mod = (JdapiModule)mods.next();
        Forms2XML converter = new Forms2XML(
        XMLDocument doc = converter.dumpModule(false);
              ... 
       }

The Boolean argument taken by the dumpModule() method instructs the converter to dump all properties to the XMLDocument doc, not just those which are overridden.

Once you have the module as an XMLDocument object, you could then use the XDK classes to manipulate it programmatically. For example, you could traverse it, remove or add objects, change properties, copy objects into other modules that are also saved as XMLDocument objects, and so on.

To learn more about Oracle Forms, see:

http://www.oracle.com/technetwork/developer-tools/forms/overview/index.html

4.2.2 Converting a PL/SQL Library

To convert a PL/SQL library, use the File > Convert option in Oracle Forms Builder to convert PL/SQL library .PLL files to .PLD text files.

To learn more about Oracle Forms, see:

http://www.oracle.com/technetwork/developer-tools/forms/overview/index.html

4.2.3 Converting an Oracle Report to XML

To convert an Oracle Report, use the File Conversion option in Reports Builder to convert binary (.RDF), ASCII (.REX), and .JSP reports to XML format.

To learn more about Oracle Reports, see:

http://www.oracle.com/technetwork/middleware/reports/overview/index.html

4.3 About Creating a Workspace and Adding Oracle Application Express Users

You access the Oracle Application Express home page by logging in to a workspace using a JavaScript enabled Web browser. A workspace enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data, and applications private. Each workspace has a unique ID and name.

An instance administrator can create a workspace manually within the Oracle Application Express Administration Services application or have users submit requests. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance.

Tip:

Functionality in the Administration Services application is not available in Oracle Database Cloud Service (Database Schema).

See Also:

"Creating a Workspace and Adding Oracle Application Express Users" for your Web listener in Oracle Application Express Installation Guide.

4.4 Uploading Database Objects into the Schema Associated with Your Workspace

In order to start the conversion process, the database objects associated with your Oracle Forms application must reside in the same database as Oracle Application Express.

If the database objects associated with your Oracle Forms application do not reside in the same database as Oracle Application Express, you must upload them.

To upload database objects associated with your workspace:

  1. Create a DDL script.

  2. Upload it to the SQL Script Repository and run it.

See Also:

"Executing a SQL Script" in Oracle Application Express SQL Workshop Guide.

4.5 Creating a Conversion Project

Next, create a conversion project by running Create Migration Project Wizard and loading the application metadata extracted in "Converting Oracle Forms to XML".

To create a conversion project:

  1. Access the workspace you created for your conversion project.

  2. Click the Application Builder icon.

  3. Click Migrations on the right side of the page.

  4. On the Application Migrations page, click Create Project.

    The Create Migration Project wizard appears. The steps included in the wizard appear in a flowchart on the left of the page.

  5. Enter the project details:

    1. Project Name - Enter a unique name. The project name must be unique to your current workspace and should not contain any white spaces.

    2. Type - Select Forms.

    3. Description - Enter a meaningful description for this project.

    4. Schema - Select the schema that contains the database schema objects associated with the Oracle Forms application you want to convert.

      The default schema is the schema associated with your workspace. If multiple schemas are associated with your workspace, all associated schemas appear in the select list, arranged in alphabetical order. When this situation exists, select the schema associated with the Oracle Forms you want to upload.

    5. Forms Module XML File - Locate the XML file which contains the information of your converted Oracle FormModule (for example, myForm_fmb.xml).

      Note that you must upload the converted Oracle FormModule file first.

    6. Click Next.

      The Confirm page appears.

    7. To add more files, click Upload Another File.

  6. To upload a file, specify the following:

    1. File Type - Select the appropriate file type. Options include:

      • Forms Module - Upload a FormModule in XML format (myForm_fmb.xml). Use the Forms2XML conversion tool to convert Oracle FormModule .FMB files to .XML format.

      • Oracle Report - Upload an Oracle Report in XML format (myReport.XML). Use the File Conversion option in Oracle Reports Builder to convert binary (.RDF), ASCII (.REX), and .JSP Reports to XML format.

      • PL/SQL Library - Upload a PL/SQL Library associated with your Oracle Forms application (myLibrary.PLD). The library must be in text format. Use the File > Convert option in Oracle Forms Builder to convert PL/SQL library .PLLs to .PLD text files.

      • Forms Menu - Upload an Oracle Form Menu in XML format (myMenu_mmb.XML). Use the Forms2XML conversion tool to convert MenuModule .MMB files to .XML format.

      • Object Library - Upload an Object Library in XML format (myObjects_olb.XML). Use the Forms2XML conversion tool to convert Object Library .OLB files to .XML format.

    2. File - Locate the file you want to upload.

    3. Click Upload.

      The Confirm page appears.

  7. To add more files, click Upload Another File and repeat the previous steps until all files appear on the Confirm page.

  8. Review the project details, and click Create.

    The Project page appears.

4.6 Reviewing and Editing Forms Metadata

Next, use the Project pages to review and edit form attributes and track the manual conversion process.

4.6.1 Understanding the Application Migrations Page

The Project page shows a high-level overview of your Oracle Forms conversion project.

4.6.1.1 Using the Project Page

This section describes how to use the Project page.

4.6.1.1.1 Viewing Project Details

To view project details, click the project name. The Project page appears.

With the exception of the File Name column, most of the information on the Project page only applies to FormModule XML files (for example, Blocks, Triggers, and Program Units columns). If a column does not apply to the uploaded file, a 0 displays.

The Project page lists the following information about uploaded files:

  • Type - Identifies the type uploaded by displaying the appropriate file extension (for example, RPT for Report and FMB for FormModule files).

  • File Name - Displays the file name and extension (XML or TXT) uploaded into the project.

  • Blocks - Displays a count of blocks in FormModule XML file. A single block can be mapped to a region in Oracle Application Express. A region is an area on a page that serves as a container for content. Each page can have any number of regions. You control the appearance of a region through a specific region template.

  • DB Blocks - Displays the database data blocks in the uploaded FormModule XML file. These blocks can be based on any of the following block data source types: table; procedure; transactional trigger; or subquery. Blocks included in the DB Blocks count are not control blocks. Note that the associated Database Block property is set to Yes.

  • Triggers - Displays a count of all form-level, block-level and item-level triggers associated with the uploaded FormModule XML file.

  • Record Groups - Displays a count of Record Groups in the uploaded FormModule XML file.

  • Lists of Values - Displays a count of lists of values (LOVs) in the uploaded FormModule XML file.

  • Alerts - Displays a count of alerts in the uploaded FormModule XML file.

  • Program Units - Displays the number of schema objects that enable you to access and manipulate database information.

You can review Forms attributes and track manual conversion by clicking the links on this page.

4.6.1.1.2 Utilizing Interactive Reports

Many pages in Application Migration Workshop display as interactive reports. You can customize the appearance of these pages using the Search bar at the top of each page.

Use the Search bar to create custom searches and customize and filter the information that appears on the page.

Available controls on the Search bar include:

  • Select columns to search icon - Resembles a magnifying glass. Click this icon to narrow your search to specific columns. To search all columns, select All Columns.

  • Text area - Enter case insensitive search criteria (wildcard characters are implied) and then click Go.

  • Go button - Executes a search.

  • Actions menu - Use the Actions menu to customize an interactive report.

To learn more, see "Using Interactive Reports" in Oracle Application Express End User's Guide.

4.6.1.1.3 Upload File, Create Application, and Run Application Buttons

Three buttons display to the above of the Search Bar:

  • Upload File - Add files to your conversion project. See "Uploading Additional Files".

  • Create Application - Create an Oracle Application Express application based on the components included in your conversion project. See "Generating the Oracle Application Express Application".

  • Run Application - Submit the pages within your Oracle Application Express application to the Application Express engine and render viewable HTML. Note this button only appears after you generate an application.

4.6.1.1.4 About Associated Application

The Associated Application only displays after you create an application. This region displays application name, number of application pages, last update date, and the user who performed the updates. Click the application name to link to the Application home page within Application Builder.

4.6.1.1.5 Tasks List

The Tasks list displays on the right side of the page and contains the following links:

  • Delete Project deletes the current project.

  • Edit Project Details and Applicability links to the Project Details page. See "Editing Project Details."

  • About Forms Conversion links to a page that explains how to convert Oracle Forms applications.

  • Set Application Defaults links to the Set Application Defaults page. See "Setting Up Application Defaults."

4.6.1.1.6 Completion Status Region

A Completion Status box displays on the right side of the page and contains the following information:

  • Components - Lists the number of components that have been uploaded to the project.

  • Completed - Displays a count of components within the conversion process that have been reviewed and have been marked as Complete.

  • Percent Complete - Lists percent of components which have been marked as Complete.

4.6.1.2 Uploading Additional Files

To add files to your conversion project:

  1. From the Application Migrations page, click the project name.

  2. On the Project page, click Upload File.

  3. For File Type, select one of the following:

    • Forms Module - Upload a FormModule in XML format (myForm_fmb.xml). Use the Forms2XML conversion tool to convert Oracle FormModule .FMB files to .XML format.

    • PL/SQL Library - Upload a PL/SQL Library associated with your Oracle Forms application (myLibrary.PLD). The library must be in text format. Use the File > Convert option in Oracle Forms Builder to convert PL/SQL library .PLLs to .PLD text files.

    • Oracle Report - Upload an Oracle Report in XML format (myReport.XML). Use the File Conversion option in Oracle Reports Builder to convert binary(.RDF), ASCII (.REX), and .JSP Reports to XML format.

    • Object Library - Upload an Object Library in XML format (myObjects_olb.XML). Use the Forms2XML conversion tool to convert Object Library .OLB files to .XML format.

    • Forms Menu - Upload an Oracle Form Menu in XML format (myMenu_mmb.XML). Use the Forms2XML conversion tool to convert FormsMenu .MMB file to .XML format.

  4. File - Locate the file you want to upload.

  5. Click Upload.

    The Confirm page appears.

  6. To add more files, click Upload and Upload Another and repeat the previous steps until all files appear on the Confirm page.

  7. Review the file details, and click Finish.

    The Project page appears.

4.6.2 Editing Project Details

To edit project details.

  1. From the Application Migrations page, click the project name.

  2. On the Project page, click the Edit icon to access the Project Details page. The Edit icon resembles a small yellow pencil.

    The Project Details page appears.

  3. Under Project Details, edit the project name, database schema, specify an associated application, or enter an optional description.

  4. Under Component Applicability, specify whether to include specific components in your conversation project. Select Yes or No adjacent to each component type.

    See Also:

    "Using Annotations to Track the Conversion Process"

  5. Click Apply Changes.

4.6.3 Reviewing Forms Modules

From the Project page you can browse the objects included in your uploaded Oracle FormModule XML file (for example, myForm_fmb.xml).

See Also:

"Oracle Forms Generation Capabilities and Workarounds"

4.6.3.1 Viewing an Imported FormModule

To view an imported FormModule:

  1. From the Application Migrations page, click the project name.

  2. Click the Edit icon to the left of the XML file name (for example, myForm_fmb.xml).

    The Form Details page appears.

  3. To delete an imported FormModule, click Delete.

  4. To download the files associated with this project, click Download.

About Annotations

Use Annotations to track the overall status of form components within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.3.2 Viewing Object Metadata and Selecting Specific Objects

To review object metadata:

  1. From the Application Migrations page, click the project name.

  2. Click the number under the column for the appropriate object type. Alternately, click the File Name to view a report describing the component.

    Clicking a number displays a listing of the object type.

  3. To include blocks, items, and LOVs select the Include check box adjacent to the object name and click Apply Changes.

  4. To view details about a specific object, click the object name or Edit icon.

4.6.3.3 Understanding Viewing and Selecting Blocks

To review blocks:

  1. From the Application Migrations page, click the project name.

  2. Click the link under the Blocks column.

    A listing of blocks appears.

    Tip:

    To displays columns not displayed by default, click the Actions menu and select Select Columns. To learn more, see "Using Interactive Reports" in Oracle Application Express End User's Guide.

  3. To edit a block name, enter a new name in the Title field and click Apply Changes.

  4. To include a specific object in your conversion select the Include check box adjacent to the object name and click Apply Changes.

  5. To view details about a specific object, click the Name link.

    The Block Details page appears. The sections that follow describe each section of the Block Details page.

4.6.3.3.1 About Block Details

Lists the details about the block.

4.6.3.3.2 About Annotations

Tracks the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.3.3.3 About Application Express Page Query

Oracle Forms can be based on database blocks which correspond to database tables or views. The enhanced query builds a query based on the database block and database item metadata, and extends it with block level post-query trigger source to show derived columns

Enhanced Query is the original query with the POST-QUERY logic included. Original Query is generated from the data source item (table) underlying the block and the columns that are referenced on that block

To specify the type of query to use:

  1. Select one of the following from the User Query list:

    • Custom Query

    • Enhanced Query

    • Original Query

  2. If you select Custom Query, enter the appropriate syntax in the Custom Query field.

  3. Click Apply Changes.

4.6.3.3.4 Relation Details

Only displays if a relationship was identified for the block in the XML file. This section displays the information on that relationship.

4.6.3.3.5 Block Items

Displays the items in the block. Click the Edit icon associated with the item to view item details.

4.6.3.3.6 Block Triggers

Lists the block-level and item-level triggers associated with the block. Click Edit icon to view additional trigger details.

4.6.3.3.7 About Audit

Display or hide the Audit section at the bottom of the page to view details about the object creation and last update dates.

4.6.3.4 Viewing and Selecting Items

To review items:

  1. From the Application Migrations page, click the project name.

  2. Click the link under the Items column.

    A listing of items appears. Click the Actions icon on the Search bar to view additional information which is not visible in the default report.

  3. To edit an item label, enter a new name in the Item Prompt field and click Apply Changes.

  4. To include a specific object in your conversion select the Include check box adjacent to the object name and click Apply Changes.

  5. To view details about a specific item, click the Item Name link.

    The Item Details page appears. The sections that follow describe each section of the Item Details page.

4.6.3.4.1 About Item Details

Lists the details about the item.

4.6.3.4.2 About Annotations

Tracks the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.3.4.3 About Audit

Display or hide the Audit section at the bottom of the page to view details about the object creation and last update dates.

4.6.4 Reviewing Oracle Reports

From the Project page you can browse uploaded Oracle Report XML files (for example, myReport.XML).

Topics

4.6.4.1 Viewing Reports

Use the Report Details page to view details about the imported report.

To view the Report Details page:

  1. From the Application Migrations page, click the project name.

  2. Click the Oracle Reports XML file name (for example, myReport.XML).

    The Report Details page appears.

  3. To delete the report, click Delete.

  4. To download the report, click the Download link.

    The sections that follow describe the Report Details page.

4.6.4.1.1 Report Details

Lists details about the current report.

4.6.4.1.2 About Annotations

Use Annotations to track the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.4.1.3 About SQL Query

Displays the SQL query associated with the Oracle Report. This SQL statement is used to generate an Oracle Application Express interactive report.

4.6.4.1.4 About Data Items

Lists each item in the report. Click the Edit icon adjacent to a specific item to display the Data Item Details page.

4.6.4.1.5 About Summary Items

Lists the summary columns associated with the report. These columns perform a computation on another column's data (for example, sum, average, count, minimum, maximum, and percent total).

To learn more about Oracle Reports, see the following hosted Help file:

http://www.oracle.com/technetwork/middleware/reports/overview/index.html
4.6.4.1.6 About Audit

Display or hide the Audit section at the bottom of the page to view details about the creation and last update dates.

4.6.4.2 Selecting Reports to Include

Use the Reports page to select reports for inclusion in the conversion process.

To view the Report page:

  1. From the Application Migrations page, click the project name.

  2. Click the Edit icon to the right of the Oracle Reports XML file name (for example, myReport.XML).

    The Reports page appears.

  3. To include a report, select the check box and click Apply Changes.

4.6.5 Reviewing PL/SQL Libraries

From the Project page you can browse uploaded PL/SQL libraries associated with your Oracle Forms application (for example, myLibrary.PLD) and update annotations. Note that PL/SQL libraries are not generated within Oracle Application Express. However, the files are imported to enable you to review and track them.

To view the PL/SQL Library Details page:

  1. From the Application Migrations page, click the project name.

  2. Click the PL/SQL library XML file name (for example, myLibrary.PLD).

    The PL/SQL Library Details page appears.

  3. To delete the library, click Delete.

  4. To download the library, click the Download link.

4.6.5.1 About Annotations

Use Annotations to track the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.5.2 About Audit

Display or hide the Audit section at the bottom of the page to view details about the object creation and last update dates.

4.6.6 Reviewing Forms Menus

From the Project page you can browse the objects included in your uploaded MenuModule XML file (for example, myMenu_mmb.XML) and update annotations. Note that Forms Menus are not generated within Oracle Application Express. However, the files are imported to enable you to review and track them.

Topics

4.6.6.1 Viewing Form Menus

To track an imported MenuModule:

  1. From the Application Migrations page, click the project name.

  2. Click the Edit icon to the left of MenuModule XML file name (for example, myMenu_mmb.XML).

    The Edit Imported Form Menu page appears.

  3. To delete the MenuModule, click Delete.

  4. To download the MenuModule, click the Download link.

4.6.6.1.1 About Annotations

Use Annotations to track the overall status of form within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.6.2 Viewing a Summary of Forms Menus

Use the Forms Menus page to view details about specific modules.

To view the Forms Menus page:

  1. From the Application Migrations page, click the project name.

  2. Click the MenuModule XML file name (for example, myMenu_mmb.XML).

    The Forms Menus page appears and displays the following information:

    • Edit icon - Depending on the Module Type, clicking this icon displays a details page describing the selected menu or program unit.

    • Name - Display the name of the menu module.

    • Module Type - Lists the type of module (that is, either Menu or Program Unit).

    • File Size - Displays the XML file size in kilobytes (KB).

    • Module Name - Displays the name of the module.

    • Main Menu - Specifies the name of the individual menu in the Forms Menu that functioned as the main or starting menu at runtime.

    • Assignee - Displays the person responsible for an object as specified within the Annotations for the object.

    • Tags - Lists tags created to describe the object as specified within the Annotations for the object.

    • Notes Snippet - Displays a snippet of the Notes specified within the Annotations for the object.

    • File Name - Displays the MenuModule XML file name.

  3. To view module details, click the Edit icon adjacent to the menu name.

    A details page appears. See the next section, "Viewing Form Menu and Program Unit Details".

4.6.6.3 Viewing Form Menu and Program Unit Details

Clicking the Edit icon on the Forms Menus page displays a details page. The format of the page that displays depends upon the Module Type (either Menu or Program Unit).

4.6.6.3.1 About Form Menu Details

The top of the page lists details about the menu, including

  • Name

  • Parent Module

  • Parent Name

  • Parent Type

  • Tear Off Menu

  • Comment

Under Menu Items, click the Edit icon to view details or track the status of a specific menu item.

See Also:

To learn more about Oracle Forms, see: 
http://www.oracle.com/technetwork/developer-tools/forms/overview/index.html
4.6.6.3.2 About Annotations

Use Annotations to track the overall status of an object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.6.3.3 About Program Unit Details

The top of the page displays the program unit name, type, and the actual program unit text (if applicable).

4.6.6.3.4 About Audit

Display or hide the Audit section at the bottom of the page to view details about the object creation and last update dates.

4.6.7 Reviewing Object Libraries

From the Project page you can browse uploaded Object Libraries associated with your Oracle Forms application (for example, myObjects_olb.XML) and update the annotations. Note that Object Libraries are not generated within Oracle Application Express. However the files are imported to enable you to review and track them.

To view the Forms Object Library details:

  1. From the Application Migrations page, click the project name.

  2. Click the Edit icon to the left of the Object Library XML file name (for example, myObjects_olb.XML).

    The Object Library Details page appears.

4.6.7.1 About Annotations

Use Annotations to track the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.7.2 About Audit

Display or hide the Audit section at the bottom of the page to view details about the creation and last update dates.

4.6.7.3 Viewing an Uploaded Object Library

To view the Forms Object Library page:

  1. From the Application Migrations page, click the project name.

  2. Click the Object Library XML file name (for example, myObjects_olb.XML).

    The Forms Object Library page appears.

  3. To view details about a specific attribute, click the Edit icon. A Details page appears.

4.6.7.3.1 About Annotations

Use Annotations to track the overall status of the object within the conversion process. To learn more, see "Using Annotations to Track the Conversion Process".

4.6.7.3.2 About Audit

Display or hide the Audit section to view details about the creation and last update dates.

4.6.8 Using Annotations to Track the Conversion Process

Use Annotations to track the overall status of an object within the conversion process. Most detail pages that describe a specific object include an Annotations section. Use Annotations to determine whether an object should be included in the conversion, assign a priority, track status, assign the object to specific individual, or create notes and tags.

Options include:

  • Applicable - Tracks whether the object is applicable within the context of the generated Oracle Application Express application. Select Yes or No.

    The initial value is determined by the applicability default settings for that component or trigger defined on the Project Details page.

  • Priority - Assign a numeric priority to the object.

  • Complete - Track if the conversion is complete. Select Yes or No.

  • Assignee - Assign the object to a specific user.

  • Notes - Enter notes regarding the object.

  • Tags - Assign tags to the object.

The values defined in Applicable and Complete are used in determining the percentage complete. All the Applicable and Complete values can be changed for a simultaneously from the Bulk Changes page.

4.6.8.1 Why Use Annotations?

Because Oracle Forms have many separate components, it is important to evaluate whether functionality in the original application is either not required or has been replicated in the Oracle Application Express application. Given that the initial design only incorporates a percentage of the required functionality, you can use these fields as a reminder of what must be implemented post-generation.

4.7 Generating the Oracle Application Express Application

After you have reviewed and updated the Oracle Forms metadata within your conversion project, you need to generate the application in Oracle Application Express.

4.7.1 About Generating the Oracle Application Express Application

When you create an application, a home page is defined by default. You have the option to create additional blank pages so that you can introduce further navigation possibilities. You can then choose which user interface theme your application should be based on. By default, the application uses one level of tabs.

4.7.2 Setting Up Application Defaults

As a shortcut, you can also set some application defaults. These defaults are used whenever you create new applications.

To set up application defaults (optional):

  1. On the right side of the project page under Tasks, click Set Application Defaults.

  2. Select the options you want to use as defaults.

    To learn more about a specific attribute, see field-level help.

  3. Click Apply Changes.

    The project page appears.

4.7.3 Creating an Application

You can generate an application based on valid forms and reports, or a maintenance application based on valid tables and views.

To generate an application:

  1. On Application Migrations page, click the project name.

  2. Click Create Application.

    The Generate Application wizard appears.

  3. On Generate Application:

    1. Name - Enter a name to identify the application to developers. The default value is taken from the migration project name.

    2. Create Application - Select a method:

      • Based on Migration Project - Select this option to manually enter all pages.

      • Based on existing application design model - Select this option to reuse an existing application definition.

    3. Click Next.

  4. On Pages:

    1. To add a blank page to the application, click Add Page.

      The new page appears in the list at the top of the page.

    2. For Subordinate to Page, select a subordinate page.

    3. For Page Name, enter a page name.

    4. Click Next.

  5. For User Interface:

    1. For Select a theme - Note the selected theme.

    2. Show - To select another theme, make a new selection. From Select a theme, select a new theme.

    3. Click Next.

  6. Confirm your selections and click Create.

    The Application home page appears.

  7. To preview the application, click Run Application.

  8. Sign in using your Oracle Application Express workspace credentials.

    Your application now appears as a separate application in Oracle Application Express.

  9. To customize application attributes:

    1. On the Runtime Developer toobar, click the Application ID.

      The Application home page appears.

    2. To edit application attributes including the application name, click Edit Application Properties.

      The Edit Application Definition page appears.

    3. Edit the attributes on the Definition, Security, Globalization, and User Interface pages.

    See Also:

    "Managing Application Attributes" in Oracle Application Express Application Builder User's Guide

4.8 Deleting a Migration Project

When you delete a migration project, you delete only the metadata associated with the migration project. Deleting a migration project does not delete or impact applications you have generated from the project or any objects, such as tables or views, in the schemas associated with your workspaces.

To delete a migration project:

  1. Log in the workspace you created for your conversion project.

  2. Click the Application Builder icon.

  3. Click Migrations on the right side of the page.

  4. On the Application Migrations page, click the project you want to delete.

  5. On the Project page, click Delete Project from the Tasks list.

  6. Click the Delete Project button and confirm the deletion.