In my previous post of this series, I talked about cookie sharing in APEX. The next post in this series is about build options, I hope you enjoy it.
Imagine having to release an apex application, but you don’t want some parts released in to the production environment yet, because they are unfinished, or not tested. Or you want to disable a module in your application for some reason.
Apex provides a solution for this called build options.
You can find the build options under shared components > logic > build options
Let’s create 2 build options:
The first one will keep the component active in our development environment, but will disable it on export so the developed content is disabled in our production environment.
The second one will disable content in the application, and take over this behavior on export to our production environment.
For the status there are two options possible:
Exclude, will disable the content in the current application, and include will keep it enabled in the current application.
For the default on export there are 3 possible combinations:
Same as current will take over whatever has been chosen in status when exporting a page. Exclude will disable the components on export of the application. Include will enable the components on export of the application.
Build options can be attached to any component in apex: pages, processes, regions, items, and can be found under the configuration tab when editing the components.
As a test you can put the 2 build options on some page items in your current application.
When you run the page you will notice that in your development environment, one item will be visible and one will be gone from the page.
When you take an export and import it back in the new environment you will notice both items are removed from the page.
That’s it! The fourth blog in this series will be about recovering applications and page elements using flashback, and will be online soon.