[Music] so [Music] good morning good afternoon and good evening to everybody from all around the world you if you saw in the comments we have people tuning in from all over uh good morning welcome to creator toolbox uh typically you'll see you would have seen both my uh myself chuck tomasi and brad tilton's face on here but they gave me the keys to the episode this time so i'm running this solo along with our guests from prasad and kartik and today we are wrapping up our san diego content with our pa hub um the show was meant to air two weeks ago but we had to delay it a little bit but no problem we're get we're ending the season with a bang now with more um robotic process automation as a reminder if you are tuning in for the first time and don't know about um all the different san diego content that we've been putting out go ahead and go to devlink.sn san diego and you'll see all the dozens and dozens of links of blogs podcasts live streams videos that we've been doing um all targeting the san diego release for servicenow uh other than that if you are new to servicenow make sure to check out developer.servicenow.com to get started today i have joining me prasad i'll let prasad introduce himself yeah hi everyone i'm prasad velamuri i'm part of the outbound product management team for automation region automation engine is the latest offering from servicenow that includes robotic process automation and integration hub i'm very excited about this product that would help you accelerate your hyper automation journey joining with me is karthik lanka who is the senior inbound product manager a product manager uh he will demo the rpa hub today uh karthik please introduce yourself and take it away right thank you very much uh justice like change i i think i got promoted looks like i'm a principal product manager now yeah so hey hi guys uh i'm karthik lanka here i'm i'm the principal product manager i uh and i'm from the inbound team and uh my primary role within servicenow is to build the product work with the engineering team and make sure that it is it is rock solid and something that you guys should be loving uh good good ex whatever you experience from your side is something that the team has built and uh for today's presentation prasadana i have a couple of slides to show just to set the context right uh and then we'll actually dive into the demonstration of how the platform actually works right so we can just start off by sharing the screen and maybe see look at start looking into the slides sure go ahead and get your slides ready it just feeds all right oh one screen there goes fair enough right so today we'll be actually starting by understanding what what process is within servicenow itself so primarily i believe everybody knows what rpe as a technology can do for you right so it basically goes ahead and automates all the business processes that are repetitive in nature which are sop driven which are manual business processes where you do not have access to the underlying applications via an api or apis are not there in the first place itself now basically what happens is we have some software robots which are installed on machines and these robots go ahead and mimic all the human actions uh that are required to execute a particular business process now within servicenow's rpa we primarily thrive towards transforming this business process that usually the staff works on into a bot process which is on the rpa hub itself now basically a bot process is a combination of various configuration items which are related to a standard business process now primarily what we're looking at is an analogy between how a usual business process looks like and how does it translate to a bot process so just start by looking at what the sopfa process is now this is your step-by-step instructions that you that somebody needs to follow to execute a specific task on their machines now this is primarily translated in the into the rpe hub as an automation package now this is what the developers build using the rpa desktop design studio which contains the instruction set as to how a particular process is supposed to get executed now then in line we have the business applications now these are the applications that are necessary to execute a particular business or business process now for example you have ms excel you have chrome browsers and there can be a bunch of other applications which you need to work on to complete a particular process now similarly within the bot process you have business applications that are available now these business applications are also going to hold the information with which in which these automation packages are going to touch upon again similar to ms excel or maybe a chrome browser now then you have the staff that is there now these are primarily your employees who are going to work on the sop of the process and interact with the business applications and they work on very very specific machines themselves now similarly within rpa hub within a bot process you have your robots you can have one or more robots which are which work on very specific machines to execute these automation packages or these sops that are predefined as well now next in line comes in the credentials is a very important stuff that we have now these are the credentials that the staff or the employees of the company use to log into their windows machines or also interact with the business applications as well so maybe you have a business application where you need to log in with your credentials similarly within the bot process we have something called as credential sets where we define the windows app windows credentials and also define the application credentials within them as well now of course for each staff that that works in a particular organization there is a specific shift time save may be morning nine o'clock to evening six o'clock and within that particular given time they would be working on a very very specific process itself now the same information is provided within the schedules of a particular broad process where you can define as to when this process or when the robot is supposed to trigger themselves and execute the automation package on the specific machines and finally you have your work items that are there now these work items are something that the staff actually works upon and they apply the sop off of the process for example if you have an invoice data that you have with you and you have to pick up that data and put that data into a downstream application that's the sopfa process but the actual data that you have is the work item that you need to work on similarly within the bot process you have something called as work use now work queues hold information like work items which have the actual data of a process which these robots will pick up and apply the automation package on top of it and complete the execution of the complete process now with that let us quickly look at the high level architecture of how the rpe hub is stacked up let me just go to the next slide i want to point out that what kartik just shared with us was a is basically how robots are going to replace all of us uh yes well actually we used earlier we used to get a lot of questions like that are we going to get replaced by these robots i believe we are not going to get replaced totally [Laughter] this is not a skynet uh system that is not quite no it's not an ai no yeah so but basically it's it actually is going to replace a lot of work which is really really boring and mundane in nature right we don't need to apply our brains and we end up working on a lot of stuff which is not going to give us a lot of satisfaction at the end of the day that's the kind of work that robots are going to pick up and do on on your behalf and you can work on something more exciting maybe build your own robots right uh i'll just move forward with that and to understand as to what the architecture is behind uh the all the servicenow rpa application so when you look at this particular screen the architecture is primarily divided into two sections you have on the left side you have the customer environment side of things and on the right side you have the service noise change itself now let's just first look at the customer environment side of things where you have three different components that are available the first one is the unattended robot now these are the robots which can run independently without any human intervention it can go ahead and automate do your end-to-end automation of a particular process now since there is no human intervention required these kinds of robots are installed on virtual machines themselves now then you have your attended robots now there can be cases where you would need the human and the bot to work together to improve the efficiency of a particular process now since you have the users interacting with these kind of attended robots these kinds of bots are installed on user desktops themselves and finally you have the rpa desktop design studio now this is where the developers go ahead and build your auto machines or your instruction sets and then go ahead and test it locally and eventually publish it onto the service now instance now coming on to the service now instance as i said you go ahead and publish the package onto the servicenow instance this can help you to manage your source control and your rollback options as well now additionally there are other things that you need to define on the servicenow instance we are we aim towards defining a perfect bot process now within a bot process as we we were looking at the previous slide that we need to define the package information we need to define which robots are going to work on those packages what's the schedule that's going to be there and maybe if there are any queues information that we need to add on as well now finally you uh in the bottom of the diagram you can see that we have a cdn network that is there now this is going to deliver all these all the plugins that are required to build a particular automation and that's how that's the end of how the complete architecture is all about now let's just let's now go to the more interesting side of things which is the demo and that's where we are actually going to see how to build an automation how to publish an automation onto rpa hub now how to go ahead and create a process and finally we'll see how to execute the process as well now i'll just stop uh the presentation slides that we have here right now and then we can begin by creating the automation and have a very quick walkthrough of the rpa desktop design studio well perfect thanks yeah so kartik is gonna um get his demo ready but it's it's very new technology um for uh service now because even even when i was looking at what you were presenting kartik uh there's not many websockets inside servicenow's instance right now and so yeah almost all of our integrations usually rely on a rest or soap api of some sort so um just having the web sockets for the unattended robots is it's servicenow's venturing into more modern technologies that are uh that enable these kind of things yeah we had a bunch of options to play with and to explore from our side when we were doing the re-platforming and we were building the whole uh architecture from our site but uh as you said websockets is is is a cool if you want to call it it's a very uh cool and very quick way for integrations between the instance and the client side as well the back and forth communication of data is very secure and it's you can have a very quick uh channel going on between yeah it's a live channel instead of a transaction channel it is it is right uh uh if it's okay i just stopped sharing my screen because i'll start looking at the at the screen below and i don't want you guys to be ready for you ready for you all right uh let me just start uh the screenshot again just give me a second this feature just start this picture there you go all right awesome so i'll just log into my windows machine now where we have the studio open for ourselves just clean this section up all right so this is how the the design studio looks like essentially right so if you look at the design studio itself you have it's broadly broken down into three sections we'll just look at the first at the left most corner this is called the tool box now within the toolbox we provide around 1300 plus components which go ahead basically help you in building your automations these are your building blocks for your automations and they they can mimic human actions and they can do a bunch of other things of how to build an automation and then on the right most corner you have the project explorer which is primarily pertaining to this current project that we have created now in this project explorer you have something called as plugins now you can go and add more more plugins to this particular project now plug-ins primarily are your capabilities to go ahead and interact with various third-party applications as well right and then you have something called as activities now you as a best practice within uh the rpa platform is to build a very modular automation in place where you can have your reusable chunks of code which you want to use over and over again within your automation itself so this activities helps you attain that level so you have you can see that there are two activities that are here one is the main activity and the other one is the test activity so right now we are in the main activity as you can see here on top of this tab and while we are at the top of this tab let's just quickly look at what this section is called this is called the design surface and this is where you go and build your automations and how do you build your automations from the tool box you identify the right component and drag it and drop it onto your design surface to start building your automations now i'll just go and drag and drop this component called set text now the essence of this particular component is it needs to go and add text into an underlying application that's what it basically means now if you look at this particular component this is rectangular in shape and there are some ports that are jutting out from the left side and there are some ports that are jutting out from the right side as well the left side ports are called the input puts and the right side ports are called your output ports and when you look at them they're of course they do have different colors associated with them the gray color ports are called the control ports if you go and connect the gray color ports or the control ports together this will define the sequence of execution for your automation itself and then you have something called as your golden ports these are your data ports now let me just bring in the component now i have got in another component called get text now what basically happens is once this component gets executed this will capture some data within themselves and this will be available in the data output here now if i want to move the data from this component get text component to the text component dynamically i can go and connect the data ports together and this will dynamically move data from one component to the other component this is very similar to uh for those out there that have experience with unreal engine it's a very similar design where with the connections and the data um inputs and data outputs so it's it it's a it's a familiar design for some people i'm sure i'm really sure about that right uh so going further let's just quickly build an automation from our side where we want the robot to interact with a particular application it's a thick lined application that we are looking at where the robot will be interacting with this so this application that you see on the screen it has got seven text boxes couple of uh buttons are available and there's a there's a table on the right side as well now we want the robot to go ahead and interact with this and in order to interact we want the robot to first start this particular application itself so for that i'll bring in a component in called the start app now i'll go and bring this onto the design surface it gets connected now this particular startup component is expecting me to enter the file path as to where this application resides on the local machine and it will go ahead and open that application from it on itself now i'll open the file browser copy the part of the application from my site and go ahead and paste it here so we have the application open we just close this now there is a very interesting option that we have when we do a right click on every component you have bunch of options that come in but one option that you see here is called run from here so when i go and select this that particular component starts getting executed and once it gets executed in this case it's the startup it will go ahead and launch this application which is now rendering on our screen now we want the robot to start interacting with this so i would need to create a very quick template of this particular application so that the robot can interact with this now today for the demonstration purposes we are going to interact with this application on the ui layer itself and not interacting with the elements that are available behind the rope behind that particular application you have various ways of interacting but as i said we are only going to look at ui based automations for that yes sir you had something to do yeah that's actually a great distinction that you just said um just to reiterate what kartix said is what he's going to set up for the demo is the interaction with the ui layer as opposed to interacting with the actual elements inside of the of the screen and if you tuned into the live coding happy hour a week and a half ago where i attempted to build a bunch of robots that would have fixed everything is if i had just done it via element instead of just um by screen grabs and stuff like that in the end it would have been a lot more functional if i hadn't done it that way but for demo purposes we're doing it this way now that's a very good point all because we usually recommend all our developers to go and build automations on applications using the element based capabilities that we have we have windows windows connectors we have web browser connectors we have java connectors a bunch of a bunch of connectors available that's the most reliable and the most robust way of doing it but of course there are times where you're under you can't capture the elements of a particular application and you might have to rely only on ui based automation for example if you have applications which are behind citrix or maybe on a remote desktop application so in that case you can't capture the elements so you would want then you would have to rely on the action set feature to interact with those applications all right now with that i'll i'll just quickly go ahead and start working on building a very very quick template so i've just double clicked on the actions on the actual set component and i'll begin by clicking on the capture image button here now as soon as i click on that button there's a ticker on the top right corner that says press ctrl shift for selection now i'll bring up the application just give me a second let's bring up this application i'll bring up the application with with which i want the robot to interact with i'll press ctrl shift on my keyboard and you would notice that my mouse has turned into a crosshair i'll go and quickly select the region where i want the robot to interact with i do might not require the complete application to select maybe i can just select this particular region and that will show up in in the dialog box below right now i have the dialog box available here and now i would i will go ahead and create a very quick template for this now how do i do that the first thing i would do is i would go and click on the add anchor button here now what this ad anchor basically does is it identifies as soon as this application launches on the screen it gives a cue to the robot by saying hey buddy this application has launched because i can identify that code systems is available on the screen this is something that it dynamically captures this information this is not screen scraping we use computer vision technology to dynamically identify the coordinates of this particular section of the application and the automation begins from there onwards now in order to begin the automation i need to add text into this application so i'll go ahead do a right click on the anchor and i'll say set text and i'll drop this crosshair on on this box i can do that again for other text boxes as well i'll just do a set text here i'll just drop it here i'll just quickly rename this to identify individual ports i'll call it as id for this one i'll call this as global equity units so i'm just gonna call it as gpu now there's a very interesting thing that i would want to show here so i'll just close this for now i'll just drag this to the side so that it becomes visible i'll open the actions dialog box again i'll just move it to the side now you'll notice that as soon as i've dropped two set set text components there are two input ports that have been created but this happens dynamically as well so if i again do a right click here and i say set text a new set text data port gets created on the component itself i'll just do it one more time and we'll stop it there because there are seven of them we'll just stop it at four from our side just go and rename this as well i'll call this as property units i'll call this as uk right so i've gone ahead and renamed them and what i want to do here i'll just expand this for better understanding now once i've added the text into these text boxes i would want to go ahead and click on the submit button i'll go back to my anchor i'll do a right click here and bring in the click component which is going to click on the submit button here and as soon as the submit button gets clicked this data gets loaded onto the table on the right side now for me if i want to fetch the data that is available in the table i can bring in a component called get table now notice that as soon as i bring this in there is a port that gets created on the component on the right side because this is where you your data outputs are and your data will be available in this port now similarly if i want to capture an image on this particular application i can say get image and i can just drop it on a particular section here i can just resize this box from my site let me just do that just resize this i can get the property value information here just bring it up here right i'll just stop the template so basically we are going to add data into four text boxes click on the submit button and fetch some information in return as well that's what the robot is going to do now in order to enter data there are a bunch of ways you can create variables you can hard code the information as well or earlier as i said you can dynamically move information as well so for the demonstration i'll hard code into these three data quotes and i'll in in order to showcase how i can move data dynamically from dynamically from one component to the other component i'll bring in component called today which when it gets executed it will it will hold the current system date and time right so i'll just go ahead and connect these two together i'll bring this in the sequence of execution there and as soon as this gets executed the date time information is available at the data output i'll go and connect it with the data input yep we are our automation is ready we can just quickly test it from our side just run it here the application spawns on the screen and goes ahead and enters data into the application clicks on the submit button that's why the table is populated here we have the hard-coded information that we we mentioned here we have the current system date that is available and let's just quickly look at what is the information that we have and the data ports themselves so at the data port you have the option of doing a right click and say preview data and you will see that the table data is available in this particular data output and then if i want to see what image that i have captured we have the property value image available as well so well our automation is all ready for us to be published onto the rpa hub instance now for that we need to make sure that we are connected to an instance if there is a green button available here that means that the developer machine or the studio is connected to the instance itself then we i can go ahead and click on the rb hub icon now i was doing some practice before the uh before a session today so when i'm so i already went ahead and uploaded the packet from my site but in this case if it's a new package you can create a new package here or if you want to update and upload a new version to the package you can upload a new version as well so in this case this is a creator toolbox session that we are having i've created a package with that name and there's a live demo that's the comment that i've gone ahead and mentioned here i'll go ahead and publish this from my site the project is published successfully on the rpa hub instance now let's just go back to the app you have instance and see what's happening there right this is where uh this is our rpa hub instance and in the rpm instance this is the landing page where you can get to see a bunch of information from your site but let's just quickly go on to the packages section and see whether our package has been successfully uploaded or not in the package section we have the creator toolbox that's the package name and within this package you have the package version the specific version that we have created which says version o3 which has a comment says live demo with earl and prasad that's the all right it looks like you you got a mug of coffee for yourself right so yeah so there you go so that's the package version that we have here uh which we have just uploaded from our site right now let's just go and see where the robot is and do we have a robot available so we have a robot that have already connected on this windows machine it's called the carthage vdi you would notice that in the cortex vdi record you have the machine name mentioned that and this robot is currently disconnected it's not connected from the instance itself right so i'll just open the robot from my site i'll just open the settings from here just push it to one side in this box you need to mention to which instance do you need to connect to so i'll say yes that's the app you have instance name that the instance name and you have a bunch of ways for authentication you have an mtls trusted machine to machine authentication available and you have your basic authentication available as well now for this demonstration we'll be doing the basic authentication so i have a username and credentials available to interact with this i'll go and click on the connect button here now as soon as i click on the connect button you would notice that i've got the robot's name that is mentioned here and the state of the robot is also changed to available now the available state basically means that the robot is trusted the robot is connected to the servicenow instance but it is not executing any automations right now so it's free if you want to define an automation to it it can go ahead and start consuming that automation as well now we have the package with us in the creator toolbox package and the package version available i'll close this tab we have the robot also available with us now as i was saying earlier we thrive towards defining a bot process ourselves so we'll go to the bot process section and we'll go and create a new bot process for us so i'll give it a name called servicenow demo up that's the name of the bot process and i have to define what type of process is this this is an unattended process that's the automation that we have created so we want an unintended robot to execute this process and then i can go ahead and define which package is supposed to be consumed in this process i'll go and click on the package button that's the package that we created earlier and we have to define the version as well so i'll say this is the version that it would use right and i'll just go ahead and save this record now remember earlier when we were talking about the analogy between a bot process and a business process you would see that there were business applications there the credential sets there you had the staff which translates to robots you have timings or shift timings that translates to schedules a bunch of other information as well right so let's just quickly first go and define a credential set where we want where we will define the credentials with which the robot will log into a particular machine so in this case i'll call it as copics i'll give my windows username and password here but these are all very very secure way of storing information here so it's and we use a kmf framework to rotate any keys for uh your encrypted data as well so it's pretty secure from that standpoint i'll go ahead and save this record but that's the credentials that i want to log in with into this particular windows machine now once i've done that i would want to go ahead and assign a robot to this bot process now we have karthik's vdi that we had earlier so we'll just go and add cut expedia here just go into this and add so this is the stuff that we are defining for this particular what process that we have now i need to define a mapping between which robot is supposed to work on which credentials you can have more than one robots working on a particular process but you need to be very specific on what which robot is picking up which credentials so i'll set that record as well straight and of course finally we need to go and define at least the schedule at which this particular process is supposed to execute itself now this is a very very comprehensive schedule options that we have i'll just give it a name called daily shed you and you can have bunch of frequencies available uh to interact to trigger themselves you have a minutes frequency you have hourly frequency you have daily weekly and monthly i can just define call it as daily frequency i'll say go ahead and pick up the workstation time zone and start working in that particular time zone and let's save this record let's just do very quick recap of what we have done we have created a bot process from our side where we have defined the package and the package version on this particular details page we have gone ahead and defined a credential set we have defined which robot is supposed to work on the package and which credentials it is supposed to pick up and finally we have defined the schedule with respect to when this robot is supposed to get triggered right once all of that is done we need to go and publish this particular record now once this is published all the data that is available in this particular record becomes read only and that's where the web sockets and the amb channel comes into place because once this record is read only all this information gets picked up and goes to the respective robot machines itself now of course we don't need to wait for the schedule to kick in we can also go ahead and manually start this robot from our side i will go and click on the start process icon here it will enlist all the robots that are available or associated with this particular process in this case right now we have only one robot associated so i'll just go and click on start process here and let's see if the robot has started yes the robot is triggered has triggered on the windows machine from from that command awesome all right so just wait for a few seconds for it to go ahead and start the automation itself so it's downloading all the latest information that we've just created and we'll go and kickstart the automation as well all right there you go bam so the robot has gone ahead and on its own [Music] open the application entered the information that we defined in the sop or the instruction set and the automation is completed so one final information that i would want to showcase here earl that all this information gets synced back to the instance as well if you go to the process jobs section you can see what how many executions have happened this was the fresh execution that happened here there are no execution logs that is captured right now because of various reasons and it also gives you a lot of information with respect to when it started when stopped and if there are any execution logs that are available it will mention that yes the execution logs have been stored as well so that's about it from my side and i'll just stop sharing and girl over to you nice so we did um first of all great demo uh we had a bunch of questions um and comments in the chat too so if we can um backtrack some of them uh mark asked is which windows versions are supported oh very good question mark so right now windows 10 as a as a version is supported for sure okay 11 is something that that the team is working on and we are doing our testing from our site to make sure that everything is working fine on windows 11 and once that is done we will publish it in the upcoming the releases as well nice uh sam asked uh does it i i answered some of the questions in the chat but i'll make sure we say it on there too does it support grabbing web page elements by xpath and css selectors and i was saying that's one of the main ways to do those things it does it does absolutely um sam also asked is there a way for you to build a reusable um like if you have multiple robots using a similar thing or like if a web form id changes how to go about that and i i was saying in the chat that there are ways to do shared data within rpa hub and so if you have an element that you know might change in the future you could put that in the shared data and pass that over to the robots itself unless you have a different idea too yeah so uh basically what these activities that you're creating right as i was mentioning earlier this these are your modular way of building your automations you can import activities from different projects as well and there is a very interesting capability as well here suppose you you are interacting with oracle as an application right and your your objective is to go ahead and build an automation where it's basically going and logging in opening up the web browser launching the oracle apps there and logging into the web application it's a very very simple activity but it is used over and over again in multiple different projects so you can convert that particular project into a skill and upload that onto the servicenow instance which can be created across the complete organization in future for some reason as you as uh i guess mark was mentioning that hey uh something has changed maybe the xpath has changed or some thing has changed within that particular application you can go ahead download the version create update the package back update the automation from your site and upload it back on to the skills that are there on this service for instance now because now your other developers can now fetch the latest updated skill and start consuming within their organization so the skill technically and physically resides on the instance you can just go and call that skill from the instance and use that within your automation uh sam if you're still watching that is a much better answer than what i had in chat the skills option allows for those repeated actions uh vishu asked um is it mandatory to join the flow to the nbox and no it's not it's not but it's a good practice machine so um in service now uh in an older um uh workflow designer uh the end box um made sure that all the branches for of the rest of the flow um ended and didn't continue on is that the similar situation for the design studio not compulsory issues so uh not compulsory so basic it's basically something that is a good practice that you would want to end it at a particular uh in so if you if you look at the design studio right wherever i'm actually going and building that automation it's an activity now if i'm not connecting it to the end the component it becomes very sometimes if that particular activity is supposed to call another activity it it slightly becomes difficult to transfer that information it's better to connect it to the end box uh and so that the flow is easier as well right so and then and it's not primarily that everything comes and connects to the inbox you have other ways of terminating a particular activity or an automation this is why i love having subject matter experts on the show because you know all these details that i would never have been able to answer uh i think the one of the last questions we got was from alan he said alan asks is there support for uh load balancing for heavy usage on a new bot or like if if there's a lot of processes running can nubot spin up um accordingly oh that's the elasticity that we are talking about uh alan right now it's in the road map for sure that uh in the future releases we are going to create a rover pool and based on uh the workload that is coming in uh and the average handling time of consuming a particular work item we can go ahead and bring in more robots uh that are there but as of now you have a static way of going ahead and defining the bunch of robots and you can add more and more robust to a particular process to scale up but that's a manual process right now but well pointed out it is in the roadmap and we we are working towards it also in the chat um uh gian uh pointed out that uh connecting to the end it also helps anybody else read the the design much easier yeah of course uh reading of designs is very important because like like we know with every software there are there are a lot of change requests that happens in a particular code that let's just call it code right so in this case in the automation package you would need uh continuous improvements continuous changes to that automation package and with the way that the studio is set up it becomes very easy to visually understand as to what is built on within that automation and like giant was mentioning he's from my team of course yeah he's one of the product managers uh so it becomes easier to understand as to where things are getting terminated and what what's happening if you connect it uh to the one conflict yeah just to add to that um when you have put many items in the queue and you want the robots to pick those items and then executing on those items if you don't connect to the end then i think that rpa bot is essentially stuck somewhere right we don't we don't release that thread to continue with the next item so it's a good practice to make sure that the robot is ending so the robot when it becomes free it can take the next item from the queue absolutely yeah and um for those of you that haven't tuned in i did demo some of those features on the last live coding happy hour episode and we set up a work queue and had it run through multiple things too yeah i remember you had that light bulb behind you which was no one said the commander in chat so it never turned on um i think that is um most of our questions uh again that was a really good concise demo um i like that you didn't even test it between uploading the new version to the to the that's that's a that's not only the best practices but that's a very very important practice to make sure that you do your unit test and then you upload it and then see how that works a lot of developers miss that but yeah that is something that is required [Laughter] yeah there you go [Laughter] right so uh if you guys have logged in or onto the previous session you would know you would realize that there's a robot that is running on earth's system which is turning it on i apparently never turn it off i just realized um prasad kartik um especially thank you for joining us for creator toolbox today uh if you have any other announcements um you can say so now anything yeah we do so next month uh we have um several knowledge events uh two in in the us one in new york and the other one in las vegas and then we also have one in australia and one in now in the hague netherlands so karthik will be attending the one in now in australia so i'll be part of the events in new york and las vegas we have several sessions that are focused on automation engine so if anyone in the audience is planning to attend please feel free to reach out to us we're also going to uh showcase some cool demos on stage and also in the booth so i'll i'll not reveal any more details from that um so we are looking forward to meeting many of you uh during the knowledge sessions yeah make sure you go ahead cutting yeah like prasad said they're really really cool that knows you want to go and take a look at them and to find out more details about that make sure to go to knowledge.servicenow.com if you want to look at more servicenow um servicenow san diego content make sure to go to devlink.sn san diego for anything developerwise developerservicenow.com thank you everybody have a great weekend oh not weekend week have a great week have a great day have a great evening thank you kartik from joining us from india my pleasure bye everyone thank you all bye [Music] you