The search technique used by the system to discover the best or most appropriate rule instance to apply in a given is known as rule resolution.

Except for a few rule TYPES — classes that inherit from the Rule- class — rule resolution applies to all rule types. Instances of classes derived from the Work-, Data-, or any other base class are not affected by rule resolution.

Despite the fact that the rule resolution process is fast and invisible, it is critical to comprehend how it works. Make key component value selections based on how you want rules to be found via rule resolution when you construct applications. The rule resolution process can be speed up by using an in-memory rule cache. If the system discovers an instance (or instances) of the rule in question in the cache, it accepts the CANDIDATE rules from the cache and bypasses MANY steps in the resolution process.

The following are some of the advantages of rule resolution:

• Across apps and organizations, rules can be shared. Object-oriented software development has many advantages, including sharing and reuse.
• More explicit rules stated at a lower level can override rules DEFINED at a higher level. While this reduces the value of sharing, it gives much-needed flexibility while highlighting exceptions.
• Even inside a single rule-set, rules might have many versions, and security rules limit which users view and execute which versions. This makes application development, testing, and PATCHING easier.
• With little conflicts and interference, a single Pega Platform system can host many apps, multiple organizations, and multiple versions of a single application.
• Applications can be built independently of one another, but they can all be based on the same set of rules that are locked (and hence will not change).