Close popover
King Yu Tam (King_Tam)
Application Architect
King_Tam Member since 2008 3 posts
Posted: October 11, 2018
Last activity: October 16, 2018

Best practise for ruleset (source) management

Hi all,

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.

For example,

  • 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.

We are currently using Pega Platform 7.x

Any help would be appreciated.

Low-Code App Development
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.