hello and welcome everybody um welcome to our platform academy this is our 21st session uh in this series today i am joined by jason lefevre and we'll be talking about getting started with playbook experience a couple of you have already joined us four weeks ago when we talked you through process automation designer today is an a more exciting day even because today is early access day of our new release tokyo um a couple of you may have already seen what's new in tokyo and the techno episode if you haven't yet and you want to check it out in the forum of this academy and ask us questions please join us in two weeks when we'll be going through what is new in on the now platform in the tokyo release we will cover all kinds of platform features like atf but also some more process automation designer news we'll talk about news for these two products today because we finally can and we'll cover the rest of the products in two weeks so make sure to sign up and to join us for the next platform academy so much for the first introduction we're very excited about our new release i hope you like our improvements um my name is lisa weinstein i am an outbound product manager for workflow automation i've been working with the now platform for over six years now i joined in the helsinki release so uh this is very exciting to see the alphabet almost coming to a close um and i've been with servicenow for about three and a half years so that puts me in the corner of i think it was the madrid release or even even before maybe london um i'm joined by my amazing colleague as i said jason lefevre please give a quick introduction to yourself hi everyone thanks for joining us today uh as lisa mentioned i'm jason lefevre i represent the workflow automation team within uh the the platform product management organization um i've been with servicenow for just over a year now but uh 15 years in technology and uh i love all things workflow automation so happy to be here and talk about some of the cool stuff we have going on in the playbook space oh yeah me too thank you so much for joining uh we also have my lovely colleague andrew barnes uh he's keeping our backs free so he'll be uh chatting with you answering questions if you have any questions about the products we're showing today or the features please put them in the q a channel um and share with us if you find anything would be useful for your use cases share those things in chat and we'll have to have an engaging session all right uh i still have the safe and harbor notice in here but all of our forward-looking statements are actually released today so uh we don't we don't need this much so i'll just skip over this all right um we have a rather simple agenda today where we did the introductions we'll be speaking about playbook experience uh we'll have some some teaser and info about what has been added to playbook experience in the past but also what is new in tokyo for playbook experience but also process automation designer and then we'll give a small demo before we head into the q a section and then wrap up this session some uh simple uh abbreviations that we may be using and you'll uh you may find us here uh use those it's pad for process automation designer pd sometimes for process definition pe for playbook experience and of course fd for our beloved flow designer because we're all flat wickets right um and because we all love our workflows so much we always like to remember what the basic and the fundamental idea of the now platform is and that is fred luddy who created servicenow in 2004 uh with the idea to create a digital workflow development platform for everyone and bill mcdermott is our ceo or has been our ceo for the past couple of years and he loves to emphasize that uh with a for a great experience we always need a great workflow so that is what our workflow automation products are designed to do they're there for you to be able to create engaging experiences to your uh to your agents to your end users to your customers whoever is your target audience and uh we find that to get into that we we have uh some problem statements that we want to talk through we already went through the problems that you have in your back end so the problem statement that we wanted to solve with process automation designer is that there was no one tool to cover cross enterprise uh exp across enterprise workflows and on the experience side we find that oftentimes there's a lack of visibility so the agents the customers whoever is using the now platform as an end user must click in and out of related lists to get all of the info that they need to resolve a task they don't they don't easily see where in the process or where in the workflow they currently are and they don't know what's the next step so they don't know which fields they need to fill what's uh what notes they have to fulfill what what info they need to inquire from their uh their caller and all of those things are problems that we want to solve with playbook experience so the idea is playbook experience was uh designed to give you a way to visualize but also to interact with business process workflows in real time so that there's a simple and task oriented view we also want to make sure there's a consistent response to commonly encountered situations so that when you have agents who are working a case they will be guided through the whole process the whole life cycle of the workflow they know when to gather which information they know when to send when to send out a certain emails manual or automated they know when to gather approvals and then uh with our additions in uh in san diego they can also ad hoc add other more activities to their process as it runs um we've already touched upon this before we want to make sure that you're aware that process automation designer and playbook experience are two sides of the same coin we can use playbook experience with other supporting architecture for example the i think hr lifecycle events can also be represented in playbooks but the most common use case will probably be to create a process and process automation designer and then create and surface that process in a configurable workspace with playbook experience there's uh always a one-to-one relationship we have a process definition that is represented as a playbook there's a lane and pad that will be seen as a stage in the playbook experience the playbook component and then of course each individual activity will also be shown as a card in the playbook um i think this was the point where we wanted to do our uh handoff so over to you jason please take us through the history of playbook experience and some of the new fun stuff absolutely so uh both playbook experience and process automation designer were released in the paris family release um so for the first time uh playbook was presented as a sequence of steps that agents can follow as they're working on tasks within a workspace in quebec we introduce support for presenting multiple playbooks for the same record so if there are multiple avenues or multiple sequences of steps that an agent should take to resolve a task we present multiple playbooks as needed as well as integration with ui builder so that investment in in the integration with ui builder carries forward to today where we support any features that are available with you within ui builder we can surface any of those types of configurations and experiences within a playbook component in the rome release we we provided support for record generators so rather than having to instantiate uh an incident or a task and then run your playbook you can actually create your record as you're running your playbook uh and then most recently within san diego custom activity uis this really unlocks the power of uib allowing you to really imagine beautiful experiences whether it's embedding images within your playbook cards displaying maps deep linking the sky's the limit we also introduced ad hoc or optional activities this allows your agents to dynamically insert activities within a running process from a pre-configured list of available activities now given that it's ea day we're very excited to start to talk about some of the new features we've introduced with the tokyo family release so uh for this room we always love release days it's awesome finally get to share with you yep we don't have to talk so cryptically anymore so uh for process automation designer this release was really focused on further empowering our citizen developers are no or low code personas that are not going to be doing any uh really sophisticated development what we've done in the process automation designer experience is we've exposed our experience properties for the first time what this does is it allows your citizen developers to not only take advantage of out of the box activity definitions but for the first time they can actually configure the experiences that are going to be surfaced in the playbook so this is really a great improvement again really encouraging citizen developers to jump in and take an active role in defining and maintaining enterprise processes we've also introduced a duplicate feature for process definitions so for anyone that has existing processes and wants to spin up a new one very quickly you can take an existing process duplicate it which essentially creates a copy make any necessary tweaks to that process definition and very quickly take that process to production as need be so i've spoken with customers that have um you know very ambitious goals for for spinning up new processes every quarter and so this accelerates the time to um you know bring a new process definition to production i wonder would this also work with order guide sequences because i can see catalog be a vast potential for copying and then just adjusting small things for uh for catalog items yeah yeah so um we are currently in discussions with our service catalog team uh to to size the lift and um and and plan for um supporting catalog within process automation designer so that's a future family release outcome where uh we're doing our due diligence as we speak awesome thank you sure on the playbook side um tokyo was really about driving some performance improvements so for anyone that is configuring playbooks within san diego we did take a little bit of a performance hit due to our activity ui feature um so so we did some performance tuning within the tokyo family release to um you know to drive uh you know a better administrative experience within playbook a couple of features that we introduced are auto advanced stages so this will bring a user automatically to the next available stage within the playbook without without having to manually click into it um so this is uh you know an improvement to kind of navigating through a playbook um i also like to call out that we do maintain wcag compliance whenever we introduce new playbook features so certainly accessible accessibility is always at the top of mind so we introduced auto web advanced stages and have maintained our wcag compliance while doing so and then finally we converted our data brokers to a proxy data broker so all of the playbook out of the box components will take advantage of these new proxy data brokers essentially simplifying the admin experience for configuring and embedding playbooks within configurable workspaces lisa i think we have one more slide on uh feature content so another uh happy moment for me with our tokyo release playbook experience has been on the st the app store for about a year now um but for the first time process automation designer has joined the party so with the tokyo release we have uh brought our first process automation designer store release to the fold and what we've done is released a number of out-of-the-box activity definitions for consumption so the first category is really augmenting our commonly uh encountered process activities um so so this is kind of core functionality within process automation designer to allow a couple of different flavors of approvals display approval information create child records just really giving again our citizen developer community some out of the box content so that it's really about plug and play as opposed to modifying flows modifying activity definitions for your specific use cases so this should again speed up the the time to define and uh and publish to production your new process definitions we also released a couple of spoke related um store apps as well so those short come in handy i bet absolutely you don't have to set them on up yourself do you have to do some credential setting when you set them up yes so as part of making use of the docusign and adobe sign as well as teams and slack integrations from automation engine there are documented procedures for authentication and setting up profiles and such those are those are common and required for even if you're not using these activity definitions but but the pad content essentially um brings these uh integration hub spokes into pre-built activity definitions again so so someone can simply drop these activities within a process and very quickly start collecting digital signatures and uh sending messages via a couple of of commonly used messaging platforms that sounds really really cool and very useful yeah they're sorry for interrupting you there um is there uh when i look at the approval uh definitions um those can surely be copied again copied and then adjusted if your approval or approvals are slightly different rate absolutely absolutely so they're generic in nature so that you know if in one example your agent requires his or her manager to approve to proceed within the process you can configure it to identify the the agent's manager or on the flip side of that if it's your requester your end customer or end user that that their manager has to approve something you can also dot walk to the the requesters manager in order to get the uh assignment requests or the approval requests appropriately assigned to the manager that sounds very useful um maybe before we head into the recap we have a couple of uh we have a first chat um andrew asked people if they are using process automation designer yet and if not what's stopping them uh so um the first uh the first chat sir leslie says it's mostly black due to lack of awareness that's what we're here for so we want to um help you get started um and then the use cases have been too abstract so um that is a good idea to join us so we can we can give you hopefully we can give you some ideas on how to get started with this awesome yeah and it looks like there was an additional comment here uh totally agree with your sentiments there um i think lisa and andrew and i are all on a mission to bring more exposure to this part of our platform and these features every time we have conversations there there is positive energy around getting started and trying it out um and and so it's just really taking that energy and and the positive message that we have to bring in and bringing it to scale so we're definitely working on some content that that can be consumed by the masses to get the word out absolutely all right um there's one question uh in the q a panel um andrew is currently typing uh quite an answer but i also want to put it out here uh the question is does this use flow designer on the back end or is this separate from flow designer and the answer is absolutely yes flow designer is the foundation for process automation designer any of the activities that you see they run on a flow there's a subflow flow action behind it and you can configure those create your own and then add an experience to show them uh to the end user to the agent absolutely and so uh one of the design patterns that we're encouraging uh process authors and engineering teams to consider is build reusable purpose-built flows and subflows don't necessarily build your entire process into a comprehensive flow because that will generate some additional overhead when it comes to maintaining those flows you know any any knowledge transfer to new teams that take over responsibility for those flows it'll be more difficult to understand what's going on building your process by sequencing these purpose-built flows and subflows within process automation designer not only improves kind of ease of maintenance of those processes because you're not having to pull apart a comprehensive flow you can really drag and drop reorder modify each of these discrete process steps as you need to um and as i mentioned earlier in the call enabling our citizen developers to have a more and more meaningful contribution and so that that includes building processes from the ground up but also maintaining them as businesses change yeah and that brings us to a recap of what we think uh playbook experience is is all about so the idea is for our workflows our or large cross enterprise workflows to be simple to organize to uh to make it easier to connect uh services that span your whole organization so maybe it's a process that starts in customer service and then goes through it and lands up in uh i don't know in accounting those big processes those are great examples um what one of the most common type of processes that we see here are any kinds of onboarding processes so be that a new customer a new client a new a new employee um so anytime you onboard or also off-board some person or entity it'll it it's bound to be a complex process and those are predestined to go into process automation designer process automation designer and playbooks make those processes more simple to modify you will have context aware rules for any specific requirements any of the activities that you add to the process can be conditional can be timed can start uh after another or in parallel and it will also make it much more easy to see how your services connect how your process connects the different activities go together in the phases and how those services are being rendered to the end user we have some more some more details on the different parts of process of playbook experience now i'm getting confused um the most important part for uh for playbook experience which is as the name said is the experience side of your process it's highly configurable so you can in the experience settings of your activity you can override pretty much anything you can determine how the form displays if the slas can will be shown on the card you can define a custom activity uis with ui builder you can have specific state mappings so state mappings i think are if you have different tasks and and in one of them like four is the closed state and in the other one the seven is the closed state you can map them throughout your process and make sure that they uh fit together uh you can add the decorative actions which is a kind of ui action it's buttons on the cards that take an action within your component or to the server or within the client depends on how you configure those you can switch between different layouts you can have it full or condensed you can have it in the sidebar of your uh workspace or as its own tab there are so many different options that you can uh you can add but the most important part you can also just get started so all of those options are absolutely optional and you can start with the global experience settings and just go from there so there's it's not mandatory to configure all of those things you can just use what we supply and then get started from there and then the second part to this of course is what we mentioned before playbook experience is now uh is integrated into process automation designers so this is a new tokyo feature and we will show this in our live instance in a minute uh but before you would have to um open this in it in the jelly form or go to the back end to configure uh your um experience properties we have changed this and and brought it to the forefront to process automation designers so it's now um ease more easily uh possible to configure those um those automation and those experience settings directly in the designer design space so um as you can see in my in the presentation here in the screenshot you can define which record field should be showing you can define what's shown in the footer or which form view which fields to show um but you can also jump out to the regular view and and change all of the rest um then uh i'll continue over to the custom activity uis uh jason has already given us a bunch of examples earlier uh so you can add pretty much anything that you can add in ui builder is what you can add to custom activity uis so i can add different images you can use any of the existing components and just drag and drop them i'll have a small demo of that as well there if you want to learn how to do this and get started on your own i want to recommend at this point the creatorcon labs that i created for this year's knowledge that are available on the developer side and then all learning uh they will provide you with uh with instances and you can test out how to create those custom activity uis well they're linked in the in the resources of this presentation um all right uh would you like to give us some words on the next two slides those are record generator and declarative actions yeah absolutely i mentioned this as we were talking through our road map and kind of the history of playbook experience so basically when configuring a record generator no longer do you need to instantiate your record in order to run your playbook that's how the the mode of operation is if you haven't configured a record generator for example you instantiate your incident once the incident has been created the trigger condition to run the process and surface the playbook has been met however when configuring a record generator you essentially replace the need to instantiate the incident you can actually start running your playbook before you've even created your incident complete the initial step and upon completion of that first activity within your playbook you instantiate your incident so again ease of kind of navigating through your playbook getting your agents immediately into the experience and following the sequence without having to navigate through a comprehensive maybe complex form and then the next one on declarative functions so uh we have three different types of declarative actions and we'll show this as we uh preview a playbook in our demo briefly so you have playbook actions which allow you to do things like cancel your playbook stage actions where we'll demonstrate things like optional activities and the ability to add an activity to a running process and then lisa mentioned before activity actions which are your buttons that are on your playbook activity card so those can be configured based on the business requirements and and can essentially do whatever you need whether it's mark complete skip cancel show a list render a map the sky's the limit that's right and speaking of optional activities this is a new feature in uh san diego it's still slightly hidden in the um in the configuration uh but again the creatorcon labs go through how to do this um so don't be alarmed by this just follow the instructions and you'll get there but i want to say that optional activities or ad hoc activities are insanely useful how often is it that you have a process and your agents tell you but i have to do this step just sometimes and there's just no rule that you can identify when they have to do that step most of the time we'll want to standardize processes we want to figure out what are the conditions when when are they taking certain steps but there are just some some use cases that you will never be able to really identify or really put your finger on them and to not clog the experience you can make those optional and then have the agent decide at which point of your process in which lane or even in which phase they want to use it because these can be either per line or you can make them available to the whole playbook so um they're not restricted to any given phase if you configure them to be so and that's already all that i have to uh say here and then we'll jump over and i'll hand over the controls to jason thanks lisa so um the first thing i'm going to do is jump into process automation designer what we'll do is show an example incident response process and then we'll talk about the some of the new features with tokyo ea and then we'll preview what running through the playbook for this process would look like so a couple of things as we jump into the landing page this is the first place where you see the opportunity to duplicate a process so you can see here i've got a disabled duplicate button i'll talk through how to enable it so if i select a process here i can now duplicate this process again the use case being if this incident response demo um process definition is something that i want to use maybe as a template and make some small tweaks to it and then quickly spin up a new process i can essentially copy it so we've got some default values here but you can update your label as needed provided an application scope a description and then away you go it'll duplicate your process and then take you into the designer for that duplicated process you can see here so i'm gonna back out of this one and jump into my actual incident response demo so this is an example of how a help desk may work through uh receiving an incident and then ultimately resolving it each of these process lanes groups like work together into into a logical grouping of topics and then each one thing jason can you maximize the window uh yes all right so thank you as i was saying no problem each of these activity cards here represents a process step again powered by a flow or a sub flow you can see that we have linkage out to flow designer should you need to make any modifications to the underlying flow or subflow with our tokyo release we have reworked our configuration side panel to not only expose the automation inputs and configuration for the flow or subflow that's powering this these activities we also added the experience tab here again allowing your low code user to meaningfully contribute to the configuration of not only your process and in terms of defining the steps but also the uh the end user experience as they work through a playbook so there's another opportunity here for duplicating when i'm actually within a process definition this overflow menu here will include the duplicate action so you can invoke it from either within the process definition like we're seeing right now or the home page like i previously demoed okay so what i'm going to do next is jump into playbook experience if you give me one second i will open playbook experience preview and then we'll set up a preview here so that we can run through a playbook so we're going to look at incident because that is the the process that we just showed in the in the pad designer we're going to take advantage of the record generator and we're using our default global playbook experience so you can see here i'll show you the different layouts that we support today so currently this shows the stacked layout so within a configurable workspace your agent will see this left navigational panel that summarizes the stages and account of the activities within each of those stages and the main activity viewer shows all of the activities within the current stage stacked on top of one another we offer another layout called focused and what this will do as you can see it will list out the names of each of the activities within the current stage but then only show the current in progress activity ui one at a time so focus is the agent in on the current activity a lot helpful if you consider activities that may be more complex than just filling out two fields so if there are more more fields or even a map or something that you want to show this view seems to be the choice absolutely couldn't have said it better lisa we also have the opportunity to view this in compact mode so this will essentially allow you to display this in the contextual sidebar in the event that you want to use the majority of your workspace real estate to display other information to your agents so is this the default or can you also use the non-compact mode in the sidebar um you can't this is the default okay yeah okay so one of the things that we mentioned before was uh playbook actions we've got a declarative action here so once we've completed this first step we'll click continue and it will take us to the next activity within this stage we now have an incident number we do now have a record we do absolutely so um now you can also see that we have some playbook stage actions we talked about declarative actions being the buttons that appear on your activity uis uh this is where you can for example add an activity we went through the uh the overview of optional activities and this is how it can be added to a running process so in stacked mode we have these insertion points within our activity viewer when selecting the place to insert your activity any pre-configured activities that are available for this playbook will be presented so in the event that i needed to escalate this incident for whatever reason i choose the insertion point select the activity and then you can see here it's dynamically adding this step to my process my playbook as i'm running it so lisa you had mentioned that maybe a playbook isn't needed uh um a particular activity is not needed for every execution of a playbook escalate is probably one of those scenarios yeah so give your give your agents the flexibility to insert it wherever needed within your process so that's exactly how we configured this demo the escalate incident activity is available anywhere across the life cycle of this process and then we configured another one to email our caller that's only available in the resolve stage so as we uh complete our work and we're getting ready to close the incident we reach back out to the caller to communicate and so there's an optional activity to insert an email caller type of activity you know and presents a form to ultimately send an email so for the time for the sake of time i'm going to pause the the playbook run through right there but you can see here essentially what we're doing is taking the sequence of steps that an agent should follow to complete an incident and we're breaking it up into discrete steps so a little bit at a time presenting uh uis that are process aware so what information is required at this point in my process and presenting a ui to the end user so they can complete the task at hand um with that i'll turn it over to you lisa so that you can talk about uh playbooks in ui builder yes um so just uh for context this instance is uh on san diego still but it houses the process that i added to my creatorcon lab so for the ones who did that might feel familiar um the reason i did this is because i already have a a custom activity ui created for my flow uh this is an expense approval uh process so there's an approval stage and then uh the expense request will be fulfilled and in in one of the steps we want to get a shipping address address from the person the requester and uh generally um this looks rather simple this would be a record um so this uh this icon here uh will show that it is let me see activity definition get shipping address i'd have to go check what this looks like so i go this is san diego as i said i cannot see the experience settings back there but what i can tell you is that this activity experience is of the type record so as a basis it will use the record activity ui however if we uh scroll far enough down or just switch the tab again we will see that in the activity definition there's a tab that is called playbook activity overrides and this is the place where you would hit click new to create a new entry and then once you have this new entry you can go ahead and configure that in ui builder so this override overrides will the name says it overwrite the default behavior and you can give it a different different look the experience type is still record so we want to make sure this only applies to the parent table that is the expense request we can give it um different conditions we can just determine it only shows for certain activity states uh certain associated tables or certain activity definitions so it's not just going walk uh working for all of the record activities but only for this specific activity definition and then we can decide what we want to override in this case we want to overwrite the activity ui of the shipping address activity that being said there's a button it takes me to ui builder and in ui builder i can do all kinds of ui builder things and let me check chat while this loads um the wonderful thing about this is that in this page in ui builder we have a page that is called custom activity ui and it'll house all of your different configurations so if you create a new one for any of the other activities or any of your custom activities you will find all of them in here and then you can start to change them i don't know why exactly it doesn't show up anymore it showed shortly but i want to show you what it should look like i'm guessing this is because it's uh my test instance um the idea is to open this in a ui builder and then add a text container and then add a text that says this ui was configured for creator con and then you can save it and the same should be showing up here it doesn't necessarily do so but i have my styli stylized text here and it says this ui was configured for creator con that's pretty much all you need to know about custom activity uis you can drag and drop any other component if you want to you can add another one uh some kind of i don't know uh text or action bar or a badge or a button um and then you can configure those buttons you can you can save the page and the next time that you run your process where's the right window there uh you would run the process um those would show up for the shipping address um activity now i'm a little confused but i think you get the point uh the second thing i wanted to show you is where to define uh the optional activity and that is in a table for now we're working on exposing that in-process automation designer that will come in uh in an upcoming release uh what i do here and it's also described in the creatorcon lab is i go to the table that is called the syspd process definition this is the um the form and list layout version of my process that i showed before it has all of the lanes and then it has the different activities listed here and i added a manual activity and that is i added the activity in process automation designer then i went to this list and changed the start rule to manual and that's all this is a either a drop down you can list edit this or you can go to the individual activity and then just change the start rule from after after previous or immediately with previous those are the ones that you see in process automation designer uh you can switch this to manual save the thing and it'll be available just as jason showed us in in the playbook preview if you want to make this activity available on all of the lanes you just remove this value save the record and you're done so i think that is all we wanted to show in the demo which is perfect timing wise let me check for more questions and share the presentation okay um retta asks how do i get to the crater con lab uh you check the uh lab um the the event uh of this uh of this um academy uh it's on the community how you signed up and uh once i have uploaded the um the recording to youtube next week you will be able to find all of the resources in the community post but also all of the com all of the resources are available in this uh slide deck so i will share the slide deck with you as well um all of the docs the academies the uh now create white paper which is really cool um and all of the videos and community uh posts and um of course all the training that is relevant to this on now learning um are all linked in here okay that's awesome more questions andrew have you learned something new today about playbook experience i i think i didn't realize quite how much you could change uh you know adding components and new fields and things to the the playbook activities is um i i heard that you could do it but he didn't i didn't see it like physically before and so i wasn't sure how much you could do and while your ui builder was not uh being helpful i understood it by looking at your creatorcon lab images and that's that's really powerful yeah you can add pretty much anything like all the components are there uh you can you can add the fun stuff you can connect it to the page uh and one thing about the playbook component as a whole is uh remember you can actually place the playbook component on any ui builder page you're not a hundred percent bound to have it be in a configurable workspace it can be any ui builder page so going forward when we look at into the future i can see um guides for callers for requesters maybe those get step those people those personas get stepped through a process more easily with a playbook so it's not just tied to agents but i can see that there's a lot of potential for different persona to use playbooks and process automation designer as well yeah anything to add jason uh you're you're talking directly to the areas that we're exploring right now on our roadmap um we we do have a lot of compelling use cases that involve multiple personas both internal to an organization that's kind of driving the process as well as its customers and end users um so we are definitely um seeing that come to reality and uh we will see a day where where end users customers requester personas are interacting with playbooks that's awesome that's brilliant that's what we want to hear right we want to see this product grow and be adopted and i really hope this session helped all of you gain more insight i would love for you all to also check out the recording of the first session if you have missed it check out all the training um that is on uh on now learning uh learn everything that you can about process automation designer and playbooks and figure find out how you can use it to make the lives of your process users a lot easier and process owners as well so with that i will close out the uh the poll um [Music] do a small outlook um as i said the next session in two weeks uh we'll be covering uh what's new in tokyo for the now platform um for more topics on our uh on my agenda on my topic backlog cover among other things um some news about atf we have a new feature in atf that is called club runner and ai driven test creation i think those are very exciting topics for customers looking to adopt atf making the onboarding and getting started with itf tests much easier will likely also have a session covering admin center and upgrade plans those are the the the topics that are currently planned for the coming uh sessions i'd love to see you back um thank you everybody for joining um this was a very interesting session i think i hope you will start using process automation designer and playbooks and if you do and when you do feel free to reach out to me or to jason we'd love to hear your feedback and your use cases and how you're adopting it and how you're making lives easier thank you so much thank you jason for joining me thank you andrew for joining us have a wonderful day bye-bye thanks for having me take care everyone