Skip to main content

New Forms2APEX Modeler
Release 24.1.1

06.05.2024 Stuttgart/Troy – The new Forms2APEX Modeler 24.1.1 is available and it is one thing above all – even more efficient than its predecessor. It has succeeded in automating even more tasks in an Oracle Forms to APEX modernization project. This increase in efficiency and further improvements to the software are the result of current modernization projects in which the Forms2APEX Modeler has already impressed customers and project teams with enormous time savings and high-quality results.

The new and improved functions of Forms2APEX Modeler 24.1.1 at a glance Preparation of the PL/SQL code for transfer to the database

A central aspect of a successful Forms to APEX modernization is the transfer of valuable software artifacts (PL/SQL code) from Oracle Forms to the database in order to make the code available for the new APEX application. In the new version of the Forms2APEX Modeler, there are more options for transferring PL/SQL code to the database. This means that significantly more objects (e.g. PRE and POST-QUERY triggers) can now be transferred and at the same time adapted to individual requirements. This means that code can be added automatically if required (e.g. for additional logging and additional error handling), but the complete structure of the database packages (user interface driven or table API based) can also be decided. This safeguards investments in existing validations, transaction logic and implemented business processes.

Oracle Forms dependencies are made easily visible

The interactive, visual representation of the Oracle Forms structure also makes it easy for developers who do not have in-depth knowledge of Oracle Forms to familiarize themselves with the existing sources within a modernization.

Validations of Forms generated automatically in APEX

Depending on the selection of the APEX region to be created and the field and record validations found in Oracle Forms, validations, dynamic actions and alerts are automatically generated in APEX. In Oracle Forms applications, the validation triggers are the most frequently used triggers alongside the command areas, which means that this generation can save a great deal of time and ensure that validations are not “forgotten” or incorrectly applied.

Selection of regions is supported

When transferring Oracle Forms blocks to APEX regions, the new Forms2APEX Modeler release gives developers more options for the master-detail use of regions. For example, the new Modeler helps with the selection of regions with context-related information.

Ingenious project view for management and developers

In release 24.1.1 of the Forms2APEX Modeler, a completely new and revised checklist has been developed for the remaining work after importing the generated sources. The dashboard shows project managers the status of the current modernization project at a glance, including the next modules to be completed, the current activities of the developers and the progress of the migrated modules. For the developers, the checklist is a safe and convenient tool to ensure that nothing is overlooked in the remaining work. The context-sensitive display of objects, properties and code makes the use of the Forms Builders almost superfluous.

Better than the APEX Page Wizard

Based on the settings of the blocks in the Oracle Forms application, the new Forms2APEX Modeler creates master-detail relations, buttons for the DML operations and the properties of the region depending on the choice of APEX region types. The created region therefore has the same properties and the same behavior as in the original Oracle Forms application and saves research and rework if the region was created via the Page Wizard. The properties for DML row processing and all column properties, such as formatting, alignment, width etc., are of course also adopted.

More flexible in all aspects: multi-scheme capable

If the Oracle Forms application accesses data from different schemas, be it in block attributes or in the definition of value lists, this information is also transferred identically to the APEX application. This means that objects from other schemas can also be accessed regardless of the parsing schema set.

Automated transfer of all leading texts and labels

For both the form-based and the tabular display, all leading texts and column headings are taken identically from the Oracle Forms layout. This means that if you have made an investment in naming the fields for the user in the past, this investment will be retained. If your application dates back to a time before the use of “Prompts” in Oracle Forms, you can use a graphical wizard to automatically assign the texts from the layout of your application to the fields. Incidentally, this step is essential for efficient internationalization of your application.

Offline database support now possible

It is no longer necessary for the PITSS.CON installation to be installed in the same network as the application database. All necessary data can be exported via an export of the schema definitions (PITSS provides an AGENT on the website: https://pitss.com/download-dbagent/). This decoupling makes it possible, for example, to run the Forms2APEX Modeler as SaaS in the cloud without having to worry about network access. This makes it even easier to start modernizing your Oracle Forms application.

Better and easier user experience

The layout of Forms2APEX Modeler 24.1.1 has been adapted and tidied up, taking into account the current work steps in a modernization. An additional process description page provides the user with further information for carrying out the necessary steps. The release supports the latest Oracle Forms (12.2.1.19), APEX (23.2) and database versions (21c). A release for the current long-term release of the database (23c) is still pending.

The benefits of the new Forms2APEX Modeler 24.1.1

One of the biggest achievements of the new version is the ability to generate APEX fragments. This makes modernization projects significantly faster, more efficient, clearer and error-free. PITSS.CON already scores highly in the following areas:

  • Analysis: By looking at every property and every line of code, all important questions are put on the table before the project starts and any surprises during the project are avoided.
  • Documentation: From the entire Forms application landscape, which visualizes all navigation options between the Forms modules, to the graphical representation of all tables within a Forms module or the call-stack behind a button, all dependencies within the application can be documented.
  • Preparation: Cleaning up technical debt (unused code, redundancies and moving PL/SQL code to the database) has long been a guarantee for efficient modernization and creates a perfectly maintainable application.

With the improved generation of APEX code fragments, it is now possible to develop the new APEX application much faster than it is already possible with the various wizards in APEX. The transfer of pages from the generated templates, for example, ensures that all attributes and validations from Forms are already transferred compared to the page wizards. This not only saves important time, but also prevents a requirement from being overlooked or incorrectly “typed”. This allows developers to concentrate on the essentials: Bringing the added value of APEX into their own application.

With the new release Forms2APEX Modeler 24.1.1, the areas “Fragment Generation” and “Create Management Tasks” from the established and successful “PITSS Modernization Process” have been improved. The goal of simplifying and controlling the application redesign and offering the development team more support while retaining all the degrees of freedom available in APEX has been achieved. The release simplifies the entry into modernization and invites you to start with a first cluster.

Would you like to get to know
the new Forms2APEX Modeler?

Please feel free to make an appointment with us:

Your Contact


Uta Daniels
Assistant of Sales Management
udaniels@pitss.com
+49 711/914-012-12