Skip to main content

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

Rule vs record

Updated on January 21, 2021

Pega Platform contains two distinct types of objects, rules and data instances, yet we commonly refer to them both as rules.

Rules are not the most business user-friendly concept. Because our customers are already accustomed to accessing records in a database, we believe that they will make a familiar association when they see and hear the term record.

Use the term record when referring to a collection of rules and data instances. This guidance also applies to Pega Platform features that affect rules and data instances. DO NOT wholesale replace instances of rule with record.

The following table shows examples of when to use record, rule, and data instance:

TermUsage example
  • Inspect the header of the record form to determine its name, purpose, and ruleset.
  • The Application Explorer gives you quick access to records in your application. To bookmark a record, select ActionsAdd to favorites.
  • Rule resolution selects the correct version of a rule to execute.
  • To work on a rule without blocking other team members, click the Private edit button.
record, rule, and data instance
  • All records now have a header section on the form. Only rules display the option to check out.
  • You may view the XML of your record by using the Actions menu in the header. Data instances have a null value for pyClassName.

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