Learn the features, enhancements, and changes made to Oracle Forms.
The following section introduces the new and changed features for Oracle Forms and Reports, and provides pointers to additional information:
This section contains information about new and changed features that are being introduced in the release, features that have been enhanced, and changes to existing features.
The following list provides an overview of new features and enhancements:
Refer to the Oracle Forms product page on Oracle.com for more information.
Oracle Forms Standalone Launcher Improvements
In this release, we have made the following improvements to the Oracle Forms Standalone Launcher (FSAL).
Starting with this release, FSAL supports single sign-on (SSO) using Oracle Access Manager.
We have improved cache handling in this release. The algorithm used to determine if a cache update is necessary has been significantly improved thereby improving application startup performance. Locally stored cache is also now stored in uniquely named directories. This will help to prevent applications that share similar JAR names but different content from overwriting each other.
Administrators can now use the new
ignoreSaaCache parameter to specify whether the Oracle Forms Standalone Application Launcher (FSAL) should ignore files downloaded from the Forms server and cached on the Java client machine from which the Launcher is being run. For more information on the parameter, see the Working With Oracle Forms guide.
The Oracle Forms Standalone Launcher is now compatible with Java versions 11.0.2 (LTS) and later.
Forms Application Deployment Services Enhancements
In this release, we have made the following improvements to Forms Application Deployment Services (FADS).
Starting with this release, Oracle Forms Application Deployment Services (FADS) correctly deploys C libraries, such as DLLs for WebUtil-enabled applications.
In 18.104.22.168, Oracle Forms Application Deployment Services (FADS) was not able to generate PL/SQL modules (PLL) when connecting to a version 12+ database. All databases certified with this Forms release are also supported for use with FADS.
Increased Allowed Text Length for Text or Display Items
The Maximum Length property for Text and Display items has been changed from 65534 to 2097151.
Improved WebUtil File Transfer Rate
When transferring files using the file upload and download features of WebUtil, the transfer rate has been increased by as much as 30% for both transfers between the user and middle-tier and between the user and database.
Updated Database Client Software
This installation includes an update to the database client software installed with Fusion Middleware. The database patch set included is 22.214.171.124.190716. If you execute the
opatch lsinventory command, the patch identification number for this update will appear as 29494060 on Linux or Unix and 30220086 on Microsoft Windows.
Autonomous Database Support with Oracle Forms
Oracle Forms 126.96.36.199 is certified to connect to an Oracle Autonomous Transaction Processing (ATP) database for both application data and/or the required Fusion Middleware Infrastructure Repository.
Some Forms features normally available in an on-premise database are not available in ATP or may be partially exposed with limitations because of ATP's enhanced security features.
Because of these limitations, Forms features like Advanced Queuing integration and Database Idle System Events are not supported.
For more information on these limitations, consult the following topics in the Oracle ATP Cloud documentation:
- (Shared Exadata deployments) Autonomous Database for Experienced Database Users in .
- (Dedicated Exadata deployments) Using Oracle Database Features in Autonomous Transaction Processing Dedicated Deployments in Developer’s Guide to Oracle Autonomous Transaction Processing on Dedicated Exadata Infrastructure.
For a description of exceptions thrown by Oracle Forms Builder when working with Autonomous Transaction Processing, see Oracle Forms Issues and Workarounds.