Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Best practices for using multiple built-on applications

Updated on November 15, 2021

To increase reuse between your Pega Platform applications and speed up the development process, enhance your applications by using multiple built-on applications. Built-on applications are structured as a hierarchical application tree.

By using multiple built-on applications, you break up common and stand-alone components into their own applications, and provide the ability to point an application to another application rule, helping to automatically update any required rulesets and versions across applications when applications undergo changes.

For example, the uPlus organization creates an application layer to contain the definition of common assets and integrations in corporate systems. Separating each integration into its own built-on application can simplify the revisioning of each integration by removing dependencies. As a result, applications use features independently and when developers want to upgrade a feature, they can upgrade only a specific built-on application, without affecting the others.

Best practices for using multiple built-on applications

Consider the following tips when developing an application that uses multiple built-on applications:

  • Limit development to rulesets in the top-most application and keep built-on applications locked.
  • To develop in the lower layers of the hierarchical application tree, switch to a built-on application layer.
  • Avoid having the same ruleset in multiple applications. Instead, refactor the ruleset to its own application or a common application.
  • Avoid using different versions of an application in the hierarchical application tree.
  • Avoid branch IDs that span several applications.
  • Avoid making any application structure changes without utilizing the Validation Tool to validate rules.
  • Avoid using Ruleset Validation mode rulesets. Ruleset prerequisites can be challenging to maintain, especially when you need to refactor the application stack. Always default to using Application Validation mode rulesets, which create the ruleset stack depending on the application in which you define the rulesets.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us