After Upgrading APEX
Upgrading APEX to a New Version
The Flows for APEX Application is compiled against the packages contained in the version of APEX that is installed on your environment. If you upgrade your APEX installation, for example from APEX 24.1 to APEX 24.2, you need to recompile your Flows for APEX environment by running a script that was included in your application distribution.
If you upgrade APEX to a new version, run the after_apex_upgrade.sql script as the Flows for APEX user after upgrade.
You will be prompted / reminded to do this on opening the Flows for APEX application if it detects that APEX has been upgraded.
Upgrading to APEX v26.1 - Upgrade your Universal Theme.
In APEX 26.1, Oracle has changed template styles, so that if you upgrade APEX and have an application containing an older Universal Theme also present, multiple style records exist in one of the APEX tables - causing some queries in older Flows for APEX versions to return multiple records where only one was expected. Consequently, when you upgrade APEX under Flows for APEX, you should immediately upgrade the Universal Theme to the latest release. Opening Application Bui;der will normally prompt you to do this.
Flows for APEX v25.1 and v26.1 are shipped as APEX 24.1 applications - so if your APEX version is > 24.1, you must upgrade the Universal Theme after installation or an APEX migration.
Re-Configure the Flows for APEX Modeler Component Settings.
From Flows for APEX v26.1 onwards, we now rely on the Monaco Editor present in APEX, rather than bundling our own copy. This reduces application size and distribution size.
After installation on APEX versions higher than the minimum supported version for the Flows for APEX release, you will need to reconfigure the Flows for APEX - Modeler plugin with the version number of the Monaco editor present in your APEX system.
To do this:
- Open the Flows for APEX application in APEX Appliction Builder.
- Go to Shared Componentsย ยป Component Settings.
- Select the Flows for APEX - Modeler plug-in.
- Set the Monaco version number. (If the version number is not in the inline help, refer to the Oracle APEX documentation for your APEX version - Try searching for JavaScript Library Upgrades in the APEX Release Notes)
