Once your system is under change management, you must ensure that all next-best-action artifact changes are carried through a change request process. This means that changes to actions, treatments, next-best-action configurations, strategies, and other artifacts should be made by using either 1:1 Operations Manager change requests, or standard Pega Platform change requests.
Once deployment is triggered from the Business Operations Environment (BOE), the change request branch is published to the repository and is queued for a merge. The orchestrator assigns the task of merging to the Development (SOR) environment, and creates a new enterprise application version based on the changes.
You must create a product rule file in the Development (SOR) environment that generates the artifacts to the repository, and is used to promote the changes to other environments.
In the Production environment, you can publish the new application version to a group of test users for verification, and then activate or discard the changes for all users. After activating the changes in the Production environment, the application is updated with the latest version.
To learn more about the work flow of tasks that your operations team can perform in the BOE to test, change, and optimize your next-best-action configuration, see Business operations use cases.