Deploying changes to production

This video shows you how to deploy changes that are made in the business operations environment to the production environment.

To create a new action that promotes credit cards use for utility payments, a next-best-action specialist, or NBA Specialist, has completed all the Build tasks and validated the generated artifacts, such as actions and treatments.

Then, the team lead promoted the change request to the revision manager to further push the change request to deployment.

The revision manager sees the change request is promoted to the.

As a revision manager, you need to push the changes made by the business operations team to the pipeline for deployment. Access the change request by clicking Revision Management in the navigation pane.

You can see the change request in this revision. Now, push the request to deployment.

Observe that the revision changes are first queued and then get merged to the deployment pipeline. Note that this process might take a while to load.

This pipeline enables a seamless experience to merge changes to the development system of record, version the application, and generate a release artifact.

Deployment Manager then deploys the artifacts to the production environment.

In the production environment, you can select a subset of users to test the modifications in a production environment, and then roll out the changes to all users when the test results are acceptable. In this case, you activate the change request right away.

Complete the revision.

You have reached the end of this video. What did it show you?

• How to deploy changes made in the business operations environment to the production environment.