[Music] thank you [Music] foreign [Music] hold on a second I changed I hope there is no Echo so I was just saying that welcome to create a toolbox a show brought to you by servicenow developer program where we demo new features for our developers and as you can see on the right side of your screen I think Daniel you can point it out to the Vancouver logo we are currently in the middle of the Vancouver release and go ahead and check out our content calendar at Devlin dot Essence Vancouver so before we jump into the content let's do some introduction my name is pranav bhagat and I am a senior developer advocate here at servicenow and I have close to eight years of experience in service now before joining servicenow is working with a customer and was helping them with an implementation I'm gonna pass it to Daniel I think one one one yeah that should better can you hear me now yep okay sorry perfect so hey welcome everyone um thanks for having me back on the show here and create a toolbox uh my name is Daniel I am a prince of product success manager at service now for Creator workflow topics um with a strong focus on automation engine being with the servicenow ecosystem for I think like 12 years by now something like that similarly you pronounce I started on the customer side before moving over to the Mothership 10 years ago I'm glad to be here today to talk about Vancouver awesome that's perfect Daniel so I'll just pass it to you so to show us what's new coming in rpn Vancouver I'm so excited about it so let's get into the new features all right thank you so much okay so for RPA Hub that's our Focus point for today all the RPA is the robot topics around do you know this is a still a fairly new capability in the platform been around for one and a half years something like that roughly uh which means it's kind of our third release of features and as you will see we constantly add new stuff to that this is one of the growing things of the platform where we're adding more and more things into it so as this is create a toolbox we won't bore you with a lot of slides I still have a few slides and save Harbor you know that part we should be talking only about Vancouver today but let's see what the questions are maybe you direct divert us from that and I might refer to the safe harbor if we talk about something going forward but what you'll see today what I will be presenting what I actually go to demo at least and some some of these points is all Vancouver features so with Vancouver upgrades on your environment you can get these features some Vancouver store one which is basically more or less now and some of them are when cooler store two coming out I think in November December time frame um so they might be a little later if you don't see them in your environment as of today let's say so we'll go through obviously the RPA desktop Design Studio our authoring experience for creating these automations running robots and we also have a few things in RPA Hub that's the service now backend basically operating and maintaining all your robots is that not boring you with a lot of slides so I have for each of these topics uh just one slide introducing it so you can also maybe refer to the slide deck later on and then we go right into the system and see that new with Vancouver release is out the way how we integrate flow designer with RPA desktop Design Studio you know hopefully or you probably know that in the past already you could invoke subflows from RPA desktop design studio uh by a simple component however finding the flow or mapping the input Fields was a bit more tedious and we have gladly improved that we have also added invoke flow I think that is a part that was not there before so we can now call any entity activity in flow designer from flows subflows and actions and while we talk about it let's go in and do that right now so I already have desktop Design Studio opened let's open a new unattended automation which we'll be using for the demo today let's call that Creator rule let me if I can spell that toolbox and it is the 29th of August 2023. hey there empty project which we'll be using throughout the show today to show you and highlight some of the new features and capabilities let's just take a couple seconds to create that project here we go and I think Johnny like I'll probably add on this is something like really like this was our developers asked a lot about how we can invoke the flows up flows and action and I don't know whether you will cover the search functionality that you've just got to launched in Vancouver so that's exciting so absolutely that's exactly what I want to do in the next probably three four minutes something like that because I am very excited about that I think this is something that was missing absolutely in the past I don't yeah before before I think like we had to copy paste the ID flow ID directly that's like that was prone to mistake so now it's easier so we can search everything absolutely so let's do that right away right so we go to RPA Hub into our toolbox open up flow designer we find all the components in there very familiar like before um I'm apologize for the screen resolution here I hope you can read that um so let's drag inbox subflow onto our canvas here we go and if you remember in the past there was an input where you would type in the flow name and you would need to remember the scope dot flow name and all these things which makes it a bit tedious right Daniel like one thing like can you zoom it a bit like so that we on the component so on below I think we have a zoom in on the canvas thing so we can utilize that thank you yeah I was just like where the hell do I assume if you're working with big screens you tend to forget the Nifty parts that better yep that looks great awesome so now oops wrong button go back to design here we go so now this is and I would call it an active component it is talking to servicenow so to be able to talk to the series now we need to log into to our instance see on the bottom we are currently not connected the gray dot here is gray so let's connect to our instance which we have a Vancouver demo instance handy and you know that part first time you launch studio and you connected to an instance you obviously have to type in your credentials say hey no see I and you do it live can't type passwords here we go yes allow going in here and close the browser now we are connected we see the Green Dot and what I can do now and that's the search functionality that you mentioned runoff I can take this component click that little gear icon to configure it and we get this new dialog to search for subflow all it needs is basically three letters to start off searching and I created a subclote called update incident right you type in up something and it searches all the subflows in that case as we're wanting to execute the subflow with our upd and it's not necessarily at the beginning it's somewhere in the name so you can find each one that you want to have in my case wanted to demo update incident it's now interrogating that subflow figuring out oh we get two input Fields an incident number and a work node let's open that one and it automatically automatically creates these input ports for us to actually call that flow how convenient is that we don't need to start mapping typing stuff it's all just there for us right right so for the sake of a quick demo just enter some values that I know exist and you'll have a look at that an internet number on that instance we are connected let's say hello from creator toolbox that's my subflow and I can just go like this and execute it now it takes you see less than a second and if I go to my instance which I have handy here um I would go to incidents incidents open we used incident call 9005 which should be this one and you can see here in the work notes we have our comment hello from Creator toolbox there we go that's very easy to call and invoke a flow or subflow or an action that is in flow designer I think that's perfect Daniel I think like I have one question for you like I see that it posted with your name like Dan and Grace so is it something the like from the from the user that we use to connect our desktop design studio so it will post from that particular user so is it a functionality can be posted using a system user or something like that if you don't want to post it from a specific user so correct you have seen me locking in desktop Design Studio that's why studio is using this connection as my user that's why you see mine I pumping up here as as the one who did the update as soon as you put that robot into a let's say live environment that robot would be executed by an unattended robot engine and it would use credentials that that user is using when logging into to the instance right so typically yes that is a technical user I generally use a user code like rpa.robot or something like that and yes that user needs to have privileges to update that incident in that case right my user has admin so it can do anything but if you want to update let's say a purchase requisition on a work order item a HR case whatever it is you need to make sure that this user you're using has privileges to update that because we trigger that flow in the context of that user correct yeah gotcha yeah thanks Daniel for that you're welcome thanks for asking so that's very easy to call a flow execute a flow and just to complete that what was there before already is like get outputs as another component right we can retrieve outputs from that flow and let's just put that on the back of this when we call that flow again we do get outputs and let's get the context ID in now the flow will take a couple seconds to run right for the sake of this simple demo I just do a party of like 10 seconds if so there's no time to update whatever it has to do in the flow and run that get outputs let's just run that one more time same content it's now 10 seconds wait here before it executes get outputs what I want to show here though is as soon as that finishes that we also get return information from servicenow and I'll go on to my return thing and say preview the data that we received in that case we get back an incident status that's just what I put into my flow you can return any kind of information from servicenow that you need so you can use this technology to look up records update records whatever you need trigger Integrations via rest or whatever right and can use that pattern to do that while you do that just keep in mind flows will be executed asynchronously so you need to either like I did put in a pause in here for a couple of seconds or you need to kind of use get execution status and loop around and wait for the flow to actually execute yeah I think this is this is one of the highlights of vanco release like you can invoke all these flows and all so according to me I really love this feature yeah it opens so much possibilities that you can do with your RPA right yes and this is just the first feature that we talked about so that's the first time most important one for me as well absolutely yes not a great feature and one that has been asked for is what we call code quality checks when you build your robots we can now add what we call Quality checks basically if you're familiar with the service now site where we have instance scan to scan for bad practices within the instance we have now a similar thing on the robot side where we can check your robot before you actually deploy it if you did obey to your own rules right and let me show you a quick demo of that as well as I go back to my um Studio that's maybe just finalize this robot as bad as it is it's just doing two things connect to start and end so we have at least filled properly we have now a code quality check right and you can basically run that on this activity you can run it on the whole project um you can view the rules that are there and I'll get to there in a moment so let's just run that this one it's checking and you get a new tab or pane open which says well there's nothing wrong with that this flow is good or this automation is good let's make it bad right just drop another item somewhere which is just free floating not connected anywhere if I now run my code quality check it actually tells me hey you got a warning here let me make that maybe bigger if I put that down here I like it better but we can see there's a warning unused component you've got an unused component you can actually select that I think by double click and it tells you hey this component that you have in your automation is not used why are you having it there this is defined as a warning I can still continue we have others that I actually treated as errors um and you can see all these rules either going in here you can see all the list of rules that are currently active you see like it's checking for infinite Loops um do we have a main activity or startup activity and stuff so these are five things that are active in our environment but if you actually go into service now in your environment and look for robotic process automation code quality rules that is where these rules are and we delivered 12 of them out of the box currently and you can decide yourself if they should be active or not or and and what kind of severity is is it only a warning or is it a hard error and hard error means you cannot publish this automation until you fix that problem so you can prevent something going into your productive environment with that right and there a whole bunch of different things some of them that you actually can configure like where do we have that variable naming convention okay look at that you go in here we have a regular expression which says all variables must follow this pad and say you can Define your own pattern how you want your RPA Developers to name variables as an example so we we have this list of the these 12 items at this moment in time you cannot create your own ones you you're kind of limited to these 12 that we have but we will extend them and maybe later on in one of the future releases we open it up I can't promise that for now these are the 12s you have and one more thing that I wanted to show if I am in Studio and if I want to publish this automation which has an issue as we know you know I can click publish it would package the whole thing and move it over to servicenow at that moment in time we will run the code quality checks and we'll let you know automation contains one or more errors make sure what you do is correct and these are warnings so I am allowed to continue if it's a hard error the publish button wouldn't be there I can't publish it anymore so these are really nice features we also store the information if I get out and publish it we get that package it's now published if I now go back to RPA hub which we have here and look at this new published package we can see the status of the code quality check in service now so we can also react on that and maybe raise a case a development task a defect or whatever we use for our developers once it has loaded there we go let's go into the package packages we have created toolbox that's the package we just created today obviously the package has one version right if we the status is linked to the version and you can see we have here a column called code quality result warning so there was at least one warning in that package you cannot build your deployment flows your process flows whatever you need you can build on that information going forward I like this tool this this feature tools it a lot because it I think it makes the quality of the robots that we built more robust I and I'm sure we will add more and more quality checks if you have ideas for Quality checks please put them in the chat right we can still bring that back to our teams like that might be a good idea to be added as a check anyway yeah I see Rob has a question here yep I can go through that question like so sort of was asking like does Design Studio have any pre-request for browser or Hardware like when we install it on our Windows machine does it have any pre-request like are you asking about the ram like how much is the ram required and all these things or if you are in the chat you can probably paste it but I think that's what he's asking that and so you can probably let us know like what are some of the pre-requests if you want to install it on our uh Windows firstly definitely it should be a Windows machine and uh what are the other things um yeah so we definitely need a Windows machine ideally that's a Windows desktop because that's a authoring environment for a developer you would install that not on a server on a virtual server or something in a data center it's basically the machine of the developer that you develop your automations on um in terms of browser we will get to a browser in a moment we support browsers of Edge and chrome these days I think we are not supporting Firefox at the moment uh for for RPA automations uh and certainly not Internet Explorer don't use that anymore it's really old outdated but Edge and chrome so basically all chromium based browsers should work just fine gotcha I think we can move into the next feature Daniel sure let me bring the slides back so this is a great feature code quality checks and I get some updates here also um stop stop bugging me um PDF connector oh no oh let me see I hope it doesn't reboot PDF connector so in the past we had a whole bunch of components in our toolbox to work with PDFs like convert to image get tables get page count so these were all separated components in the toolbox so if I go into RPA you would find them here into our toolbox toolbox right and I think they are all gone now if you search for PDF all you find is a PDF connector and it works like any other office connector with word or Excel or outlook for the sake right or Chrome you take this connector you drag it over to a global object which instantiates it and then you have that connector you can double click it give it a name and you get all these features on the connector so why did we do that for once we have a better collection of what is all around PDFs and the other thing is it's also performance and memory right with the PDF connector you would actually say I'm loading a PDF file and then once it's loaded I can do all these stuff convert images convert to XML get tables so we load the file only once with the components before every component you would use would load the file do the stuff close it now with this one we only loaded once and it's available for all the other options so this is really powerful or great and we also added the feature of working with password protect the PDF files and I got a little password protected file here to demo that if we look here let me see in my downloads I have here sample protected file if you see if you open that one up with Adobe acrobot it should ask us for a password just to prove the point here okay okay didn't do that a long time I guess see it's asking for a password right and if you don't have the password you can't get into that PDF file you might get these types of files so let's use that one and see how we can get into that file now from our Design Studio I'll take just the file name here I copy that from this one because it gives me the full path and everything I need put that in here as my file path and put in a password now the password is highly secure okay test in my case once we have loaded that let's say we want to get texts I know this PDF has some text in it so just run these two run from here takes a moment to load the PDF extracting the text information and if I Now preview the data coming out of that we can see like a simple PDF that is part of the PDF file that I've in there if you don't have the password I don't get that text so we support that now which is a great addition so that is like that's a great feature only thing that I would like to ask is like are these password encrypted because I'm seeing the password right now that you set in the automation so I see it's a string field as of now so is there any way to encrypt this password like what things absolutely usually you would store that password in service now you fetch it from a servicenow property and just use it in here for the sake of simple demo I just typed it indirectly but we do have if we go to the toolbox come on toolbox if you search for I think it's called decrypt decrypt string so there's strings that we can decrypt and something also with secure strings if I'm not mistaken yeah secure string encode decode so we have ways to work with encrypted um strings to use them as a password in this moment when they get into that connector it has to be decrypted because it's just yeah it needs the clear text password basically gotcha yeah thanks China awesome um coming back to our PDF connector so it can do a whole bunch of things like immediately converting into images to words and stuff all the things you had before and I think we also added like uh more convenient funds like merging and splitting files right so if you have a large PDF files you want to load it split it down into by Pages or you get a bunch of PDF files you want to merge them together into one before you process them further so I think these ones are new they were not there before or at least have been changed in the way how they work the rest should be stuff you might be familiar from our previous PDF components just now uh combined Under the Umbrella of that PDF connector all right let's move on in the same thing oops that was two things password protected official similar like with PDF I just showed we now have when you have word or Excel files when you open them also a password feature so we can use password protected office files I don't have a demo prepared for that but I think you have seen the PDF one it works the same way at opening the file we Supply the password and then we can read these files if you don't have the password we can't open them right um we can also create I believe password protected files right like an Excel if you give a file pass that doesn't exist with a password we generate a password protect the file and we can put stuff in there and I think Daniel like this is something like I think we can ask the product team if we can encrypt the password directly in the component itself because some developers or client might be using a hard-coded password directly here so either we have to ask them like oh don't put it there or put it as a code quality Checker like component yeah so so that don't use it because it will throw an error before they publish it so this might be a good enhancement absolutely I I like your thinking put that into a code quality let's check a tone password make sure you have them encrypted um and also provide the option to pass in encrypted one so the component can decrypt them on the Fly I like that yeah maybe and also like if they're passing even the string one it should be hidden or something rather than showing directly let me think is there is that on these ones yeah uh Port Properties you can mark it as sensitive data and you don't see it anymore it's still a clear text field but at least it's hidden when you open it right it's still not as fat as far as you want to have it but at least you can Market sensitive and you don't show them yeah for especially for this password thing it should be default to sensitive yeah so this is something makes sense makes absolute sense we know passwords are sensitive so we should have that as a default I'll definitely take that feedback to the team yes right moving forward some changes to the way we work with web pages with chrome and Edge one thing I wanted to show is that JS or JavaScript locator let's go back into Studio let me see we have a Google page open awesome so the way we work with browsers as you know is our Universal app connector right this one connects to any kind of application same like the PDF I just drop it over to Global objects it instantiates itself and I can start configuring it and I refresh find all screens that are out there and we find Google I want to have Google here add that screen and now I can work with that Google screen right that's we find the way we find it by title URL and stuff that's all great let's capture an element in this case just the search box for the sake of doing that come on search for that there we go now we have an element which is our text area for search you see we have different types of locators here in this case our Universal connector thought oh that field has an ID let's use the ID quite oftenly I have seen that with other web pages that it actually falls back to a CSS selector which would go like this um why in in uh in some of the blog posts I told you how to use Tag name and use the attribute so we have different ways how we identify an element on a web page right and what we have added now is let me just copy and paste the string here um a JavaScript locator so if none of the actually locators that we have works for you because your web page is maybe so strange so old style or whatever you can use that JavaScript locator and put in any arbitrary JavaScript that you want to and just return the object in this case a very simple one is document get Elements by ID which is actually the same like using the ID doesn't make a lot of difference from a purpose but I wanted to Showcase how it works so we return the element by that ID and if I now refresh it still works it still finds the object and I can do the same thing like I would do with other objects and navigate down text search and maybe say Set set set text set text on this one and that's hello from RPA if I execute this component it goes very fast if I go to Chrome you see hello from RPA is put in here so we executed that arbitrary JavaScript which is kind of hidden in our app connector here text search to find the objecting page it opens way more possibilities to find an object on a page or multiple objects and if you want to get a whole table area or something like that you have way more flexibility now to work with that kind of things here right so then like what I understand from this is like for example we use document.getelement by ID so we can fetch any ID on the on the page and we don't have to use the attributes or anything we can just write the JavaScript and get the ID right and it's kind of like I I think that's there so yeah so for for experienced JavaScript developers this is I think a powerful thing because they have the full control of how to parse the page basically so far they were dependent on the features we provided but with this one we open up the doors and they can do anything they want to yes and I think like as it's part of the selector thing so it might be a bit confusing for the developers like when I looked into it for the first time right now it's saying GS selector and the match attributes are also showing in the bottom so that was kind of confusing so maybe we can just have it as a separate column or something so that it's easier for the developers to understand like yeah whatever because if you open it back again the component and just open it and select the JavaScript you can see in the bottom it shows match attributes also so that might be confusing I'm not sure whether these work these both work together like is it like an or statement they should be working together I I think but I haven't tried it to be honest yes yeah yeah maybe I need we need to check how the engineers develop this thing yeah work together that's that's fine but I get your point it it is maybe not obvious if and how they work together yes yeah because is it an or statement or is it an and statement like we are putting the query on top like get this by this ID and it should have this particular class or is it of this type or something so maybe it's like we need to check yeah I need to craft the page basically with multiple objects to see if how these work together remember the simplest example here with Google doesn't really help me my assumption is they work as an end so because we locate object and we match the attributes that's the logic behind usually yeah gotcha and maybe like this is something really powerful feature we are putting it as like right now as part of the selector but if we have a separate component also all together where we just put a JavaScript there to find the element directly from the website rather than doing it from like this like firstly selecting the element and doing it maybe like as soon as the web pay load we run a script to get all the elements maybe that might be a powerful thing you were actually kind of taking away the fuss the next new component that we had is called execute JavaScript which executes any arbitrary code you want on a web page you can use that to return objects find things change things whatever you want to do on that website very powerful and very easy to use actually if I go back to my studio uh this one is hidden here on the com on the page itself so if I the Google page I had you see there's a whole bunch of things like close get URL and stuff and there's one called execute JavaScript way down I can execute JavaScript which would now execute that JavaScript on the Google web page so how do I know what type of JavaScript we just again click that gear icon get that box and we can actually say hey I have an input parameter I'll call it message for example and for the sake of the time and my JavaScript is just working so Dot Lock with that message so we have attribute mapping in you can also have return values and things like that okay and the message say we put in a static value hello runoffs okay that before we execute this I'm making sure we actually see the console right because it's not there so let's say more tools the developer tools this opens all the console and help and stuff we have here the console there we go if I now execute this component run from here I'll jumping over takes a moment to connect them you should see here a hello pronoff if I didn't make any mistake did I all right still running okay it takes longer than expected yeah maybe it's trying to find the Chrome object or something on the screen maybe you can just all right it failed pipe endpoint couldn't be found in the machine okay interesting let's close down Chrome and restart it maybe Chrome had an issue go back to Google um let me double check if you see the page here refresh it's green should be good okay and then we need to develop a console otherwise we don't see it more tools developer tools okay and now let's run it one more time there we go that was fast NVC hello pranav here we go so we can run any arbitrary code replace elements on the page stop manipulation anything you want to do you can actually do with that JavaScript anything that the browser lets you do I would want to say right including mapping input and output variables again really powerful something we did have for the very old Internet Explorer but not for modern browsers finally we have that as well definitely it's a very powerful feature like for RP developers it will open a lot of different possibilities when they are building their automation when they have this particular component awesome I think with that yes with that one we have kind of covered the major changes in RP desk RPA desktop Design Studio looking at time you're halfway through awesome so RPA Hub a couple of updates and changes we made in RPA hop and I for these ones I don't have too much of a demo maybe not that much developer Focus but still I wanted to show a few things import package versions so as a developer when you develop your automation you know that are quite some objects and service now are captured in update sets or in source code repos app repo however you deploy your code base from a def to attached to a production system with the user release we have managed to make RPA aware of that and have like bot processes uh packages versions and all these kind of things being captured as such changes and be Deployable through the stack which is great what was missing though is on the packages the file itself isn't there so if you look on RPA Hub wrong one this one if you look in RPA Hub this entry like to create a toolbox that would be generated would be transported the entry of a version 1001 would have been generated great but the attachment that is here on the right hand side which is actually the automation file for desktop Studio that was missing that was did not come over as part of the deployment now with Vancouver we added a new feature and I got here one package in that state to at least show you where it is so that's kind of how it looks like after deployment you get your package you get your package version and if you look at the package version there is no attachment you'll get an error message now saying hey hash code validation fail we seem to miss the package yes you are missing the package that's how we deploy but to get that attachment over we now have a simple button import attachment which would reach out to the development environment fetch that file upload it here and everything is fine again obviously in My Demo environment here it doesn't work because it's not fully configured it's just one instance uh you need to Define some connectivity where to find that files what's the source information basically when we have a convenient function just click that button input attachment and we pull it over makes the life of the release manager much much easier than before yep and now like as these desktop design files a bit like on it it's on a larger side they're like 10 MB 20 MB or something like that so I know we can't move it using the update sets as of now so like if we are migrating from Dev to test or to production so what's the format like do we need to download these files first into our machine and then upload it to the next environment or how it works not anymore before with Utah or San Diego yes you had to do that you have to manually download the file and upload the file into Target environment it was a manual stuff that might have been missed or you uploaded it to the wrong package or whatever right so that might have happened it potentially error prone but now with Vancouver you have that import attachment that would from the test or production system reach out to the dev environment get the file and upload it for you so there's no manual upload download required anymore yeah I think we got it I think I missed that during the Utah release so it came in the Utah release right uh that button is with Vancouver with Utah we started having that the records themselves were transported with San Diego even have that again you had to recreate everything manually so with Utah we created the records for you but we didn't do the attachments now we also have the attachment at least in an import feature import function that's perfect yeah I think that will make developers life and release managers life easier with this there's a specific role you can actually assign so if you don't want to have your success admins do that there's a specific RPA release manager role so you can give that to your developers if you want to so they can do this button themselves without the the risk that they do more than they should be it's tied to a separate role so we can delegate that capability gotcha thanks for another on that yeah awesome moving forward updating work item um when you're working with cues and flows and stuff to trigger your RPA which typically you do right you get a request like a password reset or whatever kind of information you get from a service catalog and you put that into RPA you create a work item and at a certain stage you want to maybe update that work item with additional information um there was that the content the the action itself did not change but it did does change how it actually reacts to status information right so in the past you could have actually changed that status for a bot that was currently running so even if that item that work item was currently in progress on a robot machine you could change that status and say I'm canceling it the robot wouldn't know a robot would still continue its work so you might think it's canceled but it's actually not it's still executing which could lead to some confusion so now we have changed out this update work item knows about status information and will prevent such thing saying hey I can't change the status right now it's currently in progress let it finish before we do next step right so there's some error checking now added into update work item which was not there before if you use that just have a look at the release notes and make sure it kind of fits your environment it is basically error checking that we added in here and some smaller things that we well they're actually not that small but things hard to demo here in the Creator toolbox um that that we change and add and improved so for once we removed the trigger mode you might remember on a bot process you could Define if that process is being triggered by an API like flow definer or if it's based on a schedule running every day at 9am things like that and we have separations like if you have a robot machine that is defined as a schedule robot it would not execute any API calls if you have an RPA and Bot defined for API it would not run any schedule so we clearly separated the two this forced you as a customer to have more machines right and these machines might be actually sitting idle if the schedule is not active that robot could have done API requests right why not it's there it's sitting it's idling so we saw that we removed the trigger mode as a field and all from all the filter conditions now you can mix and match you that the way you like it you might run into the situation that your robot is executing a schedule while your API trigger that's maybe something you need to take care now right but at least you have the opportunity which you didn't have before and it will allow you to use your robot machines more um more more how do you say that more efficiently that's what I was looking for so I think that's a good thing and in the same wins if you look at the middle column robot cooling if you have multiple processes um at this point it up to Utah each of these processes would probably have their own set of robots you can have more robots on one process if they need to right uh if it's a high load process that you run you could have three four five whatever number of robots in one process but what happens if that process suddenly has more load than it can cope with it would just sit in there and slowly progress job after job after job if at the same moment in time you have another set of robots idling because there's no workload it's kind of pity that we don't use them right because they're sitting there and could do work with robot pools we can do that now we can define a pool of robots independently of the process that they're executing and our other the original platform will now intelligently find out oh this process is overloaded the other one is not let's reallocate some robots to the other one and we'll shift and start to move the robots between the different processes as they are required so it makes it much easier or much better for you to again utilize your machines for the better right so they that you get the most um out of your robots a really helpful thing for large scale deployments um and I think the last one I wanted to talk about is scheduled maintenance one thing that has been asked a few times in the past we have all the information in service now about your robots which system they connect to on which machines they run on but we still kind of let's say quote unquote fail in pre-alerting that there's a change happening right if if you do if you run like a Windows upgrade on your robot machines we knew it but we didn't tell you and I think that's bad now we do on the robot calendar we show you the change requests that are linked to any of the CIS that are touched by a robot if if you're talking to an Erp system with your robot and that Erp system is going down for change for maintenance we'll mark that in the calendar and tell you hey at that time it's not a wise idea to run your robot so we see that in the calendars you see even here pop over with accepts and rechecks if you accept that we will pause the robot during that time we will not execute any jobs to wait so we kind of block out that time windows I think that's a great feature that it comes in because we have that power in the platform we know the information so we definitely should also make use of that I think that is it what I have as the major pillars major blocks for RPA in Vancouver there's probably some hidden smaller gems that I missed oh yeah I'll have to focus somewhere and get started any questions yeah I don't see any more questions in the chat but uh thank you so much Daniel for showing us all these new features in RPA personally I love personally I love the JavaScript execute as well as the flow trigger of the flow these are like game changer for developers so again big thanks to you for coming up and showing all these features and I'd like to also give a shout out to Lauren who is behind the stage and helping out with the production of this video so so thank you very much Lauren for staying up this late and helping me out so yeah Daniel like anything before before we close the show anything you would like to plug in um no I think from my side that that's I'm interested in just the comments or reach out to us by any other means that you have posted in the community um and let us know what you think about the Vancouver stuff what is grade what did you miss which ones would you which features you want to have please please reach out yep definitely and also like last thing I'll plug into we have a Content calendar at devling.slash Vancouver and you can see on the screen this is the content calendar that Lauren has created so go ahead and check out this uh calendar and yeah that's all from the show so thank you very much for for watching and I will see you for in the next episode bye bye thanks everyone bye-bye [Music] thank you [Music] foreign [Music]