{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32235,"path":"it-service-management/devops-change-velocity/update-change-model-in-pipeline.md","title":"Update change model in pipeline","bundle":null,"doc_type":null,"release":"australia","body":"\n# Update change model in pipeline\n\nUpdate the change model in your existing pipeline steps using the DevOps Pipeline Migration to Change Models catalog item.\n\n## Before you begin\n\nRole required:\n\n- sn\\_change\\_read role to read the change model from the chg\\_model table.\n- sn\\_devops.viewer role to read the pipelines from the sn\\_devops\\_pipeline table.\n\n## About this task\n\nIf you’re an upgrading user, and you want to migrate your existing pipelines steps to change models, you must perform this procedure.\n\nThe DevOps Pipeline Migration to Change Models catalog item enables you to update the change model in each step record in your pipeline at once. For example if you have set the type compatibility `com.snc.change_management.change_model.type_compatibility`  property to false and change model input is required in multiple pipeline steps, you can use this catalog item to update the change model for all pipeline steps in one go.\n\n## Procedure\n\n1. Navigate to  **All > Service Catalog > Catalog Definitions > Maintain Items > DevOps Pipeline Migration to Change Models**, and set the  **Active**  state to  **True**  to activate the  **DevOps Pipeline Migration to Change Models** maintain item.\n\n By default the catalog item is turned off.\n\n2. In the Available For related list of the catalog item, add the users to whom the catalog must be available.\n\n3. In the Approve By related list of the catalog item, add the users who can approve the catalog item.\n\n Alternatively, navigate to  **All > Flow Designer > Flows**, and activate the  **Request for pipeline migration** catalog flow. You can update the rule set in the  **Ask For Approval ** action of the flow to add a user or a group of users who can approve the catalog item.\n\n4. To add the catalog item in the Service Catalog categories in Service Portal, set the category of these items to  **DevOps**  and add the  **Service Catalog**  catalog.\n\n If the  DevOps  category isn’t available, you must create a new category called  **DevOps**  from the catalog item record itself and assign the  **DevOps Onboarding ** catalog to it.\n\n5. To add catalog item in Employee Service Center, add a new topic in the  Assigned Topics  related list with taxonomy as  **Employee**  in the  **IT > IT for IT ** section.\n\n The Assigned Topics related list isn’t available in the Default view of the **Catalog Item** form. To add it, select  **Additional icons > Configure > Related Lists ** and move the ** Connected Content → Catalog item**   field to the selected section.\n\n6. Navigate to  **All  >  Service Catalog  >  Catalog Definitions  >  Maintain Items**  and search for **DevOps**.\n\n **Note:** You can also access the service catalog from the  Employee Center  or Service portal.\n\n7. From the DevOps catalog items, select **DevOps Pipeline Migration to Change Models**.\n\n \\[Omitted image \"change-model-migration.png\"\\] Alt text: Catalog item to migrate DevOps pipeline to change model\n\n8. In the form, fill in the following fields.\n\n |Field|Description|\n |-----|-----------|\n |Tool|Orchestration tool that contains the required pipelines.|\n |Pipeline|Pipelines for which you want to update the change model.|\n |Change model|Change model to which the existing models are being updated.|\n\n9. Select **Submit**.\n\n A request is created. Based on whether the request is approved or rejected, notifications are send to the requester.\n\n **Note:** If any of the pipelines you selected in step 8 has any data policy, which doesn’t allow the pipeline steps to be updated, the same is updated as an error in the worknotes of the corresponding request.\n\n\n
\n\n**Approved and successful**\n\n\n\n- A comment is added in the request record specifying that migration to change model was successful. \\[Omitted image \"change-model-migration-success-comment.png\"\\] Alt text: Migration successful comment in request record\n- A bell notification is sent to the requester specifying that the migration has been successful. \\[Omitted image \"change-model-success-1.png\"\\] Alt text: Migration successful bell notification\n- An email notification is sent to the requester specifying that the migration request has been successful.\n\n\n
\n\n**Rejected and unsuccessful**\n\n\n\n- A comment is added in the request record specifying that migration wasn’t successful. \\[Omitted image \"change-migration-req-reject.png\"\\] Alt text: Rejection comment in request record\n- A bell notification is sent to the requester specifying that the migration request has been rejected. \\[Omitted image \"change-migration-bell-notification-reject.png\"\\] Alt text: Rejection bell notification\n- An email notification is sent to the requester specifying that the migration request has been rejected.\n\n\n
\n**Parent Topic:**[DevOps change models](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/devops-change-multimodel.md)\n\n"}}