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.

Shared ruleset

Updated on April 5, 2022

A shared ruleset contains a small number of rules that each operate on a common, top-level page of a single class (or of subclasses of that class).

Shared rulesets have the following restrictions:

  • A shared ruleset cannot contain a class rule.
  • Rules must apply to classes that extend existing classes such as the Work- base class and the Data- base class.

Typically, shared rulesets contain only a few rules. The intent is to provide a small group of rules that provide common functions that can be shared among (unrelated) applications.

To facilitate reuse of the ruleset in multiple situations, use the keyword Top in property references in the rules of a shared ruleset to refer to the top-level class on which the rules operate. Do not identify this class explicitly.

When you log in, a ruleset list is developed from the information in your access group and rules that it references. Shared ruleset versions appear near the bottom of the list, just above the standard Pega- rulesets.

To mark a ruleset as a shared ruleset , set the RuleSet Type on the Category tab of the ruleset form to Shared.

To include a component ruleset in your own ruleset list, identify the ruleset in the Enabled components array on the Definition tab of an application rule referenced by your access group.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us