Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Ruleset list usage during rule resolution

Updated on April 5, 2022

Each requestor's use of the system continually causes the system to search for a rule instance, which is known as rule resolution. This search uses properties from many sources to find the most appropriate rule for the current need, including class inheritance, security and access control restrictions, and the ruleset list.

During rule resolution, the system uses the ruleset list as it:

  • Searches the rules in the PegaRULES database repeatedly, first using the topmost application on the list, then the next, and so on. The Pega-RULES application is searched last.
  • Ignores any rule instances that are contained in a ruleset on the list but in versions higher than the version specified in the list.
  • Treats any partial version number (such as 02-) as a wildcard or mask. For example, matching any rule instances containing a version that starts with 02-.

Many other factors influence this process, such as:

  • Unavailable, final, or blocked rules
  • Time-based rules
  • Circumstances
  • Access control (whether the user has authorization to access the rule)

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