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.

Creating a product rule that does not include associated data by using the Application Packaging wizard

Updated on April 5, 2022

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.

  1. In the header of Dev Studio, click ConfigureApplicationDistributionPackage.
  2. In the Application field, select the application to package.
  3. Select the product target ruleset and version in which to generate the product rule.
    1. Specify which rulesets to display:
      • To display all of the rulesets specified in the Rule-Application instance of the selected application, select the check box.

      • To save the product rules in an application or built-in application layer, select the check box.
      • To display only the rulesets that are not part of the currently selected application, clear the check box.

    2. Enter the name and version number of the ruleset in which to create the product rule.
      Note: If you select a ruleset version that is in the application you are packaging, the product definition itself becomes part of the package.
  4. Clear the check box next to each built-on application to exclude from the application, and click Next.
    Tip: To create a completely self-contained package, include all applications in the stack. If you later try to import the application into a system that does not include the dependent applications, the import fails.
  5. Complete the remaining screens to specify items to include or exclude from the application package.
  6. Click Finish to package the application.
What to do next: After the application is packaged, click any of the following buttons to continue:
  • Preview - Displays the rules, application data, system data, schema, and code items that are exported based on your selections.
  • Modify - Edit the content of the application product rule. For more information, see Product rules.
  • Export - Create a .zip file with content based on your selections. This .zip file can be used to archive a version of your application and for importing your application to other servers.
  • Migrate - Migrate the application directly to another server. For more information, see Migrating products from the user interface.

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