Skip to main content

 –

Getting ready for business changes

Suggest edit Updated on September 21, 2021

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 done by using either 1:1 Operations Manager change requests, or standard Pega Platform change requests.

Once deployment is triggered from the Business Operations Environment, the change request branch is published to the repository and is queued for a merge. The orchestrator assigns the task of merging to 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.

Business pipeline for promoting regular application-level changes
Business pipeline for promoting regular application-level changes

    • Previous topic Getting ready for enterprise changes
    • Next topic Creating operators in the Business Operations Environment
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

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

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us