Managing change requests in a release vehicle

This video demonstrates how to manage change requests in a release vehicle.

U+ Bank uses Pega Customer Decision Hub™ to deliver personalized offers to its customers. Following extensive research conducted by the marketing team, the bank decided to introduce the following four new offers to target different customer segments in the first quarter of the year:

• Premium Rewards Card: A credit card for high-value customers.
• Edu Flex: An educational loan for existing customers.
• First Home: A special rate mortgage offer for first-time buyers.
• Family Shield: A comprehensive family protection insurance plan.

Multiple teams are working on these change requests. As the change requests progress through various Stages, the bank  wants to place the educational loan offer on hold to address new legal compliance requirements and delay the mortgage offer to allow more time for completion. However, the credit card and family insurance offers must proceed as planned. To address these challenges, U+ Bank has enabled Concurrent Change Management (CCM), which allows teams to work simultaneously without conflicts.

A release vehicle manages associated change requests as a unit and ensures that all changes progress through the generation, testing, and deployment Stages in a controlled manner.

As a Release Manager, log in to 1:1 Operations Manager and open the Release vehicle landing page.

As mentioned earlier, U+ Bank wants to implement the changes for the first quarter. The bank has already created a release vehicle named Quarter 1 Release and tagged the respective change requests during the creation of change requests.

The release vehicle is currently in the Plan stage. At this stage, you can add, remove, and reorder change requests.

The section provides an option to add change requests. This opens a dialog box that displays all change requests and allows you to select and add based on your release plan. 

To disassociate a change request from a release vehicle, you can either move it to another release vehicle or remove it from the current one.

You can reorder change requests in the release vehicle. If multiple change requests in the same release vehicle modify the same attribute of the same Rule, the system determines the final value according to their order in the release vehicle. It applies change requests from top to bottom, so the change request that is lower in the list will override any previous changes.

In the current scenario, the bank wants to proceed with the credit card and family insurance offers. Remove the other two change requests from the release vehicle, and then proceed to the next Stage. After you submit, the status of the release vehicle updates to a Pending‑Generate status, which indicates that the release vehicle is ready to generate.

This scenario illustrates a key benefit of Concurrent Change Management. Teams that work on the credit card and family insurance offers can proceed independently without waiting for the completion of the student‑loan and mortgage offers.

You have reached the end of this video. You have learned:

• How to plan a release vehicle.
• How to add, remove, and reorder change requests in a release vehicle.