hello and welcome everybody this is our i think 20th um platform academy um today i'm being joined by jason lefevre and i have my colleagues daniel and mark in the background as usual um this session will be about getting started with process automation designer thank you everybody so much for joining um we have just crossed our one year mark last week so thank you for staying with us for a whole year i hope the upcoming sessions will be interesting to you too as always this uh this webinar is being recorded and will be added to youtube um hopefully tomorrow and with that i will get into things so my name is lisa i'm an outbound product manager for servicenow and i cover workflow automation products i've been working with the now platform for about six years and i've been with servicenow for three and a half of those i'm being joined by as i said by jason lefevre who's the outbound pro inbound what is it he's the product owner for process automation designer um please give a little introduction to yourself hi everyone uh greetings from wherever you're joining us around the world uh as lisa said i'm jason lefevre uh i am extremely passionate about low code development and so my area of expertise is process automation designer our low code business process management digital process automation solution we'll be diving into some details here and hopefully getting you excited about the possibilities uh for for driving process automation within your organizations sounds good so let's dive into things um i don't think we're going to be covering a lot of forward-looking statements this time we're very close to the ea period so actually our next session which will be in exactly four weeks on august 4th will cover the second side of processes so today we will be focusing on process automation designer in four weeks we will be covering playbook experience so make sure to rejoin us at that day to learn more about the user experience side of processes in the now platform and i i really want to encourage you to check out both and learn about both and take the training that is out there as well and as i said we don't we won't be going into too much forward-looking details today so there's no safe harbor slide but next time is ea period for the tokyo release and that means we can start talking about the enhancements to process automation designer and playbook experience with the tokyo release so be sure to check that out and just to give you a small um info on the agenda so mostly we're we're speaking about process automation designer will touch a little bit on playbook experience and then as time permits uh jason will give us a small tour through a live demo of the product and then we'll wrap it up at the end all right some abbreviations that you will find us uh using our pad for process automation designer pd sometimes for the process definition um and then also pe for playbook experience as well as fd or flow designer like that and then we always love to uh use our quotes we used to always use quotes by fred luddy who wants to work through the enterprise but we have a new ceo and he um likes to emphasize that uh the now platform helps to work to flow naturally so uh whenever work flows then great experiences follow and that's really what we want to achieve with process automation designer and playbook experience as well so why did we start to create this product when there's already flow designer and and business rules on all kinds of options to create processes and to have your say task life cycles be routed and and stuff like that so there are a lot of problems to the back ends when it comes to complex processes before the introduction of pad you would always need servicenow pro developers to connect multiple services and departments with processes in the legacy workflow world with business rules and script includes it's really hard to identify what drives a given process at which stage so artifacts are disconnected as well second you can you cannot easily modify such a process as changes are being being made for each individual use case most importantly it's really hard to gain insight into the full picture of a process and there's no single process view that you can look at to understand the nested relationships between the teams and the tasks involved in the service a small dive into the playbook experience side so what are the problems that agents will face when dealing with complex processes so first of all they cannot also cannot see all of the components and steps that make up the process they will need to drill in and out of related tasks and navigate to other parts of the platform it takes quite a bit of training effort to make the agent understand which step comes next in the process they must analyze the forms and notes to find the right path and figure out the next step and when changes are being made to a process additional training and documentation is needed to make sure that the agents know to follow the process and then lastly there's no again there's no single view to make out where in the process the agent is and which steps are required to proceed i don't know how often i had people call me when we first started using servicenow when i was a customer and they would be like i don't know i need this change to proceed but i don't know which button i have to press or what is the state what does it need what do i have to do to get to the end and solve this case or close out this incident or change or whatever process the people were working on so what we wanted to do is introduce a way to make that visible to all of your agents so this is the need for process automation designer we have many applications and teams in servicenow today that may participate in business processes simple processes are still easy enough to handle in the flow like straightforward requests that only require an approval and a task or two it gets much more complicated once different departments are involved for example when requesting a new test these kinds of processes hand over info and tasks from one team to another and involve different departments too it gets even trickier when looking at complex connected services that spend multiple departments and teams to fulfill a prime example is any onboarding process be that employees customers or vendors procure to pay processes spending from expense pre-approval over fulfillment and hand over to your account account software for payment and the other end is a good example process automation designer will then provide you with a clean lookout interface to plan and create enterprise service processes to make the process transparent to the end user and reuse existing business logic for your process activities to do that our product vision for process automation designer is to provide business owners business process owners a builder to digitize visualize and manage end-to-end workflows across business services our product vision for playbook experience is to provide a way to visualize and interact with business process workflows in real time via a simple task oriented view and we also want to ensure consistent response to commonly encountered situations we're really flying through this thing but i've done this before and you will notice there's actually training and there's there's two creator con labs that i did during knowledge if you want to learn hands-on that's where you need to go so i will put i have those links in the presentation notes and i will also put them in the youtube description and in the community post so you can go ahead to now learning and do the training on demand and learn these things by yourself in a real instance and with a prepared use case so what are some of the biggest product benefits for pad and playbooks we offer a no-code process authoring experience to model an enterprise workflow and it lets you coordinate manual automated and integration process activities these steps and lanes and phases can run in parallel or sequential and you can also make use of data flow so like you are used from flow designer you can hand over data from one step and one phase to another so any subsequent steps have access to the outputs of the previous activities and speaking of loca the low code flow designer is highly integrated into this product it's basically the the fiber that keeps everything together so each of the activities will run based on a flow subflow or flow action and that means you can easily extend this with your own logic and use your existing subflows for process automation design and then on the front-end side everything can be integrated into a configurable workspace so the newer next experience workspaces can easily show your playbooks in a playback component and therefore through that offer progressive guidance to your um uh to your agents you can also extend this with other now platform capabilities so for example you can surface um sla timers on the individual activities in the playbox so that they know what how long they still have to complete a certain step so i've already mentioned process automation designer and playbook experience those are basically two sides of the same coin process automation designer is the design design space the back end the authoring tool how to create your cross enterprise workflows in to a single and unified process playbook experience on is a ui platform for viewing and interacting with business process workflows in real time both products can function independently of each other but provide the most value when used together and to give you a small insight we'll see more when we look at this live in an instance later but the general outline of a process is you will have the process definition that's the top level record you will have a trigger for your trigger table and define when this process runs and this at this spot make sure that you don't have uh duplicate triggers in flows and processes um unless that's on purpose so be mindful on when different processes and flows will trigger off the same records on the same table um to not duplicate flow logic or logic and then the top level record as the trigger record the process will contain one or more multiple lanes each of the lanes can contain one or more process activities on each of those can run in parallel one after the other only when the previous one has completed immediately so a lane set to immediately will run whenever the playbook is the process is triggered um an activity in each lane will set to immediately will run as soon as the lane starts you can also add conditions to both of those so you can make uh one one activity conditional it only starts um if the output of a previous one is a certain value you can add timers to this so you can have some delay and start a whole lane or individual activities with a delay if you want to playbook experience the playbook experience component within the workspace is the the parent record so you will see the playbook attached to a given record um each record will show different stages you can have multiple playbooks running playbooks per record so you can actually have multiple instances of the same process running or you can also have different processes trigger of the same um of the same record um each of the stages will then show the different activities and and those represent the activities that you've seen in the designer additionally you can also add declarative actions at playbook stage or activity level those are more like buttons more or less buttons that you can configure to trigger any other updates or other actions that you want to start from there um i'll briefly touch on different user personas that are involved in this so we have ah there's a question so brian asks us are declarative actions basically like ui actions in high level principle yes um i think you can also connect an existing ui action to a declarative action but declarative actions can do more things so they can for example also um interact with other components on your on your uh configurable workspace so using next experience and ui builder you can open modals for example or do other other fun stuff in your ui builder page so user personas we generally think of four personas who can be involved in processes and those can absolutely overlap so for example the citizen developer or the process owner can be the same person we can also have the citizen developer be an i.t developer or servicenow developer so don't think of these personas as rigid structures just those are the general rules involved in processes developers will use flow designer to create reusable activities to service building blocks within a process so they will be focused on the different activities and the actions that are happening the process owner will use process automation designer to create processes and to organize multiple activities into a cross-enterprise workflow they're interested in the outcomes then we'll have the workspace admins or page authors they will use ui builder to work on workspaces and custom pages but also create custom activity uis for your activities which is a new feature in san diego they can embed the playbook experience into their workspaces so they're focused on the experience level and then lastly the person who will at the end use the process so the agents who will work it they will be focused to uh working it in a workspace they will interact with activities on the playbook and complete the individual tasks within the process to bring the process to a close small history of auto process automation designer we have introduced process automation designer already four releases ago so it's been a full two years which is insane thinking of it i've been involved in creating content for process automation since the first release so i've been creating creatorcon labs for process automation designer since since the paris release and seeing the pro the the product grow and become more and more usable and user friendly is really a great uh journey to to be a witness off and i i really hope you give it a chance and start using it for your processes at first process automation designer was mostly um a very simple ui you could create your first own custom activities and some conditional activities in quebec we added some forum and ui improvements and adding actions at stage and playbook level in the roma release we inherited enhanced the ui again so that you didn't always have to open the jelly interface but have the option to configure your activities in the design space actually and then san diego brought a bunch of cool ad additions that is conditional lanes starting with delay and also integrating process automation designer into aes and with that one very important security feature we added delegated development options so you can decide to give a process owner permission to create processes and edit a process within their own proc scope so this supports delegated development for a specific application scope and i think that's a very good very important addition if you want to involve citizen developers so before we head into into things i have two more slides i think one is some additional info and the second will be outlining some differentiation when would you use flow designer over process automation designer and the first and most important thing is process automation designer does not replace flow designer it leverages it so each process activity has the action plan that runs in flow designer so the added benefit is that you also get all of the debugging capabilities in flow designers so for each of the activities you will find there's if you have reporting enabled you'll have the execution plan you'll have access to the same logs logging options you can test the individual actions before before you use them it can also automate different now uh platform capabilities so anything uh we we deliver a bunch of out of the box activities like record creation um updates notifications and and things like that uh records created through the process execution can still be interacted with as if they were created by any other method and that also means you can go ahead and update your your tasks and your records in the regular form interface if you want to and if it fulfills the conditions for the process to proceed it will proceed regardless of where you updated the record so you're not forced to use the um the playbook you can and then uh we have a couple of teams who have already started building out of the box content that are that is available through the servicenow store and we'll have more teams adding to that um i think there's uh playbooks for for customer service there's playbooks for security incidents i think i think they're working on other other itsm or technology workflow workflows as well um i won't say too much for the for the licensing um there if you want to use pad with custom apps then you will need to have an app engine entitlement and the others have different entitlements there's a whole page on docs that will tell you what is included in it so um the last one this is probably a very uh these are very frequent questions that i get asked as well but why should we use process automation designer and i can still use my flows and business rules and everything so i wanted to give you some guidance around when to use pad over flow designer flow designer is the tool of choice to automate self-contained units of logic but always keep reusability in mind and as such i will recommend to reduce scripting where possible so if you find using similar inline scripts regularly consider you creating a spoke with reusable actions flow actions should only ever do one thing at a time so for example calculating a value getting data from a remote system or something like that subflows will then be groupings of actions for reusability so for example a specific approval when with an output making a decision or and some following actions with the decision result etc and flows will then add the trigger layer um you should use pad when you come to complex processes so anything that will span multiple departments or phases or even involve multiple persona being able to surface the process to the agents with the playbook can be a major factor since it eases the need for training and enablement to allow the agents to fully work the process end-to-end optional activities and flow data allow for ad hoc input and activities at process runtime so for example additional subtasks etc and then lastly one new feature also in san diego is order guide sequencing this is a big improvement introduced so this allows you to finally rearrange and arrange and order and and sequence your order guides so you can decide in which phases they are being fulfilled as a recap before we head out into our demo let's recap on what we learned so far so process automation designer reduces or even eliminates the need for pro developers when connecting multiple processes and services across your organization it is simple to use simple to edit and grants visibility into into how the services are connected like you never could before and that's about all i have for my presentation i hope this gave you a good insight and first introduction into um process automation designer and a little bit about playbook experience so i'm going to focus most of the pres of the demo presentation on process automation designer today but i will tease playbook just a little bit so that you can see the other side of a process when an agent or fulfiller is interacting perhaps resolving an incident so we'll do a little bit of teaser to get everyone excited for our august session oh yeah i'm particularly excited about that as well because we'll get to talk about some of the new features that are coming with tokyo lisa you mentioned how teams are starting to work on more out of the box content to further enable our low code and citizen developers um that's that's one of the things that will be coming with our august store release uh in the tokyo time frame so more to come on that can you can you bump up your font just a tiny bit to make sure we can see it maybe one more thank you sure okay so some basic navigation before we jump into uh process automation designer it's available via the platform navigation so search for process automation and you'll see here that you've got a process automation designer so i've gone ahead and pre-opened uh a couple of windows so that i can show you different things when configuring a process this is essentially the landing page where an admin will navigate to see all of the existing process definitions again with delegated development a process owner can build and manage processes within a defined application scope this is also where they'd come to work to either modify an existing process or to create a new process so what i wanted to do to get started was show the way that a new process definition is created it's very simple to get started and then i'll jump into an existing process where we can show kind of the the available options how a user would configure things etc so i'll create a new process it's going to collect a couple of basic things here so uh name my new process let's say um we're going to build a contract management application let's just call the contract management process um add a description and then you pick your scope application so that's just defaulted there um the next thing you do is define your trigger type so you can choose your own conditions record create record update record create or update or you could choose an existing trigger so if lisa had mentioned uh beware of having multiple triggers used across different flows and different processes can be done in with intention but certainly be be aware so i'm going to say [Music] record create and then we can set trigger conditions so we first choose the table so in this case i would need to create a custom application for contracts um but let's say we search for case so you know if i wanted to create something with case or if i wanted to do it off of incident um this this will essentially say anytime an incident is created this process will run and we can also add conditions so if i want to have multiple potential processes that run when an incident is created i can say i want to look for specific criteria to be met so in the case of let's say a contract i want to run this process if the um if the contract type is cloud subscription we could say we could add that condition to run and then when the the parent record is created and the uh contract type is um you know cloud subscription it would run this particular process if it's a professional services contract it would run a different process let's say so that's very similar to flow designer also right so we can also decide to have this run off of extended feel extended tables or not and some other things right yeah absolutely perfect absolutely so then that's it and my process definition will be generated and then i'll be taken into my designer canvas now this at this point i'm going to jump into an existing process this particular one is incident response so this is what a example process looks like in the canvas i'm going to open up the process properties just to talk through this a little bit this is the information that was provided when we created the process the the steps i just walked through and then you can see here that my trigger type is anytime a record is created off of the incident table and in this example we have a condition to run that says anytime the short description starts with the word playbook and a colon so it's going to look for that in the short description and then it will run this process so what we've done is we've we've authored a couple of different lanes or stages the way to add a lane to your process is to click this button up here to add a lane and then you have this lane properties side configuration panel so you provide basic information the label for it the description again a run condition so if we want to conditionally run this lane based on certain properties evaluating you can add those as well and and finally when to start whether it's after the previous lane completes when the previous lane starts or immediately when the process begins to run dependent upon your use case finally you can add start with delay this allows you to bake an intentional delay into your lane or activity running with a couple of different options whether it's i'm going to specify a specific duration to delay the start of my lane or activity relative duration or percentage duration okay so i'm going to go ahead and delete this lane since i won't be using it in my process and then we'll talk about activities so lanes or stages of the process can be thought of as similar types of work so you can see here we've got a couple of steps in our incident response process that deal with identif identification so let's collect information about who our customer is let's get some information about this particular incident let's identify what's wrong and why the customer has reached out to us today for some help another potential way to segregate activities within lanes is if work needs to transition to a different team as you progress through your process but totally up to you as far as how you group your process activities together so let's talk about activities if i want to add a process activity or a process step to this designer i click add a process activity and then i'm given this modal where you can see we have a number of out-of-the-box activities so lisa had mentioned this you know if we need to create a child task that's related to our incident if we need to present some instructions to our agents as they're working on a case or even if we want to just put a placeholder so the beautiful thing about process automation designer is it enables collaboration between development teams and low code no code users so if we have a process owner a process analyst it could be someone with embedded within a business function that that is going to help to map out a process they can come in and essentially add placeholders to each of the defined lanes in the process and these placeholders don't have any automation behind them so so if you're truly not going to touch any type of automation as you define your process you can use placeholders and then your development team can come back in and determine the appropriate pre-wired activity definition that will achieve the outcome desired in each process step some of the others include user forms so if we want to present certain fields to a user so that they can enter information about our incident or our case at a particular point in the process we can configure which fields are displayed and allow the user to update information and progress the the process and as lisa mentioned if we update information in the playbook card it will simultaneously update those properties in the incident itself and vice versa you can see that there are a couple of other a handful of other out of the box activities available such as a checklist send an email show a knowledge article etc etc and again when we when we talk in august we'll show some of the new out of the box activities that we've been working on to further enable citizen developers to quickly uh spin up processes i think one cool thing about the checklist task is i you don't actually need to have a task the checklist checklist runs on so if you don't give it a specific task for example the trigger incident it'll just spin up a placeholder task somewhere else and use the checklist on that and you can also make use of existing checklist templates so you can define which template to load so which uh which checklist people need to fill out for that specific um activity for or to be completed and it'll auto-complete once all of the check boxes are checked or the skip button is hit absolutely absolutely yeah we have an example of that in uh in our playbook so uh again plug for for coming back in august we'll run this exact uh scenario in in the playbook side of things um so a couple of other uh thoughts about kind of the collaboration between your process author your process owner and your development teams lisa had mentioned to think of flow designer and subflows as you know self-contained outcomes and also to think of reusability so the same concept is applicable in in defining activity definitions so an activity definition is essentially a wrapper for a flow or subflow or flow action and the experience properties that are passed to your playbook that presents information to your agents and fulfillers so think about how specific process activities within your organizations could be pre-configured so that your process owners can simply drop them into any process and reuse them wherever applicable so uh think of it think of an approval step so if i need to configure a specific step in my process where i seek a manager approval you can build a manager approval activity definition that's powered by a subflow and then wherever an approval is required your citizen developer can drop that into the process designer and do some basic configuration like identify which manager should be sent the approval request yeah one cool thing about this and now i will recommend to use subflows or flow actions overflows because they have inputs and outputs so the inputs and outputs of your subflow or flow action are at the same time the inputs and outputs of your activity so you don't have to configure those separately and we had a question in the q a panel just earlier um that will be covered by this so the question was flow designer has access to service catalog variables can pad have access to those also so if you create a small subflow that will look up a request items catalog catalog variables and then maps those to the subflow outputs you can make those variables available to subsequent activities or subsequent lanes yeah absolutely okay um so let me talk a little bit about interacting with activities on this designer this is a drag and drop experience so as i'm a process owner and designing my incident response process i can sequence the the the sequence of steps so these are ordered and i can configure these activities so they run sequentially in the in the identification lane of this process this is exactly how how this has been configured so the first step will be confirm contact details and then gather more information only runs after the previous activity has completed same thing with review existing incidents for the customer so very sequential but you can also configure these to run in parallel so if there are multiple activities that need to be available to your agents as they're working on a playbook you can configure them to run in parallel so let me talk about the configuration side panel for an activity um so some similar information here is what you saw with lanes a label a description um a reference to the out-of-the-box activity definition that has been used so this particular activity is using the activity user form activity definition essentially prompting the agent to collect some information it's configured to run immediately and um is off of the incident table so you can see here that we've got a pre-built um form template that we're using to present information here it's collecting contact information from our user um let me show an example of how we may be able to reference data from earlier in the process so when i collect information about my incident so something that's persisted on the incident table i'm able to walk to that information so uh you know the the incident itself or any information that i've collected earlier in the process this this little icon here allows you to do what's called dot walking so if i need to leverage information that was collected in any of the previous steps of the process i can navigate into any of those data elements and then reference them later in my process another option which is a little more advanced is leveraging flow data records so if i'm collecting arbitrary inputs as part of running my playbook meaning i'm collecting information that is not going to be persistent to my incident table it's really specific to this particular process execution i can define a data definition and then leverage that data definition to collect these inputs and then use them elsewhere in my process so if something like alternate email address or alternate phone number um is not something that i'm persisting against the incident table delivery address delivery address exactly yes great great idea um i can collect that as a as part of my custom data definition in an earlier stage of the process and then later on let's say i have to ship something using that delivery address i can dot walk and reference that flow data record um to uh to generate my shipping label based on the address that was collected okay so what i'll do next is i'll give you uh just a sneak peek at um a playbook in agent workspace so this incident response demo has interactive activities we don't really have any non-interactive activities such as you know something that does some back-end processing and progresses the process um all of these will present a screen to my agent as he or she is working on an incident so i've pre-initiated an incident in workspace and you can see here that i have a progress indicator in my left navigational panel this will outline the stages or or lanes of my process and then it will summarize the activities within each of one of those lanes so you can see here that we've got three it will uh essentially give me a sense of how much work has been done on this incident so far where in the incident resolution process are we um you know i can go back and look at information uh you know let's say i receive this assignment midway through the process and i need to get my bearings i can go back and look through what has been completed and really understand what's going on with the incident um and then each of these activity cards is powered by these activity definitions within my process so your agent will follow a sequence and so uh one of the things that i i talk with customers frequently about is you know some of the challenges that they face are bringing their help desk operations to the next level some customers will describe scenarios where agents are having to review knowledge articles that will describe the resolution process here with playbooks and process automation designer we are actually sequencing the steps that should be taken to resolve an incident rather than forcing the agent to have a knowledge article open that that describes that incident resolution process so really makes the ramp time to understand how to resolve an incident very fast and intuitive and also drives consistency in how agents respond to incidents i think we also have some some options and integrations that i believe the csm team is using using guided guided decisions so you can define guided decision trees that the agent would walk through in one of those activities and then they will be taken to a specific kb for example as a resolution to their specific case so um interacting with other other products and other capabilities from our platform will help help your your agents to resolve these things a lot faster we have one more question um does pad work with mobile ah so that is actually a use case that we're actively exploring today so um we have a couple of organizations within servicenow that are primarily mobile and so that is definitely on the near-term roadmap to enable configuration and deployment of playbooks and process within a mobile experience so that would be the playbook side of things the design space for creating the processes would still be in in desktop and play in process automation designer but then the actual playbooks that run like this one in the workspace would be available on mobile in the future absolutely yep that's correct thank you okay um a couple of other comments so um lisa you had mentioned a little bit about licensing i can expand a little bit on that and we'll provide the documentation um so everyone can install process automation designer with your now platform entitlement um the the place where licensing comes into play is which trigger which triggered uh which tables you can use to trigger your processes so an example would be um if i have itsm licensing i would be given access to create processes trigger processes off of the incident and the incident task tables for example csm has other tables that they grant access to and then app engine licensing gives you access to all of the service now standard tables in addition to all of that that i just said if you're building a custom table or extending an existing service now table you can also trigger processes off of any custom table and extended table okay um lisa do you think you recommend any other areas we should dive into if you uh if you have an order guide sequence somewhere um i'll always show that yeah i'll turn it right over to you so you can do that all right okay let me answer the last question here so um the question one question about now learning or tutorials yes there is now learning and there are two creator con sessions um i will be sharing those um through um in the in the community post and uh the presentation has a lot of resources and training in the appendix so um you can you can follow there let me share this screen now be hopefully the right one all right so what i have here is another instance and i have an order guide um already created i found that it's rather easy to create one i've had some questions around it already so one question that we had in chat was that whether let me check all right if the order guide is triggered from service portal and uses workflows do the workflows need to be converted to flows before order guide sequence and can be used and the answer is no so you can use any catalog item and watch the catalog items themselves use to fulfill your order uh the different fulfillment that is in there doesn't matter for the order guide sequencing so in your once you have activated the order guide sequencing plugin you will see a new field on your order guide interface and as long as there is no record connected you will have a new button called generate sequence if you hit that you will see a pop-up come up and it will ask you to give it a new name since i already created one i will show that in a second but the order guide has a number of order catalog items attached to them and not all of them have flows i think some of them even have workflows still connected to it so in the process engine here you'll see that this one will run a workflow and not a flow um it doesn't matter for the order guide sequence though so you don't have to migrate everything right now once you have your sequence created and it's connected let me just save this real quick it will take you to process automation designer um automatically and all of the uh items will be listed in immediate as immediately in one lane i have already modified this one sequencing process so you can get to it with this icon similar to how you could get to the workflows or flows connected to your catalog item and this will load up a process automation designer and i have already added a couple of lanes and activities and move the activities around so these are basically all of the items that are included in your order guide and then you can go ahead and just drag and drop and move them around maybe have conditional lanes add conditions this one will only run under certain conditions or not and this will also show in the service portal so once you have requested this and you can see the open requests for this i submitted this order guide just today earlier once the approval has been given you will see that the lanes that are start later in the process have not yet started so the corp vpn and the desk setup those are later in my process so the desk setup here and the corp vpn this one runs after so for example i will wait for an email account or an ad account before i set up vpnx because it doesn't make any sense otherwise and for the facilities this lane just runs after previous so it won't start until the previous lane has completed and the customer who submits this this order guide will see this reflected in their in the stages of their request that was the thing about the order guides i hope this answered your questions let me see there's another one greta says thanks so seems like it answered the question that's great we do have one more small exercise for you we would like you to vote on the topics or the capabilities that you would love to see in process automation designer i think jason can help you figure out how to comment on this in zoom yes that's right so at the top of your webinar window and zoom where you see the green bar that says you're viewing lisa's screen there's a tab called view options and if you expand that and navigate almost to the bottom there's an option to annotate what we ask is that you drop an annotation on any of the squares where you think oh this is an intriguing topic it would certainly help me in my journey to automate processes um feel free to drop an icon there and then we'll certainly uh use that feedback as we weigh our our product priorities in the future so i'll give you an example it should be somewhere so you can have a stamp or something and then you can throw uh stars over there on the topic just oh yes decision that's decision builder right that's right decision builder is awesome you can get to decisions in your flows that run the activities but we're looking at um bringing that to the forefront of the actual design space in in process automation design so right now you can do it also in flow designer um but it's just an intermediate step in between okay thank you so much thank you all very much for joining us we have about a couple of minutes left let me just show you this so i will share the slide deck on the community post uh make sure to check that um all of the docs are in here as well as a white paper that we have on now create on process automation designer and playbooks with a lot of detailed info on how the different artifacts and different things work together um there are also a bunch of videos out there already a creator toolbox session on the order guide sequencing and techno episodes um they are a little older but most of the high level stuff is still relevant we also have the knowledge training and some some i've also added some really good flow designer and decision builder labs there so make sure to check those out they're really really um helpful useful and and awesome um so for the upcoming sessions as i said in four weeks we're going to be speaking about playbook experience and we will have more detailed info on the august store release which coincides with the tokyo early access please join us for that one we're very much looking forward to seeing you there i have a small summer break before that so there's no session in two weeks and um then after the playbook experience session we will dive into everything goodness and now platform uh on the in the tokyo release so the next session after that we'll cover all kinds of uh updates and new topics and everything that's new in the tokyo release thank you everybody for joining thank you so much jason for showing us uh pad and uh looking forward to have you on this academy in four weeks as well i hope everybody has a lovely summer and i will see you again thank you so much thanks everyone take care thank you bye