Deploying a revision with a business change pipeline

6 Tasks

25 mins

Visible to: All users

Beginner

Pega Deployment Manager 5.5

English

Scenario

The business content team at U+ Bank has worked on the Business Operations Environment (BOE) to implement some business changes. The bank has a business change pipeline configured in the Orchestrator system to deploy changes from BOE. They now want to deploy the business changes made in BOE with the business change pipeline.

Use the following credentials to log in to the exercise system:

Role	User name	Password
System Architect	SystemArchitect	rules
Revision Manager	RevisionManager	rules
Release Manager	ReleaseManager	rules

Your assignment consists of the following tasks:

Task 1: View the current state of the application stack and versions

As a System Architect, navigate to the overlay application to view the current state of the application stack and versions.

Note: Typically, this task is performed in the Development environment because it acts as the system of record and contains the product rule that defines the application package. For training purposes, the five environments that are used in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, you check in the same system.

Task 2: Deploy the revision to production

As a Revision Manager, deploy the revision to the production environment.

Task 3: Monitor the deployment in the business change pipeline

As a Release Manager, monitor the revision deployment in the business change pipeline to view how the changes are promoted to each environment defined in the pipeline.

Task 4: Activate test users to test the changes and complete revision

As a Revision Manager, activate the test users to test the changes before deploying the changes for all end-users in the production environment and complete the revision.

Task 5: View the deployment report

As a Release Manager, ensure that the deployment is successful and view the reports in the Deployment history section to check the process details.

Task 6: View the updated state of the application stack and versions

As a System Architect, navigate to the overlay application to view the updated state of the application stack and versions.

Challenge Walkthrough

Detailed Tasks

1 View the current state of the application stack and version

On the exercise system landing page, click Pega Infinity™.
Log in as System Architect:
In the User name field, enter SystemArchitect.
In the Password filed, enter rules.
Note: Typically, this task is performed in the Development environment as it acts as the system of record and contains the product rule that defines the application package. For training purposes, the five environments that are used in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, you check in the same system.

In Dev Studio, click Configure > Decisioning > Infrastructure > Revision Management > Application overlays to view the application overlays.
On the Application overlay tab, click OLSTDRCDH to open the overlay application.
In the Application Overlay section, click Edit Application to open the overlay application.

Note: OLSTDRCDH is the overlay application. It is built on CDH (the enterprise application) and OpsExtCDH (the Operations Manager application). The patch version should not be provided in the application ruleset version and should only include the minor version 01-01.
The OLSTDRCDHRM is a branch of the OLSTDRCDH ruleset. The current version is 01-02-01. This branch is the one to which the business changes are merged.

In the Development Branches section, click OLSTDRCDHRM branch to view the rules that are ready for deployment.

Note: This ruleset contains a set of rules resulting from a BAU business-as-usual change made by the business in the BOE environment. The BAU change introduced a cashback offer.
Typically, this step is performed in the BOE as a business-as-usual revision/change request is initiated from there.

Close the OLSTDRCDHRM tab.
In the Built on applications section, in the CDH row, click the Open icon to view the application stack and version.
In the Application rulesets section, in the OLSTDRCDH:01-02-01 row, click the Open icon to view the ruleset versions available.

Notice that currently, there are 109 rules in the OLSTDRCDH ruleset.
In the lower-left corner of Dev Studio, click the System Architect icon, and then select Log off.

2 Deploy the revision to production

Log in as Revision Manager with User name RevisionManager and Password rules to open Pega Customer Decision Hub.
Note: Typically, this step is performed in the BOE as a business-as-usual revision/change request is initiated from there.
For training purposes, the five environments that are used in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, you check in the same system.

In the navigation pane of Customer Decision Hub, click Revision Management to open the Revision Management landing page.
On the Revision Management landing page, in the Welcome back, Revision Manager section, click Update business rules R-1 to open the revision.
In the upper right, click Actions > Deploy revision.
Enter a comment, and then click Deploy to view the Merge status message.

The status changes to Queued for deployment. Deployment starts after the revision changes are merged successfully.
In the upper right, click the Revision Manager icon, and then select Log off.

3 Monitor the deployment in the business change pipeline

Log in as Release Manager with User name ReleaseManager and Password rules to open Deployment Manager.
Note: Typically, this step is performed in the Orchestrator environment as the business change pipeline is configured there.
On the Application Pipelines landing page, in the BusinessChange section, click BusinessChanges to open the pipeline.
Notice the progress of the deployment.
Note: It may take a few minutes until all deployment tasks are completed in each environment. Wait until an action is required.
Verify that the process shows that user action is required.
In the lower-left corner of Deployment Manager, click the RM icon, and then select Log off.

4 Activate the test users

Log in as Revision Manager with User name RevisionManager and Password rules to open Pega Customer Decision Hub.
Note: Typically, this step is performed in the BOE as the deployment step is initiated from there. At this stage you have completed the BAU change request deployment inititation stage.
In the navigation pane of Customer Decision Hub, click Revision Management to open the Revision Management landing page.
On the Revision Management landing, in the Welcome back, Revision Manager > Revisions section, click Update business rules to open the revision.
On the banner, click Test or activate this revision to select the test users.
In the Test or activate this revision window, select Activate for all operators.
Click Submit to display the message that deployment is activated successfully.
Click Complete revision to finish the revision.
In the upper right, click the Revision Manager icon, and then select Log off.

5 View the deployment report

Log in as Release Manager with User name ReleaseManager and Password rules to open Deployment Manager.
Note: Typically, this step is performed in the Orchestrator environment because the business change pipeline is configured there.

On the Application pipelines landing page, in the Olstdrcdh section, click Business changes to open the pipeline.
Observe that the revision is deployed successfully.
In the Deployment History section, click View Report to check the deployment process details.
On the Timeline tab, check the various deployment tasks performed in each environment.
In the lower-left corner of Deployment Manager, click the Release Manager icon, and then select Log off.

6 View the updated state of the application stack and version

Log in as CRM Decisioning Administrator with User name SystemArchitect and Password rules to open Dev Studio.
Note: Typically, this task is performed in the Development environment as it acts as the system of record and contains the product rule that defines the application package. For training purposes, the five environments that are used in a typical enterprise are combined into a single environment that acts as the orchestrator and four candidate systems. As a result, you check in the same system.

In Dev Studio, in the Recents pane, click the CDH Standard release application to open the overlay application.

Note that the version of the Enterprise application is now CDH 01.01.02. Also, notice that the application ruleset is OLSTDRCDH: 01-02.
In the Built on applications section, in the CDH row, click the Open icon to view the application stack and version.

Note that a new enterprise application was created with version 01.01.02, and the OLSTDRCDH application is now inheriting from this application. This new enterprise application has the merged ruleset version (OLSTDRCDH:01-02-02).
In the Application rulesets section, in the OLSTDRCDH:01-02-02 row, click the Open icon to view the ruleset versions available.

As the Release Manager created the pipeline configurations, the branch was merged as a new ruleset and is locked.
In the All rules column, click 38 to open the new ruleset version.

Note that this ruleset also contains all the rules added in the BOE system branching ruleset and is now available in the Development system.