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.
Within the History tab, the "View Full History" button invokes "Open URL in Window" calling the @baseclass.HistoryOfHarnessRecord Activity. Within the popup window, there is a “History for All Versions” button. Clicking this button causes the @baseclass.HistoryOfARecord Activity to be invoked. The @baseclass.HistoryOfARecord Activity invokes the History-List Method. The leftmost column of the history pop-up’s Grid contains a Pencil icon with Alt text that says “Click to view the rule as it was before this change”. Clicking this icon causes the @baseclass.doUIAction Activity to be called where the “action” parameter is set to “openRuleSpecific”.
Suppose on the History tab’s non-Final Rule-.RuleFormHistory Section a "View Pre-Skim History" button were added? When the button is clicked, results would be obtained by a Data Page that invokes a service that in turn has access to an archived version of the Rules schema before it was skimmed.
Thanks for reply. Finally we have chosen to not use the full Pega Instance for Dev History, instead we will have a database with pr4_history_rule and pr4_rule_vw tables which are used to fetch the full history in your mentioned @baseclass.HistoryOfARecord Activity.
We have added connection to this DB to current Pega Dev inctance. Then indeed we customized Rule-.RuleFormHistory Section and invoked a custom copy of HistoryOfARecord activity which in turn called for custom Connect-SQL rule to fetch the history.