The Oracle APEX blog is your source for APEX news, technical tips and strategic direction

[Forms to APEX] The Last Enhancements

Monica Godoy
Principal Product Manager

Through the blog posts in this series, I shared how to modernize a sample Oracle Forms application and finally, you'll be able to run the full APEX application.

The last components to enhance are:

  • Navigation Menu
  • Authentication Scheme
  • UI Enhancements

Navigation Menu

When you create an APEX application, it includes a Navigation Menu (on the side of the application or across the top of the application) and you can change it anytime. You also have the option not to use a menu at all.

To define the Navigation Menu settings follow these steps:

  1. Click App Builder and click on your application.
  2. Click Shared Components.
  3. Click User Interface Attributes.
  4. Click Desktop.
  5. Go to the Navigation Menu section.
  6. For Template Options, check Collapsed by Default.

Now, let's manage the navigation menu to clean it up by creating two entries, one for Customers and another for Orders. Following these steps to create new entries in the Navigation Menu:

  1. Click App Builder and click your application.
  2. Click Shared Components.
  3. Click Navigation Menu.
  4. Click Desktop Navigation Menu.
  5. Click Create Entry button.
  6. For Sequence, enter 15.
    For Image/Class, enter fa-user-circle.
    For List Entry Label, enter Customers.
    For Target type, select No Target.
  7. Click Create and Create Another button.
  8. For Sequence, enter 20.
    For Image/Class, enter fa-forms.
    For List Entry Label, enter Orders.
    For Target type, select No Target.
  9. Click Create List Entry.

Customers and Orders entries were created and now I need to define the Parent Entry for the rest of the entries. In the Desktop Navigation Menu, go to the Customer and Order options to select the proper parent entry.

  1. Click each Customer option.
  2. For Parent List Entry, select Customers.
  3. Click each Order option.
  4. For Parent List Entry, select Orders.

Finally, the Menu looks cleaner and easy to use.

Authentication Scheme

Authentication is the process of establishing each user's identity before they can access your application. It may require a user to enter a user name and password or could involve the use of digital certificates or a secure key. Since this application is going to be public, I'll turn off the authentication. To do so, follow these steps:

  1. Click App Builder and click your application.
  2. Click Shared Components.
  3. Click Authentication Schemes.
  4. Click Create.
  5. For Create Scheme, select: Based on a pre-configured scheme from the gallery.
  6. Click Next.
  7. For Name, enter No Authentication.
    For Scheme Type, select No Authentication.
  8. Click Create Authentication Scheme.

UI Enhancements

There are a number of optional enhancements that can be enabled, such as:

  • Define an understandable label for items, heading columns, and buttons.
  • Define a format mask for number type items and columns 
  • Define a consistent look and feel across the application.
  • Include extra validations to prevent end-users from entering invalid options.
  • Create a dashboard for the home page. This allows end-users to analyze the application's data quickly and easily.

Theme Style

A theme style is a CSS that is added to the base CSS. Using the Theme Roller utility, developers can change the appearance of an application. You can always change/customize the style of your application by following these steps:

  1. Run your application as a developer while you're logged in the APEX Workspace.
  2. At the bottom of the page, you can find the Developer Toolbar.
  3. Click Theme Roller.
  4. For Style, select Vita.
  5. Click Set as Current.
  6. Close the Theme Roller window.


Take a look at the Summit Application and enjoy the modernization!


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.