Skip to Main Content
Feature Request FR-3932
Product Area Application Builder
Status CLOSED

2 Voters

Backward-Compatible Plug-In Export Feature for Oracle APEX

kevintech Public · Jul 27 2024

Idea Summary
The current Plug-In Export feature in Oracle APEX lacks the ability to export plug-ins built in newer versions to previous compatible versions. This limitation forces developers to recreate plug-ins in older environments, which is time-consuming and potentially error-prone. We propose enhancing the Plug-In Export feature to allow exporting plug-ins to previous compatible APEX versions, with appropriate disclosure messages for potential compatibility issues or missing functionalities.

Use Case
This enhancement would be beneficial in scenarios such as:

  • Developers working across multiple APEX environments with different versions.
  • Organizations gradually upgrading their APEX instances, requiring plug-in compatibility across versions.
  • Open-source plug-in developers wanting to provide broader version compatibility for their creations.
  • Consultants needing to deploy solutions to client environments running older APEX versions.

For example, a developer creating a plug-in in Oracle APEX 24.1.2 could export it for use in an Oracle APEX 23.1 application, saving significant time and effort.

Preferred Solution (Optional)
To implement this idea, we suggest:

  1. Adding a "Target Version" dropdown in the Plug-In Export interface, allowing users to select the APEX version they're exporting to.
  2. Implementing a compatibility check system that analyzes the plug-in's features against the target version's capabilities.
  3. Generating a detailed compatibility report, highlighting:
    • Features that will work as expected in the target version
    • Features that may have reduced functionality
    • Features that are incompatible and will be removed
  4. Providing an option to proceed with the export after reviewing the compatibility report.
  5. Automatically adjusting the exported plug-in code to ensure maximum compatibility with the target version.
  6. Including a clear disclosure in the exported plug-in metadata about the original version and any compatibility modifications made.

This solution would significantly improve the portability of plug-ins across APEX versions, enhancing developer productivity and promoting more widespread use of custom plug-ins in the APEX community.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is not feasible in APEX.

Comments

Comments

  • vincent morneau Admin OP 1.7 years ago

    Hi @kevintech , no doubt this would be extremely valuable. However we think it's unfeasible, or unrealistic.

    We can't possibly check if a 24.1 plugin uses 24.1 APIs. Then what would happen to the backwards compatibility?

    For the same reason we can't export a 24.1 app to be compatible with older APEX releases, there is simply too much to consider, and that's why APEX only allows install in one direction.