[Music] hey everyone it's justin thank you for watching in this video i'm going to continue the conversation around devops or servicenow devops and i'm going to keep this one short and really about the change policy okay so if you've made a code commit and you've got a pipeline going and you've configured that to open a change request and service now you can have that change request follow a different process and that different process this is a demo example is using looking at uh different data points so it's gathering some information about the committer about the test results how many percent have passed stuff like that in this demo example and then it's applying a change policy based on the results and so you can see here if i scroll down a little bit it might auto approve the devops change or it might do an assignment and actually assign somebody to approve that change and you do that configuration when you're setting up devops within servicenow what i want to show you this i think it's really cool if we go to the actual decision table that's doing that that particular change i'm going to go into this devops demo change policy because that's the one i was messing around with as i was working on a demo for a potential customer and what's neat and i found well you're gonna get a super here too the decision tables themselves are pretty neat it's pretty neat features so if you haven't seen this already you should definitely check it out but look on the just to my just over here this direction i have the two inputs coming in that how many commits have no work items associated with them and how many tests passed or what percentage of tests actually passed and so i use those here in this decision table and based on certain conditions is the testing results empty are there commits without a work item how many commits have a no work item is it zero is it one is it greater than five you can put whatever structure you want around that and then apply these different policies you see over the right so notice i've got devops auto approved versus assignment group approval and i've got in my instance about four different ones of those based on that here's the message i want you to take away from this you can use those insights i talked about in a previous video i showed a dashboard to drive and improve accelerate or slow down your change process as needed so your job in a a good it organization is to keep things stable but still respond to your customers requests your users requests and rollout enhancements so with devops you can use this decision table and the change policy and the workflow associated with that change to route that change to different places make it be auto approved gets it out faster you know do a group approval gets it to the group for somebody to approve that group could even be cab like i talked about my previous video i hope you found this video helpful if you did please like please subscribe or share it with somebody you think might be interested and until next time don't forget to always be learning [Music] you