Skip to Main Content
Feature Request FR-1743
Product Area Application Builder
Status ROADMAP

38 Voters

Better Diff/Merge versioning of applications and items

maahelal Public · Aug 19 2021

Idea Summary
Add a layer of staging / auto-archival / change-sets of application artifacts to support safe and easy rollout / rollback of sets of changes

Use Case
A more oracle centric approach to version controlling the application instead of typical source control systems

Preferred Solution (Optional)
Instead of rolling back an entire application, use DB features to version smaller scopes of applications like pages, regions, components into a well defined feature/change-set and allow them to be applied or rolled back at will.

This is currently on the roadmap for a future release of Oracle APEX.

Known Duplicates

Known duplicates

FR-3141
FR-3141 Versioning control for APEX Apps

Comments

Comments

  • joseph.upshaw2 OP 2.9 years ago

    I’ve been asking for this for years. When you have a larger developer team and applications with a lot of pages, the ability to check individual pages (seamlessly or, better yet, automatically) would be a huge step toward a dev/sec/opts solution for APEX

  • jayson hanes Admin OP 2.9 years ago

    Now that we have support for human readable export via YAML - the feasibility of this functionality with APEX is getting closer to becoming a reality. The nature of how APEX works with meta data and id keys instead of traditional files simply makes this task vastly complex - a trade off perhaps in light of the performance gains of APEX. The future is looking good, though!

  • joseph.upshaw2 OP 2.9 years ago

    Thanks, @jayson hanes.

    One of the issues we run into is that, off the cuff, people do not think of APEX as a “real” development tool, i.e. one that can fit into a continuous, real time DevSecOps solution. Those of us who've been using it for close to 20 years now (HTMLDB), know this isn't true but, this feature needs to happen as a measure of “maturity” for the tool.  Then, and only then, can we effectively pitch it for enterprise adoption, including for all of our external, customer facing sites. 

    To underscore this, even the Wiki page (which no, I did not author) has only 3 disadvantages of the tool listed and this is one of them:

    • Projects requiring multiple developers to touch the same web page will need to communicate their intentions with each other. There is no built in version control and all components must be edited through the web interface. No support for merge two versions. Page locking can help guard against conflicts.

    So, nuff' said.

  • maramreddy.krishna.ananda.red OP 2.2 years ago

    yes, totally needed