Editing the same action in parallel

This video demonstrates editing the same action simultaneously in Concurrent Change Management.

U+ Bank is actively promoting its Premium Rewards Card through its website. One of the teams has already initiated a change request to add email channel and treatments, scheduled for deployment in the upcoming monthly release. Meanwhile, the marketing team recently identified a gap within the current action-level engagement policy. Anticipating that there will be more value added to the product, the team decides to modify the engagement policy to add an applicability condition using a newly created When Rule. The team aims to have this enhancement in the upcoming biweekly release.

To effectively address and manage these concurrent requirements, U+ Bank is taking advantage of concurrent change management.

Log in to 1:1 Operations Manager as a Business User. Navigate to the change request landing page and review the change request that has already been initiated to update the Premium Rewards Card action.

As a business user, create another update action change request. Remember to tag the change request to a release vehicle as required. Select the same action to update.

Notice that the status is Editable. This is because Concurrent Change Management enables multiple teams to edit the same business rules simultaneously.

Concurrent editing is a key differentiator from traditional change management, where the action would be locked until the currently in-progress update change request is complete.

Detail the updates for the selected action. Review the changes and submit, then complete the remaining workflow in the change management process until the status of the change request becomes Resolved-Completed.

Now examine how CCM works in the context of release vehicles. As a Release Manager, navigate to the release vehicle landing page. You can review both release vehicles, as mentioned in the Scenario. The treatment updates for the Premium Rewards Card are still in progress and are contained in the Monthly release vehicle, while the engagement policy change for the same action has completed and is ready for deployment in the Biweekly release vehicle.

Open the release vehicle and progress it to next Stage. Notice that because you used a non-deployed artifact, the system automatically detects and adds the respective change request as a dependent change request. This dependency management feature makes dependencies visible and manageable during the planning process, ensuring that all required components are properly coordinated.

As a Release Manager, you can now proceed with the release vehicle through its different stages until deployment.

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

• How to edit an action simultaneously in Concurrent Change Management.