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.

Class structure and rule specialization

Updated on September 10, 2021

 This presentation is part of the Reusability and Specialization e-Learning Course.


Your class structure provides the first and most important layer of specialization and reuse in PRPC.  When comparing the use of classes and class structure to RuleSets and circumstances, keep in mind that…

  • Classes provide the most out-of-the-box security flexibility 
  • Classes provide the most flexibility for persistence options 
  • Classes take precedence during rule resolution
  • Rules separated by classes tend to be easier to differentiate and navigate than those separated by RuleSets or circumstances alone

When designing your rules, keep in mind that classes using pattern inheritance can be challenging to alter after deployment since their inheritance is built into the name.  Directed inheritance, on the other hand, can be more easily changed.

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