Skip to main content

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

Packaging an application

Updated on April 14, 2021

To migrate a new application to a different environment, you must package the application before you can import it to the new environment.

  • Merging application changes

    If you develop your application features in separate branches, use the Merge Branches wizard to merge the branches before you package the application. The wizard shows any merge conflicts so that you can correct them before you merge the branches.

  • Packaging an application for migration

    Before you migrate a new application to a different environment, package the relevant data instances and rulesets into a product rule. The product rule is an instance of Rule-Admin-Product, which Pega Platform refers to as the RAP file.

  • Importing the packaged application

    To deploy a new application to a different environment, import the .zip file that contains the packaged application to the new environment.

  • Multitenancy deployment considerations

    In a multitenancy environment, the shared application components are deployed only to the shared environment, and the tenant-specific components are deployed only to the tenant region.

  • Previous topic Building the features of the Pega Next-Best-Action Advisor application
  • Next topic Merging application changes

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