Posted: 11 Oct 2018 9:40 EDT Last activity: 16 Oct 2018 15:10 EDT
Best practise for ruleset (source) management
I am looking for advice and articles on best practice for Pega ruleset management. I work in a large organization where we are required to meet specific standards for source control. I would prefer to leverage Pega ruleset management capabilities over trying to use external tools like GIT, but should I set up a separate Pega instance and use it like a GIT Repo.
Is it recommended to have a separate instance of Pega to use as the reference ruleset repository?
Is it a good idea to keep a single Pega ruleset repository to store ruleset full unrelated Pega applications?
Our development instances are not tied to our production identity management so is consider unsecure as a source management system.
In my experience as a Pega developer this is a pretty common practice. An application will often have one Pega app server which is treated as the "System of Record" for their application, and other systems are used to support the application life cycle, such as development and QA systems. The System of Record system can be kept tightly controlled and have regular back ups. If your teams are doing branch development, the System of Record should be where you perform merges.