Using App Builder and External Tools Together

Export your application to APEXlang to work on it externally and import it to reflect the changes in App Builder. Teams using working copies to isolate a developer’s changes for a feature or fix can also embrace external tools.

Importing an Application or Just Selected Files

You can use App Builder as you normally would, but be mindful that the unit of APEXlang export is the application. If you make changes outside App Builder, you can import only selected files you change. Alternatively, you can import the entire APEXlang application. Conversely, if you or colleagues make changes in App Builder, external tools see them when you next export the app to APEXlang.

When using the SQL Developer extension in Visual Studio Code, its Compare with APEX Application toolbar button lets you see differences between the remote application definition in APEX App Builder and your local APEXlang files. It also lets you selectively pull in any remote changes from the App Builder version into your local copy. This can help ensure any local changes don’t inadvertently overwrite changes made by teammates.

Using APEXlang for Source Control

Maintaining your app’s development history over time by source controlling its external artifacts in a system like Git continues to be a best practice. APEXlang files work great for this purpose, too.

Resolving Conflicts Using APEXlang

If you realize your external APEXlang and App Builder changes are out of sync, since APEXlang files are editable, validatable, and importable, you can resolve the situation by:

• Exporting the App Builder app version to APEXlang

• Unzipping it into a temporary folder

• Unifying versions, resolving any conflicts, with your favorite diff/merge tool

• Importing the unified APEXlang back into App Builder when appropriate.

The app only imports when it validates cleanly, so if it fails just review the errors, address them, and try again.

Using APEXlang with a Working Copy

If you create a working copy of your main application to isolate work on a feature or fix, you can export the working copy to APEXlang, use external tools to modify it, and import it again. APEX preserves the link between the working copy and its main application. When you are ready to merge your changes, the process works the same as if you had made them entirely in App Builder.

For more information, see Creating a Working Copy to Merge, Refresh, or Compare in Oracle APEX App Builder User’s Guide.