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.

Rule Collections

Updated on October 7, 2014


Rule collections allow you to:

  • Define a set of rules that will be executed sequentially as a group
  • Define conditions to prematurely stop the execution of the rules
  • Track and save information about the rules executed
  • Define an explicit list of rules or a dynamic list of rules generated by a List View to be executed

Collections are executed using the Collect method, followed by the Collection name within activities.

The Rule-Collection rule form has a number of tabs:

Preamble and Stop. The Preamble and Stop tab allows you to select the “Save Execution Information?” checkbox, which tells PRPC whether to save information about the rules run associated with this collection. The information saved is stored in a Log-Collection instance.

  • In the “Preset Property Values” section of this tab, you can set a value to a list of properties before executing the rule collection.
  • In the “Stop When These Conditions Are Met” section, you can list a set of When rules that will determine when to stop the rule collection before all the rules have run. You may also execute an activity when that condition is met.

Collection. On the Collection tab, the “Define Collection Specifications” section allows you to determine which rules will run as part of this collection. In this section you can:

  • Set a description for each of the rules you wish to run
  • Set preconditions to determine “if” to run the rule. The precondition can be:
    • When rules
    • Decision trees
    • Decision tables
    • Map values
  • Override and set a specific Step Page that can be a new and different top level page or an embedded page The types of rules you can execute are:
    • List views. Using a List view can allow for the rule engine to dynamically determine which rules to run based on rule metadata
    • Activities
    • Decision trees
    • Decision tables
    • Map values
    • Declared expressions
    • Other collections

Rule Collections can be very useful in BRE projects or the BRE portion of a BPM project. Potential uses include:

  • Defining and maintaining a list of adjustments that determine the cost of a loan or insurance policy
  • Defining and maintaining a list of decision rules that qualify or disqualify a loan dynamically, determining which rule caused the disqualification



Pega Platform 7.1.1 - 7.4 Low-Code App Development Financial Services Healthcare and Life Sciences Insurance Communications and Media Government Healthcare and Life Sciences Consumer Services

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