all right well welcome everyone to today's process mining Academy session focused on automated findings which is available as of the Vancouver release so uh automated findings are complimentary to the existing rule based finding definitions some of you might be familiar with uh those are the things that come with the outof thebox content packs that we provide the big difference between the two is that with the existing finding definitions you had to kind of know what you were looking for ahead of time these automated findings will start servicing process and efficiencies and potential Improvement opportunities that you might not have even been thinking of um before we get started today I'd also like to mention that this happens to be our 20th process mining Academy session which is a nice little milestone for us uh the service now process mining team of course really appreciates your continued interest in the support of these sessions all right before we get to the main course let's quickly get the logistics out of the way uh the purpose of these sessions are to help us all get better educated on service now's process mining capabilities we'll provide how-tos practical guidance use cases product updates and just as a group exchange ideas and collaborate so we all continue to get better how the sessions work as some of you know we've got a scheduled topic that we'll cover usually for the first 30 minutes or so then we open it up for questions on the chosen topic for that session then we'll open it up for questions that go above and beyond what we've just been talking about sort of like an office hours uh these sessions are recorded and they eventually get posted on the community so you can find the complete library of the prior 19 sessions out there if you're interested in doing deeper Dives in any area of the product and then as we go through this today please post your questions in the Q&A section we answer them as quickly as we possibly can and then for those situations where we don't have an answer for your question immediately we typically follow up and post those answers in some form of a blog post or just on the academy session itself in the process mining Community page this is the slide that says hey anything we say and do here today can't be held against me in the court of law it's also the slide that says as part of these conversations if we make any forward-looking statements about what may be coming in future sessions or or releases um sorry not sessions but releases you should take those as forward-looking statements make no purchasing decisions based on them whatsoever because things are always subject to change and I'm assuming you've read the fine prints all right me uh for those that I've not met before my name is Dan Grady I'm part of the process mining product team here at service now what we'll do here today as always we start with the quick process mining 101 for our newcomers um and then we'll dive into the topic right we'll do our automated findings there's three specific automated findings that we'll cover here today that are available in the Vancouver release rework pingpong and extra step we'll talk a little bit about what goes into configuring those automated findings super easy but uh it's good to know where to find the things you can potentially adjust we'll jump into a quick demo in an instance so we'll show you an example of each of those three findings in action then we'll also go look at the configuration screens we'll get your questions answered we'll F just finish up with some additional resources that most of you are probably already familiar with but if this is your first time you might not be um and then we we'll get you out of here should be a pretty quick session today all right as always the quick process mining 101 for the newcomers with everything we do there's a designed and desired path in our minds for how it should work and how things should play out whether that be one of these account planning something like one of these Academy sessions or a business process and when we design things we design for both efficiency and a completeness to provide the best experience possible for as many people as possible now unfortunately what we design isn't always what ends up happening in reality the reality is that not all the work is going to be flowing through the process taking the optimal path and that's going to have a negative impact on the experience that both the employees requesting service might be having as well as the people that are trying to deliver that service now unfortunately identifying what is actually happening with anyone within any one of our business processes and then improving them isn't always that easy what process mining allows us to do is use the audit log data that is generated as records move through a given workflow or process and then we can use that data to create a visual representation of what is actually happening within a process and this new level of visibility is going to help us accelerate our ability to identify inefficiencies non-conformant process activities and Improvement opportunities so process mining gives us the ability to answer process questions that have historically been very Challen challenging to answer so whereas the more traditional analytics that we're used to will help us answer a lot of the what questions about our processes process mining helps us answer the wise so things like where is our process getting stuck where is any un unnecessary rework happening in the process where is work ping ponging between different groups or where aren't we conforming to the process that we've designed all things that have historically been difficult to answer and act upon they're now available to us in just a couple of using process mining we always like to say that process mining is going to get you to the why behind all of your process kpis and in doing so Empower everyone involved in the process to make data driven decisions about which improvements to make and we can apply process mining to a single table like this incident example here or we can take a multi-table approach so if you think about a process like requests that has both requested items with the approval steps that you might want to be looking for bottlenecks in as well as all the tasks involved to complete or fulfill the request you know might be looking for bottlenecks inside of there you can create these multi-dimensional maps and actually that's going to be the topic for our next session is multi-dimensional Maps but you can create these multi-dimensional maps to start looking for opportunities and these types of processes another common multi-dimensional example is an HR life cycle event like onboarding where you have a high level uh event or case and then a whole bunch of tasks and requests that come off of that and now as of the Vancouver release uh we can actually apply process mining to data that's imported into the platform from external applications like this hiring example that we have on the screen here in which we imported some data from Smart recruits all right now our topic today automated findings happens to be particularly useful for external data or app engine based processes where we don't offer out of thebox content packs with pre rebuilt rule-based findings so some of you may be familiar with finding definitions right for those that aren't finding familiar with finding definitions as I've mentioned a few time already they're they're rule-based they allow us to set up specific criteria that we want to look for in the data we are mining to identify inefficiencies so for example we might configure a finding definition to look for incidents that go directly from resolved and closed and never move into an open or in progress state or maybe we can we want to configure a finding definition to look for cases that take longer to two days than two days to route and less than two hours to resolve once they've been assigned both of those scenarios would be good starting points to look for automation opportunities maybe we can figure a finding definition to look for work that touches group a then goes to Group B then for some reason comes back to group a and less than 24 hours does it really have to go to group b in the first place the idea is that you can use finding definitions to test hypotheses and gather important data about the impact of certain scenarios to help prioritize which Improvement opportunities to act on now we also provide some of these preconfigured finding definitions as part of the workflow specific content packs that we offer via the store to help you get started and there's an academy session specifically focused on finding definitions if you want to go deeper I think it might be the fourth one that's out there now what about the process and efficiencies that are occurring that we haven't thought of right like this is where automation uh automated findings come into play and help complement the rule-based finding definitions there are common process patterns that we can detect and surface for you as part of your analysis and in the Vancouver release we introduce our first set of these automated findings with our rework pingpong and extra step detectors these are going to accelerate our ability to find Opportunities to improve and reduce some of the manual effort that goes into our analysis and we're going to cover each of these individually today and just so you know they there we've starting with these three in Vancouver but there are three or four more of these automated findings slated for the washingt release Washington release du out early next year now the first one we'll look at is rework rework is defi defined as a repeated action or process step right sometimes they may be necessary but many times they represent an opportunity to improve and remove some waste from the process so essentially with rework we're looking for things that go from let's say A to B to C and then at some point go back to a for some reason right so think reopened work or work that is going from in progress to a waiting Coler info and then back to in progress when we were we were thinking about rework we were thinking about repetitive repetitions at the activity or node level right so if you think I say activity or node for those that aren't familiar with the terminology those are the ovals on the map so we're focusing on seeing things go into an oval on the map more than one time now with pingpong we're focusing on repetitive arcs or transitions on the map so looking for work that is bouncing between two process steps or more like more likely use case would be bouncing between assignment groups so identifying work that's going from group A to B then back to a and back to b in a loop uh this type of bouncing can have a big impact on productivity even if it's just a handful of hours in each transition they all add up um and they aren't something that you're you're going to want to see in any sort of these are the types of things that you're you're not going to see in any sort of report that you're running right you could have a whole bunch of kpis and reports they're never going to be able to show you this this repetitive bouncing back and forth that's impacting your overall closure resolution times now the extra step is an interesting one and if anyone happens to be watching the Marvel show Loki on Disney plus you're going to love this one because we we get to talk a lot about variants um what what are we doing with the extra step detector or what we're doing is we're looking at all of the different routes or variants that work has taken to get to closure then we start comparing those routes and identify situations where we have a certain route and then a variant of that route that has just one additional step in the process that step again could be a necessary one or it might not be but the idea is that we'll surface these situations and the productivity impact of that extra step so you can start digging in and finding ways to eliminate the unnecessary ones uh so we may have a situation where the ideal path for work to take is a b c e uh but then we find that we have a variant of that route that goes a b c d e and when work goes through that dstep there's an additional four days added to the closure time of that piece of work so like why are things going to that dstep and can we avoid that happening and reclaim some of those additional four days so the ability to surface these extra step variants pretty powerful so those are the three automated findings that we've added in Vancouver now as you can imagine because we are automatically detecting and discovering these opportunities we have the potential to generate significantly more Improvement opportunities than in the past with just the rule-based findings so in order to help organize and make these things more consumable we've updated the summary and insights page in Vancouver right so um this just again designed to help us make it make it easier to consume all of these new potential Improvement opportunities that we're going to be surfacing so when we start to configure your findings both the rule-based ones and the automated ones you're going to be able to align them now to a category as well well as certain performance analytics kpis that these Auto these findings will potentially impact so this this will help us to to focus right you may choose to focus on findings that are impacting your closure time kpis first and then sort these findings by the volume of Records or the total impact um as we always like to say there's going to be no shortage of opportunities to improve your processes and and having the data you need to help you prioritize where to act first is really really important now in terms of configuration where do we configure automated findings well just like the rule-based finding definitions you're going to configure them in the process configuration record for the table that you want to mine um so you'll you'll see an additional related list in the process configuration um process configuration record um and to add or adjust these you you need to have the process mining admin or power user roles and you might be saying Dan you just said process mining admin or power user roles the slide says process optimization as most of you know in Vancouver we made a name change but under to the product itself but underneath the covers the roles still have the same same name there now configurate configuring an automated finding is pretty easy much easier than the rule-based finding definitions that you've worked with in the past the the first thing you need to do is you need to pick your type of finding rework pingpong or extra step uh then you pick the category um that you want for the the finding whether it be quality conformance performance or Automation and now I'm often asked about these categories and there's simply a way to help you organize your findings completely up to you what you choose the only impact they have is how things are going to be grouped on that summary and insights page so you may want to choose to categorize a rework finding on the State field as quality because it will be flagging work that is has to be done a second time um and if the quality of the work was better the first time we wouldn't have to be doing it a second time you may want to flag pingpong as a performance category because it's slowing us down extra step findings on state you may want to categorize as conformance because they could be situations that aren't aligning to the design path it it's really up to you how you categorize um so that's just something people often ask like what does this do it's just about categorization you'll need to pick the field or activity you want to apply the automated finding to most likely it's going to be state or assignment group then align the finding to certain kpis this is not required of course you may not even be using performance analytics um if you if you're not right if you don't align it to kPa you just might have some empty space on one of the widgets on your summary and insights page now for those of you that saying to yourself we don't use performance analytics but we like the idea of aligning it to Key performance indicator ators for organizational purposes one idea is that um you you you might want to use performance analytics manual indicators as placeholders so for those that are not familiar with performance analytics there's different types of indicators automated indicators or things that actually run and collect data from the platform itself but there there's a type of indicator called a manual performance analytics indicator that simply allows you to create a an indicator a kpi a metric and then you can type in the numbers if you want but it's a an easy way to kind of create a placeholder say hey you know what this is going to impact mttr so if you're not familiar with them dig into manual indicators then the last thing that you have to you have the option to configure is a few parameters for your finding you notice I've set this slide up for rework and pingpong um their parameters are the same and pretty straightforward you'll configure a minimum minimum that's easy for me to say minimum repetitions value so in the example here we're only we only want to surface the situations where the rework happened two or more times so it went back to the state of let's say in progress two or more times and the maximum findings that's how many findings do you want to surface on the summary and insights page and the example here uh will surface the the top 10 in terms of total productivity time so I often get asked about this total productivity time is the number of Records times the duration uh that you're you're seeing on the screen okay I know we've been on this slide for a little while but like in real life it takes a matter of minutes to create an automated finding I just wanted to call out all the individual pieces all right now for the the extra step detector there were a few more parameters and they are a little bit more confusing if you choose to play around with them um you can configure different minimum and maximum ratio values so you you have a main or parent variant and then you have the EXT step variant the first parameter is the ratio that sets the minimum number of Records an extra step variant needs to have in relation to the main or the par parent variant uh so the in the example on the screen we we have a value of five which sets a a five: one ratio meaning that the minimum number of Records needed for an extra step variant to be flagged would be 20% of the parent variant the second parameter sets a minimum number of Records an extra step variant would have to have to qualify to get flagged as a something we would put on the summary and insights page so in this case uh if there aren't more than a 100 records in that extra step variant it's not going to qualify we're not going to surface it on the summary insights page now just like the first parameter we can set a maximum ratio for the extra step variance so if we we set this value to one it means that an extra step can have up to 100% of the number of Records the par parent variant can have if we were to set this to two it would be up to 50% of the parent variance so um let's see math isn't my strong point but let's say if the parent variant had 500 records and we set this value to one we could have 500 records in the extra step variant if we set the value to two the extra step variant could have up to 250 records now the minimum step is exactly what it says it is the minimum number of steps needed to qualify as a variant the important thing to note on this one is that it includes the created and end steps in the count so you if you're thinking about steps in your head like new in progress to on hold to resolved to closed I think that was five you would want to set a minimum you would need to add two more um as your minimum because created and process end uh would would be included in that count now I don't anticipate anyone touching these initially and you shouldn't have to touch these initially but as people start getting deeper I I wanted to make sure that the recording had some explanation in in it for what you're going to see here all right let's uh jump on over to the the instance itself and hopefully I haven't timed out um we'll take a look at a couple of different examples so the first one we'll look at is this uh rework example so we'll come in here in this case I've mined my 27,000 incidents or 21,700 incidents you'll notice the the updated um summary and insights page where we've got our Improvement opportunities overview where we're grouping things by the category that we're setting uh the types of Records by the different types of opportunities as well as our linkage between the kpis that we've got there at the summary level then as we move down we get to the list of improvement opportunities and I can come down here and I'm going to find this one that's rework on a waiting caller info and I can see here rework on a waiting caller info the max number of times that something went into a waiting caller info we had at least one record that went into waiting caller info nine times there's 343 total situations in which if I click on this it'll tell us right rework on caller infro rework refers to a repeating step just like saw already but to apply for this Improvement opportunity the record needed needs at least three repetitions between a node the node repetitions can be interrupted by other not so three times so in this case here I have 343 incidents that went into the awaiting caller info state three times or more and one even went nine times here's the kpis that we've aligned this to that this potentially could be impacting here's the average duration of those 343 here's the total inefficiency see so those 343 times the average duration gets me to this 9 years and now we could go in here and say I want to look at in the workbench these 343 that went into that awaiting caller info state three times or more and it will narrow it down and what we can see here we've got our 343 records one interesting thing to do just to kind of point out what we've done here is if I click on this awaiting caller info let's just hide this click on this you'll notice with my repetitions histogram the distributions start at three and that's because we're only looking at tickets that went into the waiting C State info state three times or more and here's our one or two that went into it nine times throughout so you could always use the distribution uh piece here the repetitions to kind of answer some of these rework questions but it's nice to have them called out on that summary and insights page the other interesting thing to do here is now that I've identified these if I wanted to focus focusing on which assignment groups were the ones that are kind of involved in these situations in which we have to keep going back to the user for additional information we just use our breakdowns and I can see the majority of these that are going in and out of waiting Coler info more than three times have something or in some point are touching this it support America's team maybe we want to focus in on those so that's the rework example let's come over here and look at this pingpong example and in this case right I've chosen to set my project up with assignment group very very common assignment group as an activity very common for the ping pong situations I don't nearly have as much data or poor quality data if you will poor quality process information as I do on the the state side uh so I've got a number of different ping ponging scenarios here but the volumes aren't all that high and maybe I want to focus in on this one here in which I've got things bouncing back and forth between my it support Americas and support it group and I can see here the way that we've set this one up up is to apply for this Improvement opportunity the record needs at least two repetitions between the two nodes so at least two times going back from it support to support it to it support to support it right that's what that's what was the qualifier and these four records met that condition stats same as before and now if I wanted to focus in on these I could view these in the workbench and what we'll be able to see here just bring this down a little bit make it a little bit cleaner is I've got these situations where things are looping back and forth between these two groups one way to focus in on this if you've not been playing around with the process mining workspace before if you start doing your group analysis it's always interesting to use the variation analysis piece to come in here and say okay there's my one example where I've got one record that took one month and three days to go from it support America support it it support America support it right there's that transition that's repeating that's what we were flagging with our pingpong uh detector there or automated finding in this case here I can see that that transition happened let's just close this I can see that that transition it support America support it it actually repeated itself three times I andan it needs to be consecutive for it to be caught by the pingpong so support it support America support it it support America support it it support America support it those all qualified for that pingpong automated finding so this is just a different way to look at it but you can see what we're capturing in the data with the automated finding now if we were to look at the uh extra step let's use this hiring process data so the external data that we imported um as part of our last Academy session using our external data capability available to us in Vancouver these automated findings really really helpful uh for external data situations when we're importing the external data because if you're importing data we don't provide you any out of the out of the boox rule-based findings in some sort of content pack so the automated findings are great for helping you get a real good understanding of the data that you imported and where the initial opportunities might lie um so here if I come down on this we've already looked at rework well let's look at this extra step detector right so we find this one situation where I have these 259 records and what is telling me is that offer pending is an additional step between interview and for Approved right so it's looking at the different variants um of the the routes and it found the one that we've got kind of this extra step between so it's kind of easier to see this if I bring this into the workbench and when we narrow it down in the workbench it's going to show us only the two variants right so if I build this out it's going to show us both the parent variant and the EXT step variant here so I can see here's my parent variant let's close this right the one that kind of we looked at first created sourcing interview offer approved filled right and that was on average taking two months and two days seven steps and then here's the 259 that had that one additional step right the one additional step of offer pending and if we were to look at the map right we come down here we see okay great if I look at things that go these 259 that go into offer pending they're sitting there for an average of 2 days and 19 hours uh before they move to the next step so this piece here things that go into an offer pending right it's it's slowing us down almost by an average of three days so we might want to just focus in on on those 259 and understand why we have to go into that offer pending state so I can narrow it down to just those and then come over here to my breakdowns again and start digging into those a little bit deeper so very useful way to see if there's anything within a process that we might be able to to cut or pull out so three highle examples of one of rework one of the pingpong and one of the EXT step automated findings now let's jump over and just look at those configuration records so where does this get configured well we can come over here to our process configurations if we open up process configurations you're going to see that we have a record for every one of the tables that we've chosen to mine uh in this case and let's just open up the incident uh process configuration and you'll notice this is kind of as the Hub if you've not familiar with the process configuration it's the Hub of what you would configure all the different things you would configure for a given um process that you want to M you'd set up your automated root cause analysis Fields here your automation Discovery taxonomy here any sort of cluster analysis configuration you want to do get set up here the rule-based finding definitions that come with the content packs and the ones that you get you create on your own you do that here as well um and then you'll notice now in Vancouver you have an additional tab uh called automated finding definitions and this is where you configure those you've see that I've already created a bunch for the examples that we've looked at in the little demonstration here but let's just create a new one real quick so you can see what that looks like uh maybe we want to create one that looks at rework on the priority field right you want to find situations where priorities are being swapped or changed quite frequently um in the the process we can choose our rework type we'll choose our category I guess if things are the priority is changing or bouncing back and forth more than once maybe that's a conformance issue so let's let's flag it as conformance what field do we want to apply this to let's apply it to our priority field and then what kpis with this impact right again not required but maybe we want to you know head a kpi of mttr to help bucket it on that summary and insights page and we'll hit submit or we can say save and once we save this you'll notice that our parameter screen comes up here so one is the max findings so how many examples of rework on priority do you want to show in that summary and insights page once we run the model and then our minimum repetitions what's the least amount of times that something has to change priority or had the priority change before we we flag it or go into a certain priority so let's say more than two times or two times or more in goes into the priority of critical right that would be something would be flagged here we can update this it would be there and away we go now I do want to show you one other thing uh as part of this because this is a little bit of change in um in Vancouver how do we get these findings or automated findings into a project so we'll come here we'll create a new project we'll say incident and we'll just hit save we'll choose our table like we always do and we'll say incident choose our table of incident of course we'll say active is false but this isn't important because I'm not actually going to hit the mine button today but you always want to make sure you're you're mining closed records and then we hit save in this case let's just add our activity of priority so we'd be looking for priority changes on the map I'm not going to add any breakdowns because the point of me going through this exercise for you is just to come to show you now prior to Vancouver once you pick that table of incident anything from that process uh configuration record would be pulled in right we would already start seeing our finding definitions here no longer the case right now what you have to do is you have to hit this import process finding templates and what it's going to do is it's going to go out it's going to look at that process configuration record and then pull in the process finding definitions or the ones that were more rule-based as well as the automated finding definitions that we we had at that in the process configuration level and then once you're here you can open up any one of these automated findings and let's say that we want to look for things are going into a certain priority more than three times you can actually adjust the parameters at the project level you don't have to always adjust them at the process level so I just wanted to show you that a little example because that's something that is a little bit different in Vancouver you might be creating project you're like hey where are my automated findings just make sure that you've you've imported them into the project that you're mining all right I think that's what I wanted to cover in the instance let's jump over and see if anybody's got any questions so if you had questions about anything that we covered could you please put them in the oh looks like we had questions put them in the Q&A in the chat but um I'll I'll just read them aloud thank you your room for answering the questions as I was presenting it's always good to have you here with me but um there's a question in case of rework what about those scenarios where we intentionally want work to go to a to verify or for B yep this could be fine like not all the findings so this is the situation the automated findings and this is also a thing about service management right we designed for both completeness and efficiency so there going to be situations where those things should be happening um but there's also going to be situations where they they shouldn't be happening so the idea is that maybe you want to adjust the parameter to see the situations where that thing is happening more than once like things that are going into a waiting call or info three four five times that's there's got to be something that we could could be doing better there right like if there's a high volume of those situations in a certain category of ticket like what can we do be doing better is there something that we can improve to do to improve the intake experience so yeah some of these situations are going to be totally valid by but identifying situations um where you know they're calling these things out it's I always like to compare these automated findings to kind of like a dating app like we're going to surface a bunch of things you can choose to swipe left or swipe right on them but we're just making you aware that these things are going on can we also look at the actions that we need to take for these process gaps and uh yep so I think the the idea here if I'm understanding the the question is like Hey we're identifying these situations like what are the next steps or actions that we should be taking totally there's lots of different ways to continue to dig into the data and look for the types of things that you should be doing um as Yun pointed out in the answer in the Q&A there's things like root cause analysis or cluster analysis to help us look at the short descriptions and the descriptions the unstructured data around these tickets to help us kind of dig deeper into the data this solution process mining is all about kind of narrowing uh the data down to where there might be opportunities and continuing to then have a conversation with the data to ask it additional questions get additional answers to help you understand what actions you could be taking inside of it so there's other things we didn't them in the session here today um but if you go back and look at some of the other prior Academy sessions we have there's specific sessions that about how to use the solution and different aspects of the solutions to identify next best action or things that you should be following up on perfect does anybody else have any additional questions uh that they didn't put in the Q&A as of yet all right as we wait I'll give you a couple more minutes to get some questions in uh just some additional resources above and beyond what we covered here today um so just for those that are not aware there is a now learning course out there on the now learning site um called process optimizations essential process optimization Essentials we're in the process of updating that and renaming it but there is a course there that gives you some of the basic foundational information that you need we of course use process mining here at service now and the team our now on now team has written a really good white paper around how we've approached process mining from an organizational perspective and then some of the initial findings that we had across I think five processes that we they documented in here there's a community Forum page you probably already know that that's likely the way that you found how to register for this session here um but if you if you've not found it go to the service now Community or community. servicenow.com search for process mining it'll take you to the form we check this every single day for questions and feedback from our customers so if you've got a question that you you don't want to answer or ask here please post it on that site we'll answer it as quickly as possible and there's tremendous amount of content out there for you um on that page to to learn more one of those things are these process of mining Academy sessions as I mentioned earlier this is our 20th Academy session so there's lots of other recordings of different aspects of the solution right like the question that we just had in terms of like how do I figure out kind of now that I've narrowed it down what types of things I potentially could do to act on this whole session on kind of how you dig into the data using root cause analysis uh to help you do that type of thing so go out check out those other Academy sessions the other thing that's out there that we're trying to supplement these Academy sessions with is we recognize that process mining might be a new muscle for many of our customers but there's common types of things that you would use process mining to ask and answer so we've started this use case series which is a series of five minute videos focused on a specific type of analysis that you might want to do like SLA breach analysis or that example of work that's taking longer to Route than to resolve we just recently posted a use case that was focused on how do you use process mining to identify approval bottlenecks in the process so I think there's eight of those out there now um and there's there use cases that you're interested in us doing a quick little how-to on please post to the community the site and we we'll follow up with that and then the last thing that I'll leave you with is this live on now session um so in terms this this is a good session to watch if you want to focus in on what plugins do I need to turn on how do I create my first project um and kind of what is the vocabulary of process mining we cover all of that in that live on now session with that I'll give you guys the the group one more chance to to ask some questions any questions please put them in the Q&A uh anything that we haven't um answered yet uh there is a question about the slide deck the slide deck gets posted to the community site so if you go to the process um I would say the fastest way Google service now process mining Academy it'll take you to the process of mining Academy page with all 20 recordings that are there or all all the session recordings that are there if you drill into any one of the sessions uh We've attached the a PDF of the PowerPoint deck in each of the individual sessions so I usually get the recording out um the day of this so we uh um you know give me a few hours I got a few more things on the calendar here today but it'll be posted at some point today um on the community site and the deck will be attached to this session so that's where you can go pick that up any other questions last chance for romance um get those questions in uh just so you know um today is we're doing our automated findings deep done the last process mining Academy session for this year will be uh in December we're targeting December 15 um and we've had many requests for uh session on multi-dimensional maps so those Maps where you you know let's say we're looking at a request requested item and the the SE tasks associated with it or an HR life cycle event that's got that high level case and then the subtask so uh we'll spend the last session of the year on those multi-dimensional Maps there's been a lot of enhancements made to them over the last couple of releases so it's it's a good time to dig into how we can figure those and then how we interpret those maps and where you potentially could use them so that's going to be the session uh for 12:15 um and that'll be the last one for the year with that any last minute questions if not really appreciate uh your attendance as always and look forward to your questions on on the community or meeting you in person at some point at some event um and uh don't ever hesitate to to reach out thanks everyone see you next time