Versions Compared

Old Version 18

changes.mady.by.user Erick Jones

Saved on

compared with

New Version 19

changes.mady.by.user Erick Jones

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Oracle APEX plugin provides a means to build and deploy Oracle Application Express (APEX) applications, and export exporting a workspace from App Builder with the intention of placing under source control.

Tip
titleMajor Improvements in 5.1.0.3

In FlexDeploy 5.1.0.3 the Oracle APEX plugin has undergone a major overhaul, supporting a very rich set of use cases.

  • Automatically export APEX application from development environment.
  • Selectively import entire application or individual pages and/or shared components.
  • Automated export of APEX application and commit to SCM of your choice to enable continuous integration. As application is exported in split format, it is very easy to use SCM tools to view changes over time to individual page/component.
  • Source application from development environment or SCM.
  • Compare individual pages and/or components across all environments to find difference. Comparison is done against deployment state details in FlexDeploy.
  • Change detection during deployment, i.e. if application/page/component is already deploy (no changes) then it will skipped. User can force deployment if necessary as well.
  • Manage supporting database objects (tables, packages etc.) using FlexDeploy JDBC or Database plugin.

As a result the changes are not backward compatible, and will cause refactor of any existing workflows and projects.


Development for Oracle APEX is performed on the database using Application Builder. So, this is different than traditional development environment where code is created on developer's workstation and checked into a Source Control System. You can take one of two approaches to automate promotion of APEX applications.

  1. Developers export an application as SQL files and commit to Source Control System. The build in this case is a simple export of Source Control and packaging into a zipped artifact. 
  2. The application files (e.g. pages and components) can be built directly from Application Builder in a Development environment, bypassing a Source Control System all together. 

No matter the approach chosen, the build operation produces a zip file containing the application sql files, and the deploy operation deploys the application to the target APEX database.

...