Close popover
Braam Smith (BraamCLSA)
Partner Success Technical Lead
Pegasystems Inc.
BraamCLSA Member since 2012 100 posts
Posted: October 29, 2020
Last activity: October 29, 2020

Maintaining DevOps best practices when using Branching in App Studio [LSA Data Excellence]

Choosing Branch development preferences requires all Rulesets in your Application to be locked. DevOps best practice is that the core rulebase ("the trunk") only evolves by adding non-breaking feature sets. This cannot be realistically achieved when an individual developer makes iterative rule changes that are visible to all members of the delivery team.

In Dev Studio this can be mitigated to some extent through the use of Check-Out, however App Studio simplifies the configuration experience by not requiring citizen developers to check out rules to modify them.

By locking the "trunk" and requiring all delivery team members to work in Branches, the scope of developers affected by iterative changes can be limited, and feature sets can become subject to Branch Review before being merged into the "trunk" where more stakeholders are affected.


Discussion on this topic was sought from the LSA Data Excellence (Pega 8.4) webinar conducted in July 2020. The webinar and its full set of discussions that arose from it are available at LSA Data Excellence: Webinar, Questions & Answers

***Edited by Moderator: Pooja to add Developer Knowledge Share tag***
Pega Platform 8.4.1 Low-Code App Development App Studio DevOps Lead System Architect Senior System Architect Developer Knowledge Share