this video is going to look at two important tables behind flows subflows and their executions in service now so I'm in service now workflow Studio which is part of the Washington DC release uh so this was formerly known as flow designer and in here I get uh when I go to the flows list I can see a list of all my flows and here I can see a list of all the subflows in the instance and so the question is uh where is it getting this from right where is the table because in workflow studio and in flow designer before this you can't see what the table name is from the URL it's not uh it's it's not listed there you can't see it on this video either because I have the screen cut off uh below that but uh you you can't see like you can in in the classic UI where it's coming from so we're just going to go take a look at this same table in the classic UI so I go over here to my my classic UI whoops I already had it fired up here so I go over to the filter Navigator uh to the Navigator and I go cisor hubor flow. list and here I'm going to get the same table and so this table actually contains both flows and subflows so if I wanted to just see flows I'm going to put the flow type column uh make that visible and do a show matching on it and so this is uh just my flows uh from this same same data uh just a different UI um so why would you want to go in here uh to see it in classic UI instead of just using it in here uh well to be honest uh there is a lot less of a reason to do that now than there was a few versions ago uh because service now has brought in a lot of the table functionality um into this UI right so you can now choose columns that you want and uh I think you could do filters before but uh um right and primarily before the reason I used to go into the classic UI a lot to get to the table was because if you did filters and this has been fixed so if you did a filter so let's say I want to do right I only want to see visual taskboard spoke flows and I open one up uh previous ly I think this is like Utah and before or maybe Tokyo and before if you went back to the flows tab it would lose your filter so that that made me crazy and uh so that was a good reason to use the classic UI but as you can see they fix that because it keeps the filter so that's not really a good reason anymore to uh to do that to to look at it in the classic UI however there are still some functionalities in the classic UI that the new UI doesn't have uh and probably the most important of those is the export functionality so if you you know had a whole bunch of flows that you just wanted to export to um XML for example to you know back them up or whatever uh you can do that from classic UI you can't do that from the new UI yet I'm sure they will add it at some point uh so cisor hubor flow is both your flows and your subflows uh just one more note in here is uh since Washington DC and the Advent of workflow Studio you these no these links no longer work anymore so you used to be able to fire this up from the classic and I'll just do it uh in another tab here and it used to fire up the flow in flow designer but uh this doesn't work anymore we get this error message about asset not found so I think the redirects are broken or whatever I'm sure they'll fix that okay let's go to the second table that is uh important and interesting and that is what we see in workflow Studio or in Flow Design in workflow Studio it's called operations in uh flow designer it was called executions uh operations is a much more friendly name and so this is if we go to flows over here these are all of the flow execution contexts uh so all the flows that have run uh so we can see you know what happened with them um so if we go back to the classic here these are found in CIS uncore uh flowcore context I do a do list and again I just see exact same data uh just in a different format here uh just in the in in this UI um I will point out a an important column or important columns in this uh in this table and that is the source table and the source record columns so these are not visible by default you have to go into uh edit the column list and put them in there but the source record table will it contains the CIS ID of the record that the flow uh op was triggered from um so you can see I have this test flow that I had for another video and I can see that the executions uh are affecting this so the reason why this column is useful is let's say you have a record and let's go to my incident table and let's say I have a record uh you know this one and there are let's say there's a bunch of flows on this and I'm trying to figure out how the heck did this data get changed what uh what happened and so I will copy the CIS ID of this record and I'll go into here or I can go into the classic view to the CIS flow context table but you can do it in here uh go to the source record to a filter is and I throw the CIS ID in there of the record and it's going to bring me up all the contexts that are that were triggered by that record uh so I can see this is one of them and um I don't have reporting turned on but normally right you click on that and it brings you to the execution of that you can see what happened uh so super useful column when it comes to debugging and troubleshooting figure out what the heck happened with a given record so those are two uh really useful uh tables that are behind flows subflows and their executions in service now