PEGA Decisioning - Managing the Business Rules(Revision Management)
AppOverlay & Decision Manager Portal configuration:
·
Decision Manager portal mainly used for PROD
Simulation & PROD. Use an applicationOverlay for development
·
Business sandbox & AppOverlay env &
Direct deploy for Decision Data update
·
Need to configure ADM monitoring, IH, VBD
Building An app overlay application:
·
Create New App Overlay wizard and create an
app
·
Define the accessgroup & list of
available rules to expose to AppOverlay to make the changes. Primarily on
Decision data.
·
Default application Overlay will be created
after Landing opage. The name of the overlay starts with ‘RTC-‘.
·
Start the Application Overlay wizard via the
Decisioning > Infrastructure > Revision Management->Application
Overlays landing page.
·
Define the AppOverlay applicaiton, Revision
ruleset, accessgroup & the Rules to be included as part of AppOverlay
·
Selet the rules to make available for the
revision Management, select the rules and click "Include for Revision
Management"
·
Review the AppOverlay and credit the
AppOverlay application
·
Setup new accessgroups & their roles and
the required operator IDs to use.
Managing the Business Rules(Revision Management):
Has
3 envs in PROD (build-Sandbox, test-sandbox and prod).Revision Management
enabled business users to make the change with the limited rules.
Post
every release, AppOverlay reset will be done in the dev environment
(PROD-AUTH). ie, new version of the app overlay will be created. Post creation,
completed package will be deployed in business sandbox (Simulation) followed by
PROD like regular BAU release.
·
AppOverlay release & package deployment
as part of BAU release has to be explored.
·
The process to create a version & export
is based on the dynamic case management process
·
As part of Revision management, CRs will be
created by Revision Manager and the change will be implemented by Strategy
Designer. Revision manager will approve/Reject the CR
New AppOverlay version will be installed like below:
·
The System Architect can use the revision
activation landing page which can be found at Decisioning -> Infrastructure
-> Revision Management -> Revisions.
·
These revisions are primarily used to
implement the config parameter to alter the decision application behavior
·
To sendback the CR to the RevisionManager,
use SendBack CR option incase any additional RuleSet access required.
·
Once you submit the Revision, jar package
file will be generated. We need to download them.
·
To implement the changes in pre-prod &
Prod environment, Decisioning -> Infrastructure -> Revision Management
-> Revisions->Import revision
·
Select the Operator from the available list
to test the changes for the selected operators before promoting the
change.Decisioning -> Infrastructure -> Revision Management ->
Revisions->"Activate" the change. Change will be activated to all
the users. We can roll-back if needed
·
After activating the package, we need to
logout and login again
Working with the Revision Management is 2 set process. 1. Create Revision. 2. Create CR. We can have more than 1 CR in a given Revision. Once Revision Submitted, Jar will be generated. If the change is not working, we can revert the change by doing "Roll-back", otherwise activate the Revision.
More
details about app overlay setup is available at https://community.pega.com/knowledgebase/articles/decision-management-overview/applying-changes-business-rules
Happy Learning!
