-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service Now Change Management - Transmitting Change Request Number as an Output Variable Between Stages. #1207
Comments
I have been looking at the same thing. You don't need to do that at all. UpdateServiceNowChangeRequest@2 task will query for the change request number first if not provided. It will get the change request number created by the approval gate (uses some correlation id behind the scenes to query for it).
|
@aczarkowski Thanks for the yaml it helped me big time, I was really excited after finding your yaml. I have another question I am using environment approvals and check at the prod deploy stage to check if the change ticket created during the dev stage is in a certain status now my question is how do I pass the change record number dynamically in the environment at the approvals and checks so that the valdation can be done on the exact change which was created during the dev stage. I am a beginer in yaml and ado so I would really appriciate all you inputs here thanks. |
Is it possible to designate "Change_Request_Number" as an output variable in a YAML pipeline, similar to the approach used in a classic release pipeline?
This is how it is being done in classic release pipeline.
We aim to use the Change Request Number in a subsequent stage to perform an update on the corresponding change request.
The text was updated successfully, but these errors were encountered: