Skip to main content

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

Understanding App Studio publishing

Updated on July 14, 2022

App Studio publish enables Pega Platform users to publish and deploy application changes with no prior Deployment Manager experience necessary. This seamless functionality publishes minor application changes through deployment pipelines to create new artifacts without ever leaving App Studio.

Note: Some configurations do require Deployment Manager interaction. Please contact your system administrator for access to the orchestrator environment.
  • Configuring App Studio for publishing

    Publish application updates in App Studio using an existing deployment pipeline to seamlessly create patch versions of an application and start a deployment.

  • Publishing application changes in App Studio

    You can publish application changes that you make in App Studio to the pipeline. Publishing your changes creates a patch version of the application and starts a deployment. For example, you can change a life cycle, data model, or user interface elements in a screen and submit those changes to systems in the pipeline.

  • Interpreting different publish statuses

    App Studio provides various status updates throughout the publish cycle to inform you of various challenges or roadblocks your pipeline might encounter. These guardrails are intended to mitigate and resolve issues before publish failures.

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