hello and welcome everybody welcome to this uh 46th session of uh the platform Academy today I am just like last week joined by my colleague Jason Lefever and we will be talking about process automation designer uh which is the design interface of for all of our cross Enterprise processes we have talked about Playbook experience last week which is the user interface the user facing side of playbooks um so if you missed that session last week I encourage you to uh subscribe to the uh links and to check out the recording as soon as it's posted on YouTube next week and to give a quick introduction I think uh we'll let Jason go first hey everybody I'm Jason LEF I am part of the workflow automation product team and uh represent process automation designer Playbook experience and my larger team also represents flow designer Legacy workflow decision Builder everything cool that we have going on on the now platform relating to workflow automation awesome so thank you everybody for joining uh thank you Jason for joining me again today I'm very excited to H do another session with you um my name is awesome my name is Lisa hin I'm an outbound product manager for the now platform and I specialize in the workflow automation uh product suite and that includes process automation designer playbooks as well as flow designer and decision Builder I've been with servers now for almost five years I've been uh I worked as a solution consultant in my first year at service now and worked for a customer before that and with that I'll go through a couple of housekeeping and general uh slides before I hand it over for uh the main topic of the day uh as always uh you'll probably already know this slide um we might hint at Future uh uh future features or upcoming releases uh timelines may change uh scope of uh features may change so please don't make any purchasing decisions based on anything that we say today this is part of a bunch of more series more webinars Morey that are happening all all across the platform uh we have cies about AI about analytics uh as I said workflows platform next Experience mobile all kinds of awesome stuff and you will see um you can get this you can sign up for the other sessions as well and I'll also have a list with Links at the end of the session and I think with that I will hand it over to you Jason thanks Lisa again hey everybody uh today we're going to be talking about process automation designer this is one of the uh platform capabilities for workflow automation this is a no code Builder experience experience for sequencing automations that that uh Power your business processes so if anyone's familiar with flow designer flow designer is a low or no code experience for building automations so you can build subflows flows actions and these uh automations are reusable across any use case process automation designer is powered by flows subflows and actions so as I build process steps or what we call activities these activities have automations behind them that uh Power the outcomes that we're trying to achieve so for any business process where I have multiple steps where I may be engaging with multiple personas uh multiple departments process automation designer is the no code experience for building and empowering those business processes uh we say no code because it is friendly for any type of persona whether you are a pro developer that needs to support automated processes or if you are a process manager or a business analyst somebody that is responsible for defining redefining optimizing your business processes there are uh capabilities here that help you to quickly automate your business processes let's talk about the vision so we want to provide an experience so so that you can visualize and manage your end-to-end workflows across Business Services again I mentioned a whole bunch about how it is a no code experience that that that caters to any type of persona before we jump into what we've recently been working on as far as new features we want to raise a poll question and the question is if you're using process automation designer today how how frequently does your organization use it to automate workflows So Lisa you could launch the first poll question that looks good answers are coming in uh and we have quite a few who haven't used it before so it's great that you joined us and it's amazing that you're here so we can teach you all about process automation designer I do love the about a third of people who said we're just getting started so some of the folks have tried it already absolutely you know what Lisa I think that's going to um have us call an audible here when I go to the demo portion I'm going to highlight more than just the most recent Innovations we'll do kind of a general overview of the capabilities within the Builder so that people can get more familiar and then refer back to when they want to share this with their their team members and and respective organizations that sounds like a good idea so I will uh let this uh poll open for a little bit and while you continue and then I'll make sure to post post uh any resources and getting started links to training for those people who are new to process automation designer and playbooks so that you know where to go uh once you get out of the session perfect and Lisa that's a great mention because we recently refreshed our fundamentals and introduction courses on now learning so they have been refreshed to incorporate our Vancouver features um so uh process automation designer and Playbook experience were initially released in the Paris family release so 2019 2020 time frame it predates me um it was fun I did the first knowledge labs for for Creator con for process automation designer and it was really amazing to dive into a net new product yeah absolutely since then we've uh doubled down our investment in the capability so a lot of changes for anyone that has been with us for that Journey uh so we we've invested heavily in the product and and new capabilities and most recently um we've been uh working on features based on customer feedback based on internal Buu use cases and where our application teams want to go with with the capabilities that they offer one thing that we introduced back in San Diego was optional activities optional activities in San Diego were uh insertable in a running process so these are uh activities that I could insert via an API if I'm a user working in a Playbook let's say I'm responding to a case and there are things that I may want to add to my process sequence I would be able to invoke a Playbook or a stage action to insert optional activities in Utah we took our configuration experience of optional activities out of the list and forms experience and brought it into the pad designer so that is a pattern that we are following over the course of time as we we advance the product we're bringing the old ways of building workflow so I need to know about business rules and flows and um form views and I need to stitch them all together in a cohesive way to make a workflow we're we're changing that and we've introduced a new way to workflow and that new way involves bringing everything process or workflow workflow related into the same Builder experience um so so optional activities in Utah was one of our first um kind of convergence opportunities so optional activities can be configured directly in the pad canvas rather than in the list in forms experience and then talking about our most recent release Vancouver we introduced a completely new view of building a process in pad and that is our process diagramming feature so we'll show that in the demo I have a screenshot in a couple of slides this um allows you to view and configure your process in a diagrammatic way uh so the initial release of pad included a visual taskboard like experience so I could organize my process steps or my activities into stages and now uh you can you can do the same type of configuration but in a diagram View and then our our both of our capabilities playbooks and process automation designer we do ship enhancements via the App Store and so in our November Q4 release this year we introduced support for decisions within a process and so we'll also demo how to configure a decision within a process definition this will allow me to author um decision branches and so if I want my process when it's executing to follow a branch dynamically depending on information entered in earlier steps of the process the decision shape will actually evaluate the branching conditions and then and then follow the the branching strategy that you've configured within the process that is that is the most exciting new thing I think for decisions uh in processes I'm very excited for that feature awesome awesome Yep it's available now so if you go to the App Store uh you need to be on the Vancouver Family release but look for process automation designer version 24.2 that is the store release that contains the decision activities um and we always encourage uh customers to look at our latest family release but also now that both pad and playbooks are on the app store go to the App Store and install the latest version of the app that's that's compatible with your family release so be on Vancouver and then check out version 24.2 of pad and playbooks all right so let me go to the next slide slide we're going to show a couple of screenshots before we go into our demo so optional activities uh what you see here is the pad board view this is the initial canvas experience that we introduced for building process definitions uh you can see here I've got this uh swim Lane at the bottom of my canvas this is where you can insert your optional activities as you're designing your process we support two types of optional activities today uh Global optional activities and what this means is any activity that's considered Global can be inserted at any point in my process and then we have stage specific optional activities these are activities that can be inserted when the specified stage is in progress when I'm running my playbook the other option is that you can programmatically insert optional activities into a running Playbook via a scriptable API so if there's a scenario where um you want to dynamically insert something into your running process let's say um you have some kind of approval request the approval gets rejected and you need to go back to a previous point in your process and and complete a step again you can programmatically insert the optional activity into your process to repeat the step necessary to ultimately gain approval uh and move forward with your process and then process diagramming so for anyone that joined us at knowledge this year we showed process diagramming all over the place and so this is this is the new way to workflow so uh a con a Consolidated uh experience for sequencing and building your process automation bringing together the configuration experiences uh for anything related to process so um you know what we envision are things like uh a forms EXP experience so if I if I have a step that's going to present a form um how do I uh do that today I'd have to go to the form View and configure it and then save it and then come back into pad and reference it that's not the that's the old way to workflow the new way is that you will have a soft exit ramp into your form Builder and then um you can immediately consume that form view within your process so you're not leaving your process context in order to configure all these other things and then Stitch it back into your process it's a a Consolidated seamless uh configuration experience um so process diagramming was introduced in our first Vancouver Store app so if you are in the process of upgrading to Vancouver I just made a plug for our 24.2 um store release but this is included in our 24.1 store release and every release after that um and then decision activities you can see here in the in the screenshot that we've got a diamond shape in the middle of our first stage this is the way that we configure decisions and then route a user through specific decision branches as they execute A playbook um so we'll go into that momentarily with the demo uh I'm going to pause there before we jump into my instance and see if we have any questions that we should call up here live Lisa yeah that sounds good so uh a couple of people asked for the links that I posted uh one of the questions is can pad be integrated with project or demand management so for example decisions or actions that are associated with projects that is a great question so we um when process automation designer was initially released there was some level of control over which tables you could use to trigger your processes it was called the trigger license table table with our Utah patch 7 and our Vancouver patch one we removed the trigger license table so my favorite news this year if you have access to those to the tables that you just referenced you can trigger them you can use them to trigger processes so all you need to do is come into process automation designer um if you're on a prev Vancouver instance then you'll need to activate the pad plugin if you're on couver or later the plugin is activated by default so open process automation designer when you start to build your process definition it will ask you to specify the table and the record operation that will trigger the process so you can either Define a custom Trigger or you can uh Define one on the fly so you can uh say when a record is created when a record is updated or thirdly when a record is created or updated it will trigger this process and then you specify the table where the record will come from so uh if you have new demands or new projects Etc you can reference those tables to trigger these processes sounds awesome one thing uh one shout out I want to give is we have uh many many other teams and our different business units who also create playbooks most of them should be available through the service now store uh so if you're licensed to any of those uh products like CSM uh you might want to go check them out and then uh if you have the license for those products uh you can just go and install and uh customize those play playbooks for your uh needs uh if you want to you can also create playbooks process definitions for any of your own processes um process automation designer itself does not incur any extra license you just need to be licensed for the tables that you're working on exactly uh one thing that we'll plug right there as you made that comment Lisa we have some demo content on the App Store so there is an app called process automation experience demo and this comes with three example processes there's an incident response demo there's an application approval demo and then there's a Playbook experience demo which I think is uh on the interaction table um not only do we have the process definitions pre-built we have an example workspace so that uh when you trigger when you create any of these records you can view the running playbook in the in the demo workspace uh these aren't intended for production this is just really uh some demo content so that you can get your hands dirty and and become accustomed to how processes work how playbooks work um and how they work together so definitely encourage you to check out that store app uh as you get started awesome thank you one more really good question from the Q&A panel uh maybe you can give some recommendations on when we should use pad versus flow absolutely so Flo uh when you have something that's uh a self-contained automation I'm seeking an approval I'm sending an email I'm calling and integration um those types of things we we describe as Lego blocks so you know you might be able to uh seek an approval in multiple business processes so how can you build um you know a custom approval action or a custom subflow that that does something um and then reuse it across multiple use cases a process is like taking all of your Lego blocks and building something out of it um so I would say uh if you're thinking about um building a process that has multiple steps may involve multiple personas or multiple business departments um that's that's the use case for process automation designer if you've got a self-contained automation that's really couple of steps um then use a flow or a subflow wonderful thank you absolutely great question more questions please put them in the Q&A panel and we'll address them when we can all right at this point I'm going to jump into my instance and we will do a walkthrough of process automation designer so we're going to navigate to process automation designer uh for anyone that was with us last week or if you weren't we we dove into Playbook experience uh you do not need to have a Playbook experience uh associated with your process but we found that many people do Implement end user uh facing playbooks that that um are associated with their processes this is the UI component of a of a running process um and so anytime you have a user that needs to complete work in order to achieve a business outcome that's why you have a Playbook so that's part one this is part two to complete the picture of what powers A playbook so I'm going to go ahead and open one of our demo processes and we'll get a look at the overall Builder some of the interaction and then I'll highlight the most recent features optional activities diagramming and decisions so uh processes are organized into stages so the The Columns here represent process stages these can be delineated by similar groups of work so if you have steps for the identification stage of incident response um similar things to really figure out what the nature of the incident is um you group those steps into a stage another way that you could interpret stage delineation would be if um work changes hands into uh different teams or different departments as you progress through the the process life cycle so uh We've organized four stages into this demo process um each of these cards represents an activity uh these are process steps and behind each of these process steps is an automation so we mentioned before that flow designer powers are building blocks each of these process steps or activities is a building block you can see that this confirm contact details step is powered by a subflow if I ever want to look at the subflow I can uh go to flow designer and see what automation is powering this step um this board view offers drag and drop capabilities and so if you are really kind of sketching out your process for the first time and uh need to move move things around the board view allows you to drag and drop uh to determine the appropriate order of the steps that should take place in your process you can configure start rules so as you uh execute your process the the steps and the stages can execute in a perfect linear sequence so um you can see here that our impeccable timing I'm sorry but impeccable timing we just got a question about how to conditionally launch activities I'm sorry awesome go back to so um you the what I'm about to say about stages also applies to your activities so um we have configured this to run linearly so uh the first stage uh runs when the process starts and then each subsequent stage runs after the previous stage so you can see here that this uh logging stage starts after identification but it is possible to configure a stage to run in parallel so um if I were to change uh the the stage two properties to run when the when the process starts then that would mean stage one and two will be in progress as soon as my process uh triggers so it's possible to run things in parallel um and it is also possible for um subsequent stages or activities to wait for the complete of multiple activities um so let me just take a look at one of these um you can see here that I have the third activity in my first stage if I wanted this to um wait on both the completion of one and two and maybe I I have um these two running in parallel um I can update my start rules to refer to any of the previous activities um to kind of have these diverging and converging paths and this this will become even more apparent when I flip over to the diagramming view uh this that shows nicely when you have things running in parallel versus in a in a linear sequence uh the other thing that I want to touch on based on that question is that you can configure run conditions uh so this also applies to stages and activities I'm going to click on the Show additional options here in my configuration side panel and you can see that we've got a couple of um run condition uh options so the first is a start with DeLay So if you want to uh delay the Run of your stage or activity you can specify an explicit duration a relative duration or a percentage duration and this will delay your stage or activity from running until the point that you've specified so uh an example that I always use is let's say we've just closed a case and uh We've we've addressed uh either a new business service request for from from a customer or maybe there was an issue and a customer initiated a case for support and then you've closed it you may have as your last step a uh follow-up survey so how did we do let us know how we can improve you may want to delay sending that survey request for 24 hours like give the customer some time time to you know get back to work after their issue is resolved and then follow up within 24 hours with this survey so they have the opportunity to give you feedback you can build your delay into your activity or your stage um so that it it meets your business requirement the other thing that you have available is a run condition so if you want to specify uh conditions that need to evaluate to true in order for your stage to run um you can do that and and uh one example would be let's say I have a stage uh our application approval demo process has an approval stage and a rejection stage so the use case is I'm applying for some kind of line of credit or a credit card it's it's a financial services type of use case you may have a stage that runs through a sequence of steps when the user is approved and then you would uh essentially uh configure a run condition on the stage that looks for the approval step and the result of the approval so if my approval request is approved then run this stage if it's rejected run the rejected stage so you have the flexibility to dynamically run or skip stages and activities in your process based on what's Happening uh within the process itself uh Lisa I'm seeing some hands being raised I'm seeing some chat do we have anything you want to address uh we have a couple of questions that came in in the meantime um I answered as best as I could but maybe you have extra input uh one of them is pad looks very similar to life cycle events in hrsd are they related uh they yes and no um so we are uh we are working with the life cycle events team the plan is to eventually um Power life cycle events with process automation designers so that that is work in progress um we um life cycle events does make use of playbooks um and so for some of their end user experiences they will they will run playbooks but they are they are different technology Stacks that we are working over time to bring into one consistent uh configuration experience yes that is awesome that is pretty much also what I wrote a great question uh one person oh we we just uh talked through this uh so it was not just the question for uh conditional uh activities but also the comment that Pat is great so yay um exactly I think we talked through most of them one was a special question about a problem in the uh in a PDI uh but that might be a good chance to uh again call out if you want to try this out and you don't want to do this on your uh company instance you can get a a personal developer instance on developer. servicenow.com install the plugins for process automation designer process AO automation content Playbook experience and play around there test it out there's also training as we outlined earlier on now learning where you can get your hands on pad and playbooks awesome more questions wait more questions can we can Playbook Loop so repeat roll back to a stage uh that is coming yeah it's interesting that Lisa and I were chatting before the webinar and I said I have so much stuff that I would love to demo right now that's coming and uh so we're going to try and get back into the The Academy schedule as soon as possible uh that's coming so so stay tuned we will we will get back on that as soon as we can share it yes and then another question so pad conditions can be dynamic calls uh so yeah you can uh dynamically reference previous activities output exactly exactly so um that that Segways into the next kind of General overview uh demo topic um we ship several out of the box activities and um some of these are based on the uh like right operations to the parent record that triggered the process one of our commonly used activities is called user form this allows you to collect inputs from your user in the Playbook um you can either expose a form View and present a number of different fields that are that are in that form view or you can specify the fields one by one that you want expose in this step and what that will do is it will collect inputs those inputs will be stored against the appropriate um variables in the in the record table um so for example our first step of the process is to confirm contact details and when we run the Playbook it will ask me which channel did the did the call Reach Out by so I have to choose email or chat or walk up and um that will write back to my incident record um and then what I can do is reference that input later in the process so we have app complete support for data flow throughout the process um another way to do that um use data flow is to collect user data so this is for data that's not going to be persisted against my parent record um let's say I need to uh collect an address and so later in the process I'm going to be shipping something to that address I might expose a custom data definition that um stores that address but we're not necessarily persisting that against our record itself um so that allows you to collect arbitrary inputs and then use those inputs later in your process should you need to reference them so great question we support data flow end to end um and a number of different approaches some of our other outof the-box capabilities include instructions so if you need a user to do something maybe in another application and you haven't integrated it with your workflow uh you can present an instruction that tells the user what they need to do and then they can acknowledge that it's done um we have a number of different create record type of activities so one is an outof the-box create task we have a create record these are interactive so it will present a UI to the users so that they can specify attributes about the record or task that they are creating and then actually generate the appropriate record we also have non-interactive activities so if I want to automatically create a record without exposing a UI to the user I can do that we have automated create automated update um and then a number of other things here so if I want to send emails or show a knowledge article or uh whatever the case may be we we do have a number of different approval um steps that we ship in our process automation content app and then uh Lisa mentioned that across our applications uh service now ships several outof the-box playbooks all of those are going to contain um outof the-box activities that that were customized to the application use case all right so let me uh not wasit waste too much more time I love talking about this stuff so I could go on and on um our features that that we highlighted as as recent features so we have this switch within our board view that allows you to turn on your optional activities view this is uh the same thing that you saw in the screenshot so I have this swim lanane that opens that allows me to configure Global optional activities so I have the same picker here that I can uh insert Global optional activities and then I can add stage specific optional activities um where it's warranted so before you had to go find the process definition list on the list and forms classic UI navigation you had to add an activity to the process definition there and then you had to give it a manual start rule so it wasn't a great configuration experience this enhancement again brings uh configuration and list and forms into the the pad canvas so you can do more work related to your process in one place so that's optional activities and then uh drum roll please here is process diagramming so um this is the same process definition but in a different view so um you know if I have a process that has decisions or it's uh has multiple things running in parallel perhaps the board view is not going to uh intuitively kind of help me understand the nature of those details as much as a diagram would represent um so this really gives the process author options so you can configure a process in the board view because it's simple and you can quickly get an understanding of what the the process contains or you can do in diagram whichever whichever is more comfortable for you you can use this these views there's parity between the both of them um so you can see here that rather than having the the column orientation we've got these these larger boxes to represent our process stages and then each of these tiles within the within the stage represents our activities our process steps um so you can see that we've got um a linear sequence in my first stage in my second stage this is where I've got a decision so let me quickly talk about how decisions work um if I need to add a decision to my canvas I can add a plus here so hover within your stage and you see these pluses these are where you can add things to your process so you can either add another activity you can add a decision or you can add a parallel path uh we have a decision here and so the way that I C I configure decisions is I will first provide basic information like a label a description I can give it the appropriate start rules and then I uh Define my branches so in this uh use case we are going to treat our process execution uh differently for the different priorities that that my incident could be uh the different priorities that could be calculated for my incident um so just as an an example I've configured two different branches that represent what happens if my incident is a p one so this is a critical incident and then if I have a P2 so a high priority incident uh each of these branches has the ability to label and then you specify the um the condition and what I've done here is I have dot walked to my trigger incident priority so you can see here I'm using the dot Walker I can kind of scroll to the priority or I can actually search so if I want to search for priority it will do the dot walking for me um so I've I've pill picked to um trigger incident priority and then uh we've said that if it's critical we want to follow this path uh I did the same thing for p2s could do the same thing for all of your priorities if you want to treat each priority differently um and then one of the options that becomes available when you have at least two branches is you get a uh processing approach so by default the the decision will process the first branch that evaluates the true and when you have two or more defined branches you can process any and all branches that are evaluating to true so it really gives you some flexibility in how you can dynamically route your user and your process execution through certain steps depending on uh information collected as you progress the process and then each decision shape comes with an else so if there are scenarios where you want to route to an an else Branch because none of the uh branches evaluate to true then it will proceed uh accordingly so um I'm going to pause to take a quick drink here um let's see if we have any questions the obvious question just came in can pad use decision Builder so it can can and I'm I'm I'm not going to talk Safe Harbor quite yet let's talk about how this is done uh today so it is possible to call a decision table from flow designer and um what you can do is uh reference the decision table and then render a decision within your flow and then you can if you have a subflow built each process step can be powered by a subflow or an action you would create a subflow that leverages the the decision table and renders the decision as an output and then you can create an activity definition so an activity definition is a wrapper for your automation so your um your action or your subflow and then if your if your process step renders a UI it has the experience properties that will present that UI in a Playbook so today the configuration experience requires you to make subflow that calls the decision table and then reference that subflow in an activity definition so there's there's some additional configuration required in the future we're going to work on how to bring those two together more seamlessly so uh if I have a generic uh decision activity can I just reference a decision table directly so that that work is coming um and and for now there are just a couple of additional configuration steps to make it possible awesome thank you so much H One Note for these if you uh do have the subflow with the decision make sure to have uh your decision outputs mapped to subflow outputs because all all of the outputs that the that the subflow uh hands over to the activity definition will be available uh for activity or Lane conditions as we saw earlier so uh all of the subflow outputs will be activity outputs Y Cool all right a couple more things about diag pring so excuse me for my coughing here this morning um we have some validation rules that we put in place uh for the diagram so let me Force some errors here so we have these connectors here and if I was to delete a connector uh you can see that we've got some colors showing up and additionally we've got this arror tree at the top of our uh header here um what this does is it shows me as the the author anything that I really need to think about or fix before activating my process and a yellow warning is kind of a a soft warning it won't prevent me from activating and using my process basically for this because stage one is missing an end connector this won't stop me from activating my process but what it will do it just lets me know that um after stage one is done executing the process will stop because it doesn't know where to go next now with stage two we're missing a start rule so this stage doesn't know when to begin so this is a hard warning and it will prevent activation of my process so I need to F I need to give all of my stages at least a start rule in order to be able to use my process um so the fix here is to Simply drag a connector and you can see here that my validation tray has been cleared out let me show you a couple of cool little tricks um so if I if my process has let's say a bunch of Errors um all of my errors will be visible here in the tray and then where we um can navigate you to the configuration property you can actually click from the error tray so this what this does is it opens up the the specific property that's missing and it will allow you to fix it so I'm just going to have uh stage two start after stage one again and you can see here how the the error tray was cleared out because I've resolved the errors um if I have any um activities that are missing inputs uh that will be another thing that that throws some validation errors here um so you can see here that I've got multiple errors done and what this is looking for is just the require IR ired inputs um so when I have a user form again that is for writing values to my trigger record or any record that I specify um in my running Playbook you need to reference a table so we need to know which table are we writing values to and then within that table which record are we writing values to so you'll see some some kind of helpful hints here to make sure that as you're authoring you are completing all of the required fields in order to make use of your process something else that was introduced with diagramming undo and redo so you can see up here we've got an undo and a redo button this allows you to um track changes within your current application your browser session and then if you do something that you didn't intend to do you can undo it and then you can redo so you can see here undo redo so that's a quick that's a cool little enhancement that that assists with your uh configuration tasks and then let me show one more thing so if I want to change my start rules I showed you how you can do it in the configuration side panel you can also actually redraw your lines in some cases so if I want stage two and stage one to run um simultaneously I just redrew my my connector here and that essentially updated my start rule so that my Pro my stage two starts when my process starts so you can you can uh redraw your lines here in order to appropriately sequence your your stages and your activities excuse me um we do not yet support drag and drop in the diagram so that is a coming feature not yet available just wanted to call that out um let me pause once more and see if we have questions any questions I don't think no new ones nope all right oh that where there's one coming versioning question mark versioning okay so um we do not support versioning per se um in process automation designer today we you do have this concept of a draft process and an activated process um so if something is in draft that um you're not yet ready to activate and make use of it can stay in the draft um we also um have snapshots so every time you activate in the back end we take a new snapshot of your process um you can um track versions via Source control so so if you um use various Source control uh applications or capabilities you can track versioning within Source control um but as far as authoring workflow and inv versioning uh not just yet it is enough idea on our road map we just uh you know we have tons of things that we're excited to do with this space and so uh haven't yet got to that so much to do so little time exactly exactly all right um other questions it looks quiet all right well yeah this this was meant to be kind of a an inal process automation designer again we're going to have you walk away with our Coe links which contain um you know pointers to our learning modules pointers to any recent uh knowledge Labs that are available um Lisa does a fantastic job of uh curating content with best practices relating to not just process automation designer and playbooks but also um all topics relating to workflow automation um if you missed our Playbook experience uh Academy from last week we definitely encourage you to go review the recording as soon as Lisa makes it available um because it is the other side of a process the UI side of a process so we always split this into two parts just because there's so much content to cover um but that that is definitely encouraged as well uh let me jump back into the presentation so that we can cover our final slides before we close out for today we have another poll So based on what you've seen uh what are you most excited to use and we give you three options so you can choose optional activities diagramming and decisioning but if there's anything else because you're just learning about pad today uh as we walk through the demo feel free to put that into the chat uh if there are additional options that you want to let us know about yes please let us know what you think and we have a a very clear front runner and process diagramming and I absolutely agree it makes it uh for some processes it's really nice to work step by step go through your lanes and add the things but sometimes you just need a big picture and then uh diagramming is amazing for that absolutely absolutely um another plug for some of our outof the-box process activities I know that our uh regulated markets um our financial services industry team teams they ship some rather complex playbooks that are available via our App Store so if you're uh if you're licensed to use any of our financial services applications um there's one out there for responding to fraud cases that's a very complex process that gives you a starting point and so if you need to be compliant in a regulated market take a look at some of those out of the boox processes and playbooks to give you a starting point for responding to business critical situations um another one to call out is in our source to pay space so supplyer life cycle operations has a number of outof the-box processes and playbooks for different uh supplier life cycle scenarios on boarding uh different source to pay type of purchasing scenarios um and then the sky the limit if those are if you're use cases require different types of workflows you can use these capabilities to support whichever workflow requirements you have that sounds awesome um I threw the general link to the store uh in the chat as well so if you haven't checked that one out yet uh please go ahead and do that uh I think uh we answered most of the questions we had some really good questions today thank you so much for uh being such a lively crowd today uh some really good questions and in interest in this session uh I want to leave you with some more links uh some of these you've seen uh you'll also find the overview of all of these acmy at sn.org Academy um which will link you to a community post with all of these um I'll hope you check out all of the other great content that my colleagues put out and I think with that what I have to say for uh for today is thank you everybody for joining us thanks for an amazing platform Academy year uh 2023 we had some amazing sessions this year with uh great guest speakers um to those that I don't speak anymore I wish you happy holidays and uh and a nice quiet time this is the last session for this year um starting next year my uh wonderful colleague Tara Fisher will uh take over this platform Academy and I for myself will spin off a workflow Academy from this series so uh keep in mind as sn. workwork flow academy uh so there will be a dedicated Academy about all things workflow next year and we'll cover best practices guidance tips and tricks um and also uh some how chose um and run some AMA uh live streams where you can join us and ask us questions about workflow automation on the now platform and that is about all so uh thanks again everybody thanks for joining thank you very much thank you so much Jason for joining me uh last week and this week and uh hope to have you on my Academy next year you know I'm always in for it awesome wonderful H everybody have a wonderful day uh rest of your day have a wonderful weekend and wonderful rest of the year bye take care