Posted: 13 Oct 2016 10:33 EDT Last activity: 26 Oct 2016 7:13 EDT
Syncing User Made Changes To Lower Environments
Hi, We have created an Admin tool in Pega for business users to make certain updates as needed in the PROD environment. Our change managements has requested that we design an automated process to propagate these changes to the lower environments. If anyone has done this and has some tips that would be appreciated. I was thinking of using SSIS. but if there is a better way I am all ears. Thanks
***Updated by moderator: Lochan to add Categories***
Assuming they are using a single unlocked ruleset, you could do a reverse migration and lock it, migrate it back from prod, to UAT, to Test, to Dev (or whatever your setup is) and create a new, unlocked version in Prod. That way it's locked in Dev (to avoid anyone "accidentally" making rules there and causing confusion) and you can test as you go to confirm that the changes there aren't going to cause problems with the changes working their way up from Dev.
I agree with Santanu that you want to be careful, because you are creating more vectors for change, so you want to limit the scope as much as possible to maintain control over the overall health of the system.
There could be many ways to automate this process.
One of them could be: If change is more frequent and you have to move changes to lower environment everyday then, Create agent to get the rule details to generate RAP of Changed rules at EOD( or defined time) and then do connector call to call Lower environment services to install the product.
Other solution: There are many Devops soultion being developed where we are moving code from Dev to UAT/Prod automatically. you can use that idea to move code from Prod to UAT/Dev
It has been a bit since I could come back here and check on this. Thanks for your replies. To answer one of you, the scenario is there is an Admin site deveoped in Pega so that business users can add or update eligibility questions.Whe n Iwas in Page CSA cclass the instructor said this was not an uncommon practice as it means the customer can update content thatdoesn't required logic changes without having to go through the whole SDLC. But the technique was more advanced than what was covered in the class.
I will take the suggestions and go back to my team with them. Thanks