My client installation is using a Pega Marketing 8.1 application on a Pega Platform 8.1.5.
Production environment have two applications – one points to the production rule sets which is actually the production environment and the other, which we use as a Business sandbox, points to a higher version of the rule set.
Can I please have opinion from our experienced community if it is okay to implement Pega Revision Management in our Business sandbox environment?
Pega Revision Management is the recommended approach for efficient rule management and enables business users to respond quickly to changes in the external and internal factors that influence their business.
I think this is worthy of more discussion but my first thought would be no. Could you elaborate your use case some more as typically the RM and the Prod are separate and this is somewhat unusual set up for a business change (sandbox) environment.
Revision Management is not intended for production, as I understand it. Its a means by which you can introduce changes from a lower environment into production through the use of "Revisions". That said, another aspect of RM is the use of application overlays and change requests. This allows for roles of RevisionManager and Strategy Designer to make and approve changes within the scope of Change Requests. I've got to imagine that if your only intent is this latter aspect of RM, then creating an application overlay in your "Business Sandbox" version of your application - that this would work.
However, if your intent is use Revisions to move rules to or from this instance - I would think this needs deeper discusssion.
Hi All, Thank you for your comments. Our purpose of using Revision Management is to allow Revision Manager and Strategy Designer to make and approve changes with in the scope of Change Request. But as I already mentioned We share the same Production Environment for the Purpose of Business Sandbox by just using a higher rule set with in the same application. We will make and test changes in the higher ruleset and when Happy with the change, make that higer ruleset available to the production users. Hope our intention is clear here. So in this scenario do Pega recommend using the Revision Manager using the Change Request and the "Role".
One thing to consider here is changes to the rules in the revision management will be done as part of the revision ruleset (created as part of application overlay creation). Also the revision management creates and deploys the revisions for the same(one) application.