[Music] oh [Music] oh hi everyone good morning good afternoon good after is there any Echo okay hi everyone good morning good afternoon good evening my name is Prana bhat and I a senior developer advocate here at service now and I bring you our latest episode of create a toolbox where we talk about new features that are coming in the current release we are in the middle of of the Washington release and as you can see on your screen now we have a full content calendar and this episode happens to be our first episode from the W release itself so I like today we're going to cover service now rpn I have Daniel oh I have Daniel dce with me to talk about what's new in RPA So Daniel why not you introduce yourself then we're going to start off all right thank you praf hello and welcome everyone good day good morning good afternoon wherever you are my name is Daniel D I am a product success manager service now for Creator workflows that's up here there um so everything you use to build applications from App engine app engine studio and all the things around automation engine doc Intel RPA and all the other fancy Tools around pleasure to be here today to talk about what we do with RPA in Washington awesome I think I'm really excited to know about some of the feature I already talked about it during Tech now but it would be great to see a demo so stage is all yours Daniel I'm GNA yeah so let's get started with it all right so Washington well was Washington is in early availability so Safe Harbor has to apply right it is not fully released yet but we are very close to it so probably everything I'm saying today will be in the product but you know things might change so don't make make any specially purchasing decisions and things like that based on my statements today with that out of the Court let's move forward and see what we have today so I'll I'll focus in this session on two blocks things we changed in the desktop design studio and things we did on the RPA Hub side of things more on the service now instance how they interact together we have a a lot of new features a lot of great new stuff um I picked out my favorites there's a few more well may to my extent to my feeling to my um rating lesser important but they are still there so please check out the release notes you might find more other gems that are interesting for you these are just my personal favorites out of the RPA release in Washington and I have prepared a couple of demos for the different things so to make that interactive please also use the chat speak up post your questions and we will try to address them as we go forward so let's start um the first one I have here on the list RPA desktop Design Studio our authoring environment for automation flows that you use to build these fancy robots helping you to do the mundane work a tiny change but I think it's an important change is actually our Connection Manager when you log into the service now instance uh you know most of you that have used it before probably have seen that the login screen didn't really render nice in our Connection Manager you always had to use the external browser like Chrome or Edge or whatever you are using to actually log in we finally fixed that the login in The Connection Manager works just fine and I'll see that in a minute when we log in so so much simpler no more external browser that need to open up I think I think I I think Daniel I love this one because I remember like whenever we had to log in we have to select like launch in a default browser otherwise it opens in an Internet Explorer so that's that will be handy like it won't cause like interruptions for RP defs so absolutely that that works for desktop it works for the attended robot for the unattended robot so we fixed it for all of them finally yay that that was good was long du I would say and we will see that in a minute as I go into the demo so I don't do a demo specifically of that but you will see it in just second one I have in here is follows a complicated name Shadow dumb support and I know that's a technical term that maybe not everybody understands what it is on a nutshell is there are websites out that use a technology called Shadow D and our technology was not able to query that website and find elements and actually use controls on that and most primary example for us is service now ourselves we use Shadow do so you could not build an robot automating against RP service now instance um I had actually a customer I do have a customer that wants to use RPA to talk to a customers instance of them because they are not allowed to use some kind of integration technology which typically we do that's a very very let's say critical sensible customer not saying where they're working in but very sensible and they had to use RPA and they couldn't do it against so there no instance we washingt this is fixed and I give you a demo on that in just a moment that's great we finally support that the third third one and then I'll move into a demo and show you all three of them so Daniel like sorry to interrupt you like I'll go back to the shadow Dom thing like so like our audience is service not Developers so they might not be familiar with the shadow D or something so maybe like if you can give a one liner or two liner what it is and that would help them yes sure absolutely thank fov so a a the Dom is the do document object model which is used in browsers to render web page so that dum consists of all the text Fields the labels the images everything is part of that D in the browser and we use a technique when we when you install a plugin in in Chrome or an edge um that goes crawls basically through the Dum and adds little tags to it and saying hey this is service now we want to be able to work with that element and Shadow Dum is kind of a hidden dumb so you don't see it necessarily in the browser and our plug plugin was not able to read that content that's underneath the shadow Dom so all we would see as service now as as our RPA technology was a black box and what's in that black box we had no idea now we are able to crawl into that shadow D and see all the elements underneath that's why the screenshot is there for service now screen where you see that drop down box being highlighted and it's actually it's a Tex select we know what it is we can actually work with that awesome y all right third one and then I'll move in a quick demo and show basically all three of them is set password um when you work with RPA and you interact with other let's say backend applications you might need to orchestrate against an EOP system a financial system whatever have you usually your robot needs to log in to that environment um we we we have't will come to credentials in a moment as well we we always have the possibility to store credentials in the service our world in an encrypted and safe manner but at the time the robot was executing we needed the password decrypted it had to be clear text so we can actually tell the robot type that into that password field this is kind of sensible information we don't want to have that password be invisible if we don't need to right so when now we have a new component set password which is allowed which will allow us to use the encrypted or secure string as we call it in the desktop to be passed onto a password field and I'll show you that as well how that works with that let's move into the first part of a bit of an interactive demo let me get my uh back to my desktop so quickly close that we'll start r a design studio so that hasn't changed you've seen that before and the first change you will see now is as it comes up with the login box The Connection Manager we don't need the external browser yay second to pop up here loading components obviously when you install that the first time on a Vash Washington instance make sure you get all the updates it will take a m a few moments to load and get all the download and everything so make sure you get the latest and greatest version and update your windows environment here we go with a new beautiful rendering of the service now login screen here no and if if I would go back actually to the instance you can see I don't use that launch in default browser anymore just say Markus default and that's it now let's log in Connect now that's the first very nice and change that will make life a lot easier logging in and here we get the new studio it looks the same the big change is the version number down here right you get 7.0 which now the Washington notation with a bundle of 8.0 But Here we are now let's say we make a new unattended automation Lo [Music] in Lo into service now I one you show you quickly the shadow Dom capabilities and the secure password piece right so I do have this one open so let's just look out for a moment this is on my service now instance right and already this page is using what is called a shadow Dum right in previous Washington our capture features would not be able to do anything in here right now I can actually just go to Global objects and you see another tiny change we can actually add add connectors from here I don't need to drag and drop them they're just here in a nice list where do we have the universal app add connectors and it's there I don't need to find it somewhere in the toolbox it's just one of these tiny things that I didn't mention isly in the slide deck yeah I think these chiny things add lot of value for RP developers like quality of live improvements we should call them and they're really helpful yeah so let's grab our login page add that to the screen and now I start capture elements on that page and immediately you can spot it actually highlights elements on that screen before it would be just one big red box and you couldn't select anything right now I can so if I go here for example to username and another nice thing I didn't actually mention you can see the name is prepopulated now it's not just an empty field and you have to name it actually it's intelligent and figure out what the label is and takes that over not a really helpful thing right so let's just capture these three elements going back you can see we have them now in here all of them username password not important that's a login box it's not important okay maybe that's a name we should change but other than that it captures name all is there it's just fine now the thing I can do here is let's say username behaves like before right we can just say set text come on put my name in here if I want to do that and if I go to the password field it actually does have a new feature called said password which I can concatenate and this one accepts now a secure string which means it's an encoded value at this point I don't have that I'll come to that back to that later when we talk about credentials in RPA this one will now accept the secure string um which I cannot just type in here so be secure it has to be encoded beforehand and I can pass it in to populated value and this will just work if I I could run that from here you will actually see it just takes a moment to execute just like before couple seconds and then we should at least have the username there this one obviously fails because we don't have a password but if we get here the username is populated means our shadow don't Feature work we were able to get in we were able to interrogate the page and this that that's fantastic yeah I think this is this is a game Cher for building all these RP automations because lot of websites support Shadow capabilities and all so this this is something a really great Improvement awesome so let's go back to the presentation just we have been in set password full screen another nice thing we have added is what we consider a graceful stop now when you have a robot that executes something ideally in a loop right you're processing a lot of Records maybe you are uh looping through an Excel sheet with hundreds of rows and doing something for each and every row up to now now there was a two options you had either wait till it's done or you forcefully quit it and just kill the whole process which kind of leaves you in a state you don't know how far it went and didn't do kind of a cleanup thing or something like that right it was really just a forceful kill now you have the option to do a what we call a graceful stop within service now when you want to stop a process which means basically service now will tell the robot hey next time you can please stop it's kind of kind ask it's not a forceful quit and the way this works is in your automation we have a component called graceful stop which will give you a a a Boolean value back am I supposed to stop yes or no so as you design your automation you can put that component on any place where it would make sense to stop coming back to the looping example maybe after every row of action you come back am I good to continue or is there maybe something else I should be doing right so you can gracefully stop freeing up the robot to do other work for example so things like that is now possible and said the way it works you put these graceful stop components into your automation at the places where you say this is a good time to actually stop if this component is not there the graceful stop from service now will not work this one will say well sorry there is no graceful stop we can't gracefully exit we have to forcefully quit it so we know that a graceful stop is used and we provide that option if it's not used it's not there you can't do it it's it's more about like we can logically quit the like our automation so that uh we don't get data in inconsistencies and inefficiencies in the back end so corre that's a nice that's your time to kind of clean up maybe move away directories folders files that you have started working on put yourself a marker how far you have come things like that right you gracefully end instead of just killing it so D this is like I'm getting curious we have a stop button in our bought process that's there so if we press on the stop button like do you think like what what happens like will it gracefully stop or it will just stop then and there if the graceful stop component is used if you click on that stop button that dialogue you see in the back will pop up saying hey Iz this is running on a given machine right I blurred that out as it's kind of burping out my my virtual robots right but it will show you this process is currently running on this and that machine it's in busy State and it gives you the option to gracefully stop if that automation has a graceful stop if it doesn't you don't get that option it just kills it gotcha perfect and that's obviously hard to show in a demo so please go around and play with that I put in at least a screenshot so you kind of refer to how it works but yeah for a demo that takes a little more of setup in having a process running for a longer time another piece we added is what we call a bot process restriction so what does that mean and let me maybe show you that in the demo piece again if we move over to studio so whenever I am developing a automation you know for testing purposes I need to assign a bot process I need to say hey please and early on we call that impersonate we kind of say do as if you would be running let's say RPA Challenge on this machine because I might not develop on the machine it's actually running right I might develop on my local desktop but running should be somewhere in the data center so I'm saying hey please do as if you would be that robot executing that process somewhere in a different machine now this works great but it poses the risk that you actually select a robot that might run for example an invoice process or an ER process that I personally should not have access to right because maybe it captures some credentials from the bot process where I can see logins coming back to the unencrypted or decrypt the passwords and things like that that I could suddenly see as an RP developer that I should not be able to see now with a restricted B process we actually limit that and if you see that for example if I want to say hey please do that shipping process I get a message like hey looks like you don't have permission to do that robot you Daniel are not allowed to run this robot because it might expose data to you that you're not supposed to see so we have that as an extra security isolation layer to control who has access access which of your developers has access to which robot automation you might have a large developer Farm you might even democratize RPA development to give it to Citizen developers or into business teams and with that you have the opportunity to allow who can see what and that is actually done in RPA Hub um let me just go there so you can see where that is okay obviously being on camera password there we go so on RPA Hub another thing you find RBA Hub now in workspaces so no need to fiddle in the all menu and go way deep it is just here in workspaces RPA hub and in here I'll go to my bot process let's take for example the RPA challenge that I just showed on that RPA process we now have a related list once it's loaded that allows us to control who has access to this robots uh where is it gone why it can't find it in here where did it go ah no it's not here sorry yeah my bad it's actually on the robot yeah y y my fa so I'll go to the robot machine on that robot machine go over to the machine not to the relationship we have that list assigned Studio users that says who is allowed to impersonate a bot process of that machine so that's in here where you can control that I'm surprised to not see my name at the moment so where did it go did I have a filter I'll check for that in a moment that's basically where you can say hey within studio who is allowed to impersonate this machine right um that that's that setting that will bring you back to this error message if you are not part of that even if you're full administrator on the service now instance you still need need to have that assigned bot process privilege assigned Studio user you can see that he it's on assigned Studio users on Daniel's VM so that's I took that screenshot from should be there whyever it's gone in my instance at the moment probably filter that allows me access to to that given bot right yeah I think it's an added layer of security that's added like who can access certain bot processes and everything yeah absolutely and the intention is Bots use for example credentials or sensitive data they might use HR information and you don't want to expose that to every RPA developer you want to limit who has access to certain organizations right yeah and I think like uh this time we we have focused a lot on security thing so Daniel I think there is one thing that also came up is the Q sensitive content right so that's that's also there so we have q sensitive content we have set password secure we have bought process restrictions so lot of things uh like the RP team has done done to improve the security as you mentioned that it is in the slides in a few few slides down but as you mentioned let's go there we have on to the cues now I need to think which one I think it was the invoice que that I set up for this one on the Queue now you have a new flag which says if a scroll is it sensitive content yeah here is work item content sensitive you see this is a new checkbox um in this case it's activated once it's activated you can't change it back anymore it's it's one time switch you it and forget it it's there and this means everything in that content on that queue is sensitive and should not be exposed if I now look into one of the work items for example this I put in here this is a sensitive item and you scroll down you you still see like status and QE and stuff like that you still see that that's fine but request content this field you don't see the content any longer this is used standard encryption on the platform and only the robot will be able to read even an administrator has no easy way to get the yeah obviously is service now encryption on the platform if you are malicious enough you will be probably find a way to get there but it is at least hidden from the suspicious eye it's not that easy to get to anymore got it so R like do we need to do anything else in the design studio uh if we just enable this Q as sens do we need to do anything oh that's it on the Automation in in the studio it's just working the same way than before and uh this is by default like sensitive or is it something is off if you want to use that feature you need to turn it on onto the que right so that's basically come on back onto that que record onto the details this flag is off by default and you need to enable it where you actually want it gotcha awesome so let's move forward um so that's kind of high level on the desktop Design Studio piece of things now let's look at RPA Hub what we in roduced there also there I think quite a a few good important security relevant features talking about security the first one that has highly been asked in in I would say almost every customer that I talk to about RPA is external credentials we always had credentials in the service now world right we stored them as part of your Bot process as part of the credential sets um and we stored the username and the password encrypted and save all good but we still stored it in the service now instance Now using external credentials we can actually store them somewhere let me quickly show you on High level how that works uh clearing out a few things here yeah yeah close I think was it in here already so here we have a bot process it's called an invers process you can see it has a Windows credentials we always need that to lock to the Windows machine and if I'm not mistaken you can see already here the windows credentials we can store externally also at the application CR credential where I did that here in the example we have an Erp credential which we say It's actually an external credential so it's not stored in service now then we ask you where do you start it externally in this case we there's one record called demo cyber Arc and I'll show what that means in a moment and what kind of input does that credential store need to get us the password in this case it just needs a name credential data but you could have kind of all kinds of different inputs that are required to find the password in that credential store now how does that work how do we know to get to a cyber Arc and get the credentials from cyber Arc to get in here we have our external credential walls as part of the administration and here we have just one currently yeah demo park that's kind of the the standard record we ship um by default it's inactive so if you want to use it activated but the technique behind uh actually is we we give it a name and we give it a subflow so we are using a flow inlow designer to get to the actual credential so technically how does it work let me see I got a slide on that that's straight out of the documentation slide so if our robot here on top of the screen needs a password it will actually send the question to the service now instance saying hey I need the following credential and if that credential is enabled for external credentials then we will call the subflow passing the parameters that we just showed that Chason piece and that subflow can do whatever it needs to to get to the password we bring you an example flow for cyber Arc but you can build your own flows going to hashu cor to asak key wall to any other wall that you have you will just need all you need to do is basically build that flow that might be able to might be using a mid server might be using a rest call external wherever you keep your password that flow all it has to do is return the password and give it back to the robot that's that's how it works this is a completely extensible architecture so you can do any kind of external credentials that you need absolutely I think uh lot I have also talked with customers and one of their thing was like they don't want to store the credentials directly so this thing is something like will remove their hesitancy to use the RPA thing absolutely yeah it it opens so much more doors and it's we understand right that that that is one of the number one things that was asked in in the past absolutely um the only thing to keep in mind is obviously when the robot needs the credential it might take a few extra seconds to get it so your automation execution time will get slightly longer because we need to reach out to your credential wal and get the password usually that should not be a problem but if you having time sensitive things just keep that in mind maybe don't do it too often moving on another very nice feature for agents working with RPA is what we call the embedded taskbar Automation and let me show you a demo of that and then go behind how that is done let's close a few screens here uh let's go to I got an in incident prepared somewhere okay incident here we go so imagine you have a support agent working on a customer case or on a uh internal it incident ticket it could be an any task based record basically they look at record say hey Li we have here mismatch currency on some product web page blah whatever right so they are here and say well now I would want my robot to help me to navigate to the exact place let's say maybe open that product web page or open the CRM system to find more information about Alysa as maybe the customer something like that what you had to do up to now using the attended robot you would probably go down here start your attended robot start find the robot had a couple of clicks to get there and get the thing rolling right now with embedded taskar automation you can get a button your classic UI action get currency price for example and when you click on that it flashes for a second and you will see oh attend the robot is launching and executing the robot immediately so no more searching where to go what to do you can pass in information from the current record into the robot that robot is not the fastest you can see it's launching it the attended robot it's our VMS just a bit they more pieces but it's getting there it's launching it just for you with the simple click of one button get there and executing your robot this is a fantastic piece when you have attended robots and you want to integrate these attended robots with a service now process without the need of kind of media breaks clicking around so and I I think this is this is one of the amazing features journel that came in the release because what I felt is like when we are creating lot of forms in the middle to pass the data to third party applications we could have directly utilized the forms and all I asked this thing to the product team and they said like something is coming up very soon and that's embedded task automation so now it's very easy to leverage the service now forms rather than creating the middle uh middleware form to pass data to that form then to third party application which it will it will save lot of time for RP devs for this absolutely you see here now that is the attended robot bringing up a box right it launched a browser it could launch anything right it could do anything it want to you maybe let's say just convert US do to Japanese it's checking that web page and should come back I think with probably this one here um that's just a robot execution yeah it's 149 Japanese Yen right and you could pass any information from the service now instance as mentioned before so you could say well actually I don't want to convert one1 US dollar I need to convert 59 because that's what the customer ask for things like that you can start doing and the beauty of that as I close that down yes I want to close it I will close down everything again come back to the screen the beauty of it it is so simple to get that button again let's just go to RPA workspace and I show you how to configure that because it is actually really really simple you go in here in your um build feie piece you have a menu called attended configurations and that's where you define where to see these UI actions get in here has an active inactive flag so you can turn it on and off we can see which bot it should execute what's the label which table oops no no co-pilot which table it is triggering on that any task table will work basically and you define a trigger if I go to edit this one yes move it into edit State we can actually also modify switch scope okay classic scope piece I can move into edit conditions and I can say in this case I said if the short description contains currency and the state is in progress then show this by button all it does in the back is it will create a new I action record it will Mark these conditions for the record and do all the wiring behind who can use it this works great caveat currently it works only for classic UI if you want to have these buttons also from a let's say a workspace or now ux framework you'll need to add the declarative action on top but the docs will tell you how to do that's on our list as next right we we started with the classic U here all right I think yeah I have Daniel I have one question on this particular thing so for example I have like multiple fields that I'm getting from the form itself but uh there is one particular field like one particular piece of information that I need to pass so do I need to create a proper field or can I just create some other record or something like that oh yeah the the field parameter mapping I'm just thinking like can we just map a default value to a particular field like uh going into the robot you mean or yes going into the robot a default value so the field parameter M WIS control what information from the current record you want to pass into the execution of the robot um I have not tried to put in a fixed value I typically what I've seen is mapping an existing field from the record um I would need to try that can't stay on the top of my head Goa I'll also try it because I haven't tried that too so I thought like maybe you would have tried it well if it's a fixed value you can still put it as a process parameter on the bot process because it won't change right the idea for these ones is really changing content context sensitive information Goa what I meant by that is like for example I'm passing the information from a particular incident to a bot right for that particular incident let's suppose I need to pass certain commments or something which doesn't have a particular field on the form itself so how we can do that so that's kind of a thing I was thinking maybe I'll try that thing yeah sure let me know are happy to get your feedback and the use cases uh to talk about how we can add that yes awesome so let's move forward so that was embedded taskbar automation right got a little screenshot here of that tender configuration a request in that case and yeah that's just a screenshot but I given you the demo part of it next part sensitive data in in qes we talked about that you brought it up pra absolutely we have that work item content sensitive which will hide the request content only the request content not the response so if the robot send something back into the response field that is currently not considered sensitive let us know your feedback if you think that is also something we should protect for the time time being it's only the request content track automation locks is another I believe it's a kind of a it sounds like a tiny thing but I think it's it's really a major changer it helps a lot actually means we are tracking lock messages from the robot execution within service now you don't need to go to the robot machine and find some lock files and stuff like that we have that within service now and let me show you how that looks if I go again to my RPA challenge robot I believe um you all know the process jobs list which is whenever that process is executed you get an entry in here it was executed at which machine how long did you take and stuff like that and if I open for example the last execution which was yesterday we get a new tab here saying automation locks and I see messages like bot stter launching browser bot finishes browser closed so we get lock messages from the robot in here and how does that look in the robot let go to this piece and just open that so you can see it if I open remote project RPA challenge it's a part of the demo y that's the right one you can see we have here the lock component that's the lock component you have been using already that hasn't changed on the surface but underneath now it's actually taking that message and pushing it to service now rather than only to this execution Lo down here you will still see it here if I execute the robot you still see it down here but as it's executed from service now this messages will be pushed into the service now instance and this is a great relief you can put in a lot of different points in your automation lock messages how far you've come like Loops one out of a thousand or something like that and suddenly within here you can see what your robot is doing without the need to go onto the virtual machine that the robot is executing that's a great great piece of U making life easier for administrators to know what's actually happening and and we keep that per chop separated we had a sequence number we actually Purge the stuff obviously also as after X number of days and things like that so we take care of the housekeeping here uh we have them in here and that is a a big big help drag automation locks yeah there's the screenshot you get that in as as reference exactly what I've shown you at the moment and I think this is pretty much the last piece that I have here maybe not so much developer focused but at least maybe towards citizen developer piece we have added the help center to RPA Hub so if you're now in RPA Hub at any time you can click the question mark and it will open up the help cont let me just pin that for a moment and will it will find stuff relevant for the process for for the entry that you're on so if we go for example on a b process you see it's refreshing it's looking for Content that makes sense come on loading and it should give us information about what is a bot process yeah what is a bot process how to assign a configuration other helpful resources and as you navigate around in op ahub it will kind of constantly refresh and show you relevant content for the things that you're working on at the moment that's especially great for new starters once you probably a seasoned experience a developer you don't need it anymore you can turn it off again it will disappear and I think you mentioned I think Daniel you mentioned correctly like it's for new developers who are just starting with service now RPA solution and also for release managers they won't be having because they might be just started doing releases with RP and also this particular Health Center will will help them and I think I saw that we have added like almost 200 topics Heth topics and everything that's impressing I didn't know the number I yeah I I was talking with product team so and I saw a list I think there are like around 100 to 200 topics that they have added on this thing that's amazing that should make the adoption of it so much easier right as you get to what you need to when you need it basically let me see did I have anything else no that was what I had prepared for today's what's new in RPA have amazing questions comments feedbacks I think like uh one question I answered already in the chat was around uh about stop button thing like like developers are getting confused like stop button and graceful stop button so the easiest simplest answer is like stop button stops the automation then and there without looking into anything graceful stop if you use it logically it will stop the automation based on the logic that you created in the automation so that you don't get data inefficiencies and all like one of the use cases is like for example if a rpbot is filling a particular form right from a third party like third party application or something we click on stop button the record won't be filled fully and it will just stop there but if you use the graceful stop component it will go ahead and stop the after the form is fully filled so that you don't get like data incomplete or something for that other thing Daniel like like this is something I was just reading about like we we mentioned about cyber Arc thing right we can store external credential there so for example if a bot rpbot is calling a suff flow right that is can that like for example I'm I'm still trying to understand the use case but can that sflow uh do we need to store local credential for it or is it like going into external credential that that subflow if you want to integrate let's take cyborg for an example or hasik cob it's the same thing basically that would use an integration Hub spoke to connect to cyar so the credential to get to your wall yes would be stored in service now as part of your integration setup your spoke setup but we don't have individual credentials like for an EAP system or an HR System we would not store these in service now we'd only have that one credential to your Vault and from there we can get the credentials that we need need at the time we need them and we only pass them through we will'll never persistent so it's very easy for you as a customer to to turn off access right if you turn off that one account we have no access to anything anymore awesome I think that's great and yeah I think like one of my personal favorite is the embedded task Automation and Health Center so what do you think Daniel what's your favorite pick I know everything is awesome but what's your one favorite pick from my favorite pick I I do love theck Lo component that we finally get the lock messages in service now if you have your robot running unattended somewhere in a Data Center and suddenly you think like why the hell is it not working you don't need to go to the machine you can see everything I'm just an operations guy to see what's happening without the need to go there yes I I think yeah that that will be my that was a like I was getting uh like I I had a dilemma like which to choose log component or like all these things because everything is super awesome and log component is something like for a new RP developer when I started like I had no idea what's going on and at that time I had to check each and every components try to get the error and everything uh that's great I need to see like I haven't seen like how it's logging in the back end is it something like detailed logs or is it just error messages and all but uh let's I I need to explore that so yeah that's that's all we have folks for you from the RPA Department I hope hope you enjoyed it and we have lot of content coming up this is just the first episode we covered RPA we have a flow designer that's coming in the evening where I'll be with Jing in the mo in the morning time for us and night time for me and we're going to talk about what's new coming in flow designer and as you can see on the screen I just put a like put a whole calendar there like this is what coming up so today we have flow next week we have more creative tool box episode and other things that are coming up so and if you want to know about all these things go ahead and uh go to Dev ding. Ence Washington that should be coming up on your screen right now so yeah nev. Ence Washington so you will be able to find the content calendar and what's coming up and that's all I have for you thank you so much for joining us and if you have any any questions like if you're watch if you are not able to join us live and you have question go ahead and add your question in the comment we'll try to answer those things and yeah any final thoughts Daniel before we go off thanks for having me it was a great show thanks pavf I love it coming back every time anytime that you need me and I hope everybody has fun using these new features we love to have you Daniel always there is always something new to learn from you thanks for coming and and yeah thanks everyone see you bye-bye [Music] bye-bye [Music] oh