Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded.

Creating an application archive file

Creating an application archive file

To create an application archive file, you must first create a product rule to identify the components you want to include in the archive file. Then, you create an archive file that contains the application components.

product rule

Create a product rule

You can create a product rule in two ways:

  • Create the rule instance manually and add the information to the fields on the rule form. The rule form provides greater flexibility than the wizard. For example, you can set minimum or maximum ruleset versions to include in the archive rule. You can also include rulesets that are not in the application. However, manually entering information — such as selecting specific data instances — can be time-consuming and error-prone.
  • Use the Application Packaging wizard — it guides you through a series of steps that populate and create a product rule. The wizard includes the rulesets in your application. Because the wizard presents an inventory of components that are in your application, selecting the components you want to include is easier and more accurate than manually entering them in the product rule. When the wizard creates the product rule, it enters your selections automatically on the form. For finer control, you can modify the product rule after you have created it in the wizard.

Create an archive file

Before you create an archive file, do the following things to ensure that the file is complete and correct.

Note: Do not lock delegated rulesets. Locking the rulesets prevents users from updating the rules in the destination system.
  • Associate your data records with rulesets; this ensures that all the data records required by your application are included in the archive file.
  • Make sure that all rules are checked in so that the rulesets are complete and current.
  • In most cases, lock the application rulesets included in the package to help ensure that the migrated application and its rulesets are synchronized among the source and destination systems.
  • Merge branched rulesets and remove the branches from the application if you are exporting the application to a production system.

You can create an archive file using buttons on the product rule form or on the landing page that contains the wizard.


This Topic is available in the following Module:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice