Applying changes to business rules
Pega Platform™ provides business users with the means to implement and test modifications to their applications outside the enterprise release cycles. Revision management enables business users to respond quickly to changes in the external and internal factors that influence their business. Responses might include introducing new offers, imposing eligibility criteria, or modifying existing business strategies. To change business rules that govern decisioning strategies and proposition management, business users use the Customer Decision Hub or Pega Marketing portal.
You can manage revisions of decisioning rules in business sandbox environments and monitor the effectiveness of decisions that are made in production environments in Pega Marketing and Customer Decision Hub portals.
Pega Marketing portal
Revision management involves two roles: revision manager and strategy designer. A revision manager initiates a change to business rules by creating a new revision. Each revision consists of one or more units of work that are called change requests. A strategy designer implements changes by amending the business rules that are part of a change request and reassigns the change request to the revision manager. The revision manager approves the change request and prepares a revision package for the system architect, who deploys the package in the production environment.
Changes to the rules are implemented through a change request or change requests that are part of a revision. Revision management of business rules is a multistep process that takes place in different environments and requires the Customer Decision Hub or Pega Marketing portal. The process to create a revision and export it as a revision package is based on the dynamic case management capabilities of Pega Platform.
Revision cycle of business rules
Perform the following procedures to modify business rules in your application and deploy them in the production environment:
The revision management cycle is complete when the system architect creates an application overlay with a set of rule instances to be placed under revision. Then, the revision manager uses the rules instances in the application overlay to create a revision with change requests and assigns the change requests to the strategy designer. After the strategy designer makes changes per the change requests, the change requests are sent to the revision manager for approval. Finally, the revision manager prepares a revision package with the changes so that the system architect can deploy it and activate the revision.
The revision manager can also initiate emergency rule changes through fast track change requests. This type of change request enables amending business rules urgently, without disrupting ongoing revisions. For more information, see Resolving fast track change requests.
For more information about revision management, see the Manage Business Rules Changes course.