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 July 8, 2022

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:

  • Application Packaging wizard – Creates a product rule that contains relevant data instances and rulesets.
  • Export wizard – Creates a .zip archive from a product rule.
  • Import wizard – Imports a .zip archive.
  • Product Migration wizard – Creates a .zip archive from a product or product patch rule, migrates the archive, and imports it to one or more destination systems.
  • Package Work wizard – Creates a product rule that includes work items, work item history, and work item attachments.
  • Deployment Manager

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us