Reuse and Version Management

Build for maximum reusability to keep your versions clean.

Get Started

Reuse and Version Management covers a range of standard Pega features and developer practices that support:

  • using the right version of the right rule at the right time
  • leveraging existing processes and components to achieve similar tasks in disparate places in the application, without having to write the same processes over and over
  • simplifying and clarifying the organization of the application's code, to make the project easier to understand, navigate, support, and share

Reuse and version management article index

Dig Deeper

Browse the information below to discover how reuse and version management can help optimize your application.

Rule resolution and availability

Rule resolution: When an activity (or property or other rule) is called during processing, rule resolution first searches for that rule in the class where it was called. If the rule is not present in that class, rule resolution then searches other classes in the hierarchy, based on specific procedures.

Rule availability: The “Availability” option on a rule allows you to prevent rules from being copied, or turn off rules which had been in use but are no longer applicable or have been replaced by a different rule.

Rule resolution overview 
Rule availability options

Circumstancing rules

Circumstances and other qualifiers usually represent facts about customers.  These conditions or circumstance options can be a date, property, or template.  They allow you to specify that different rules should be used for different situations.  By specializing or circumstancing a business rule, you can create conditional variants of the rule that address more specific business cases.

Circumstance a rule with different properties or templates
How multivariate circumstancing works

Component and shared rulesets

A component is a set of rules which contain encapsulated functionality.  Components hold a standalone process which can be embedded in multiple applications; they do not depend upon one application’s rules or functionality.   Use a component when you have functionality that could be applied to more than one application, such as a credit score calculator. 

About components
How to create a component
How to embed a component into an application

Training and Support

Training

Build and validate your skills

Find the training that works for you and invest in your success.

Support

Get the help you need

Search support articles, community posts, and open support requests.

Video Library

Watch the latest videos

Browse our growing video library and maximize your Pega investment.