Close popover
Ivan Anikanov (aniki)
Principal System Architect - Pega Consulting
Pegasystems Inc.
aniki Member since 2014 2 posts
Posted: April 9, 2018
Last activity: April 27, 2018

Development history instance

Hi LSAs,

My customer is looking for some guidance in Development Environment organisation. The problem is that current dev contains the full history of rule changes for 7 years of development, the application is long in prod already, but still actively developed. Despite this history is useful sometimes for investigation purposes (like why somebody has changed this decision table 4 years ago and now it contradicts with recent changes and causes issues in prod), most of the time this is just a noise in search results, siblings, etc.

The same in production - it contains now 5 times more custom rules than platform itself, because the rulesets have been skimmed multiple times but never deleted from system.

What customer wants is to have cleaned up all upper environments and have two dev: one cleaned and used for active development and another one called dev-history containing all rules with all changes history, comments, etc. The question is is there a way to establish such kind of dev-history environment in preferably automated way?

They are now in Pega 7.2.2 and in process for migration to 7.3.1.

Low-Code App Development DevOps System Administration Installation and Deployment
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.