Setting up a development environment using subscriptions

The architecture of a single APEX application is simple. You create a workspace, then you create an application, and then you build pages inside that application.

But what if we anticipate more than one application in our workspace? It's possible that a company has a single corporate style for all of its web applications. If we had to create templates for this style in every single APEX application we create, we would lose a lot of time which could otherwise be spent on creating functionalities for the application itself.

In this recipe we will see how we can set up a development environment that can reuse as many elements as possible and still be flexible.

Application Express uses a feature called subscriptions. This allows developers to inherit a number of properties from one application to another. By using these subscriptions we don't have to build something like a template twice, but instead, we create it once in a parent application...