Skip to main content


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

Enabling run-time branching and editing

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Help citizen developers safely make changes to the UI by setting up a branch for run-time editing in Live UI. With this approach, less experienced developers can introduce changes to the interface in a separate environment, and the lead developer can later review the updates and merge them with the main product.

Before you begin: Ensure that all rulesets in your application are locked. For more information, see Configuring ruleset version settings.
  1. In the header of Dev Studio, click the name of the application, and then click Definition.
  2. In the Development branches section, click Add branch.
  3. In the Add a branch ID dialog box, enter a name for the run-time edit branch.
    For example: Liveedit.
  4. On the application definition tab, click Save.
  5. In the header of Dev Studio, click the Toggle branch development icon.
    Toggle branch development icon
  6. In the Branch development preferences dialog box, enable Branch development, and then click Submit.
  7. In the navigation pane of Dev Studio, click App.
  8. In the application pane on the left side of the screen, click the Branches tab.
  9. Expand the node for your application, and then right-click the branch that you added.
  10. In the drop-down menu, select Use for edit at runtime, and then click Submit.
    Result: The application now uses the branch for storing changes that developers introduce through the Live UI tool. Even if you develop the application in a different branch, the system always stores Live UI changes in the designated branch.

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