Skip to main content

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

Packaging your application in a product rule

Updated on August 25, 2021

Use product rules (sometimes referred to as RAP rules) to migrate or deliver an application to another Pega Platform system. 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

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
  • Creating a product rule that includes associated data

    To include associated data in your product rule, use the Create menu to individually specify the contents of a product rule for an application or for work. When you use the Create menu, you can specify one or more applications, one or more rulesets, or individual rule instances to include in the product rule.

  • Creating a product rule that does not include associated data

    If your archive does not include associated data, use the Application Packaging wizard to identify data-admin instances associated with your application and create a product rule to define your application. This is most common for customers who have upgraded from PRPC 6 or earlier.

  • Creating a product rule of test case data

    To migrate small amounts of case data, use the Package Work wizard to create a product rule that contains case data generated when the application executes. This case data can include work items, assignments, history, bugs, documents, and attachments. After you create the product rule, you can transfer the application to multiple systems.

  • Editing a product rule

    Customize the product rule to specify contents, dependencies, deployment options, and history entries.

  • Previewing and creating the archive file for a product rule

    After you configure and save your product rule, preview the contents of the archive and generate the archive file.

  • Previous topic Running the Static Assembler in stand-alone mode
  • Next topic Creating a product rule that includes associated data

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