Skip to main content

Challenge

Deploying a revision with a business change pipeline

6 Tasks

25 mins

Pega Customer Decision Hub 8.6
Visible to all users
Beginner Pega Customer Decision Hub 8.6 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

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 View the current state of the application stack and version

  1. On the exercise system landing page, click Pega CRM suite to log in to Dev Studio.
  2. Log in as CRM Decisioning Administrator with User name CRMDecisioningAdministrator and Password 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.
  1. In Dev Studio, click Configure > Decisioning > Infrastructure > Revision Management > Application overlays to view the application overlays.
    application overlay
  2. On the Application overlay tab, click BusinessChange to open the overlay application.
    Open application overlay
  3. In the Application Overlay section, click Edit Application to open the overlay application.
    edit overlay app
    Note: Business Change is the overlay application. It is built on PegaCRM_Marketing 08.01 (the enterprise application) and Ops Manager. The patch version should not be provided in the application ruleset version and should only include the minor version 01-01.
    The BusinessChangeRM is a branch of the BusinessChange ruleset. The current version is 01-01-01. This branch is the one to which the business changes are merged.
    overlay app rulestack
  1. In the Development Branches section, click BusinessChangeRM branch to view the rules that are ready for deployment.
    overlay app branch
    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.
  1. Close the BusinessChangeRM tab.
  2. In the Built on applications section, in the PegaCRM_Marketing row, click the Open icon to view the application stack and version.
    Open app
  3. In the Application rulesets section, in the BusinessChange:01-01 row, click the Open icon to view the ruleset versions available.
    open ruleset

    Notice that currently, there are 5 rules in the BusinessChange ruleset.
    Rules in a reuleset
  4. In the lower-left corner of Dev Studio, click the CA icon, and then select Log off.

2 Deploy the revision to production

  1. 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.
  1. In the navigation pane of Customer Decision Hub, click Revision Management to open the Revision Management landing page.
  2. On the Revision Management landing page, in the Welcome back, Revision Manager section, click Update business rules to open the revision.
    Open a revision
  3. In the upper right, click Actions > Deploy revision.
    Deploy revision
  4. Enter a comment, and then click Deploy to view the Merge status message.
    deploy revision comment

    The status changes to Open-Inprogress. Deployment starts after the revision changes are merged successfully.
  5. In the upper right, click the RM icon, and then select Log off.

3 Monitor the deployment in the business change pipeline

  1. Log in as Release Manager with User name ReleaseManager and Password install@1234 to open Deployment Manager.
    Note: Typically, this step is performed in the Orchestrator environment as the business change pipeline is configured there.
  1. On the Application Pipelines landing page, in the BusinessChange section, click BusinessChange 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.

business change pipeline progress

 

business change pipeline progress in prod

 

 

  1. Verify that the process shows that user action is required.
    business change pipeline user action
  2. 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 tage you have completed the BAU change request deployment inititation stage.
  1. In the navigation pane of Customer Decision Hub, click Revision Management to open the Revision Management landing page.
  2. On the Revision Management landing, in the Welcome back, Revision Manager section, click Update business rules to open the revision.
  3. On the banner, click Test or activate this revision to select the test users.
    Test or activate revision
  4. In the Test or activate this revision window, select Activate for all operators.
  5. Click Submit to display the message that deployment is activated successfully.
    test or activate revision options
  6. Click Complete revision to finish the revision.
  7. In the upper right, click the RM icon, and then select Log off.

5 View the deployment report

  1. 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.
  1. On the Application pipeline landing page, in the BusinessChange section, click BusinessChange to open the pipeline.
    Observe that the revision is deployed successfully.
     
    deployed change in business change pipeline
  2. In the Deployment History section, click View Report to check the deployment process details.
    view report
  3. On the Timeline tab, check the various deployment tasks performed in each environment.
  4. In the lower-left corner of Deployment Manager, click the RM icon, and then select Log off.

6 View the updated state of the application stack and version

  1. Log in as CRM Decisioning Administrator with User name CRMDecisioningAdministrator 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.
  1. In Dev Studio, in the Recents pane, click the BusinessChange application to open the overlay application.
    Business change app

Note that the version of the Enterprise application is now PegaCRM_Marketing 8.02. Also, notice that the application ruleset is BusinessChange: 01-01.

app rulestack
  1. In the Development Branches section, click BusinessChangeRM to open the branch.
    Note: Because the five environments that are used in a typical enterprise are combined into a single environment, this system also represents the BOE environment. Because all the rules from BusinessChangeRM are merged into the Business Change ruleset, the ruleset is now empty.
  1. Close the BusinessChangeRM tab.
  2. In the Built on applications section, in the PegaCRM_Marketing row, click the Open icon to view the application stack and version.
    open enterprise app

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

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

 

open a 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.

 

rules in ruleset version

 

 


This Challenge is to practice what you learned in the following Module:


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice