Packaging your application in a product rule

Use product rules to migrate or deliver an application to another Pega Platform systems. Product rules identify the rulesets and versions, rules and data objects, and other parts of an application. Define a product rule to specify what to include in the archive. Then use one of the other tools to create the product rule.

After you define the contents of a product rule, you can generate a .zip file that contains the following items:
  • Rules in rulesets and versions for a specific application
  • Rules in selected rulesets and versions
  • Instances within any class
  • A post-deployment action that displays Read Me information
Using a product rule is the best practice for packaging applications. You can do any of the following with a product rule:
  • Export multiple applications
  • Export dependent rulesets that are outside of your application
  • Include sample data
  • Specify whether to include history, snapshots and memos

The following tools work with product rules or .zip files:

Use the Records Explorer to list all the product rules that are available to you.

Product rules are instances of the Rule-Admin-Product class. They belong to the SysAdmin category. Product rules are sometimes informally called RAP rules.

Product rules are rarely referenced by other rules. When searching for a Product rule, the system does the following:

  • Filters candidate rules based on a requestor's ruleset list of rulesets and versions.
  • Finds circumstance-qualified rules that override base rules with the same key.

Class-based inheritance does not apply. Time-qualified resolution features are not available for Product rules.

By default, the product rule contains instances of the following data classes, which are part of the application you are packaging:

User Database