24.6 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.
Application is the Unit of Export and Import
You can use App Builder as you normally would, but be mindful that the unit of APEXlang export is the application. If you have made changes to your app outside App Builder, importing its APEXlang replaces App Builder’s current version to reflect the latest external changes. Conversely, if you make changes in App Builder, external tools see them when you next export the app to APEXlang.
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
- 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.
Parent topic: Working with APEXlang