Skip to main content

 –

Understanding application changes made in App Studio

Suggest edit Updated on July 6, 2020

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.

Ensure the following items are properly configured before making application changes in App Studio.

  • A product rule exists with the same name and version as the application being deployed. For more information see Creating a product rule by using the create menu
  • A pipeline has been created in Deployment Manager for the application being deployed.
  • There is at least one unlocked ruleset in the application.
  • The users who will publish changes are logged into the application being deployed on the development system.
  • The users who will publish changes have been granted a role in Deployment Manager that can start deployments.
  • The RMURL dynamic system setting, which defines the URL of orchestration server, is configured on the system.

Your pipeline should have at least one quality assurance or staging stage with a manual task so that you do not deploy changes to production that have not been approved by stakeholders.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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