Name: Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.1.
Uploaded: 2025-06-25T15:30:40.087Z
Duration: 56 min 24 s
Description: Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.1.

Transcript for "Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.1.": Just gonna give it a few more seconds here. Alrighty. I think we might as well get started now. First, thank you all for coming, and welcome to Rocket Xena and Enterprise Orchestrator four dot five one release webinar. Before we delve into the content we have in store for you, just wanted to go over a few housekeeping items, to keep in mind. So, of course, we'll we are recording this session, and we will follow-up with you in an in, in an email giving you the recording link in the slides. You know, we'd like this session to be as interactive as possible. So on the right hand side, you're gonna see that chat button, and you'll also see polls. So feel free to ask a question in the chat or just put your thoughts in there. We'd love to hear from you. We'd love to hear your thoughts. And just a quick note on that, if we don't get to your question, we will with you in an in an email, so we will give you that answer. Lastly, we have a five question post event survey that will pop up when you leave the webinar. So if you'll please just take the time to, to take that, that'd be much appreciated. And just quickly here, this is the Rocket presentation disclaimer. And without further ado, I'm gonna pass it on to to Paul to introduce the agenda. Hey. Thanks, Olivia, and welcome, everyone. Hey. We have a great attendance today, so this is really cool. And we have some good stuff. So, just really briefly on the agenda, I'm gonna mention, just after this, self-service, and then, we'll go through the agenda in a fairly detailed way, via a demo, from David Young, our principal, engineer. So additional process functionality, action triggers, security and rights, and, one or two additional items. So we'll be looking at, in-depth detail of those, and then, we've got one or two other, features just to mention as well. So, Olivia, if we, if we move on. First of all, I'm proud to present the first of these features. It's it's called self-service, and think of it as democratizing, automation. So there is now a capability within Xena and Enterprise Orchestrator for you to be able to build, workflows under IT control or your site reliability engineers or your automation experts, and then allow, business users in other departments to be able to trigger that at will whenever they wish. So for example, you could have a an HR department, given a button to do, employee onboarding, for example. So the the workflow is built. It's, it's it's under control. It's audited, and yet it can be triggered as needed by someone in perhaps HR. There are many other opportunities, for for deploying self-service capability, perhaps, security to, block block someone if there was a if there was a security issue, perhaps running, payroll requests, things like that, maybe creating virtual servers for training, departments. So the idea is that you get asked a series of questions, perhaps a name, an email, or the number of virtual servers you needed. You press the button and then, off it goes. And it it builds that workflow for you and and the task gets done. So, accessing it would be via named users. So, again, you have good security, good control, and we'll be looking at a demo of this. David will give us a demo of this later on. So for now, that's just a quick heads up on this this new exciting feature. It's an add on to Xena and Enterprise Orchestrator. And later in the year, we think it might be an add on to Zeek as well if there are any customers on the call who are running Zeek. Next slide. Okay. I think we're gonna go straight into the demo, actually. So Oh, right. Okay. So, David, Young has joined us. He's a principal engineer, and we're delighted to have him, to go through a demo. So now we're gonna transition over to David. David, take it away. Thank you. Great. Thank you, Paul. I get the fun part here. I'll show you some new functionality here. We'll start with the the self-service screens here that Paul just mentioned. Just to give you an example of what that's gonna look like when, you have somebody come into this. The setting up the screen, you have control over the colors that show up, the title that shows up here at the top. You You can have an icon displayed over here to the on the title bar on the left hand side. And then, basically, you determine what is gonna display on the screen. In this case, in the case here, I've just, added a a job list widget in which you can specify which jobs you want this person to be able to run. In this case, I've set up three different jobs that, this person can run. We also have just a a simple note over here. You can add images to this. You can put whatever text you want in this. We have another widget where you can add any type of report that you want in this. But, basically, what this gives is whoever's gonna come in here and run this, it's a simple screen where they really don't need to understand the product in any way. They can come in here and just see those things that they need to run. They can you know, if I just click over here on the run button, we'll get that fired off. Now however they wanna run these. And you'll notice as as we're running this, you see the status of the the different jobs change. They can see those as they're running them. They have a few other options here to see the details of that item that run, in history for it, and then also being able to run, possibly hold it if it's running too long. If it's been held up, they can release it, or they can actually cancel it also. So just some basic functionality that they're given at this level. Here, I just have these reports for for any of these items that they've run up here to show up down here so they can see any history quickly from right down here also. But, again, it's just a simplified view into being able to run something. So if you have, like, you know, any any nontechnical user that needs to be able to run something or, some business user that needs to be able to run something, you can easily provide this view for that person and they can come in and and run those items. Just to quickly show you how that is set up within Xena, I'm gonna switch over here to a a different view here. You'll notice on the authoring side, we have a new section here over here on the left hand side called self-service views. If I click on that, you can see here I can set up, as many views as I would like to. We'll drill here in just to one of these ones that I've set up prior. You give it a name. You can see who's the owner of it just like you would any other, the other folder. Here is where I can now determine which people are set up to actually view this self-service screen. If I click down here on details, this is where you can set up the title, how you want that screen to look, which logo you want displayed on there, the color, so the header font color, body, background color. So you have control over all that. And then along with that, here is where you can set up the widgets. Okay. And on this right here, it's similar to the dashboard where, basically, you know, you have this full screen. You can select the layout that you wanna see. We have some predefined layouts here, and you can have just something that takes the full screen. It's broken up into two columns, broken up to two columns where one's larger than the other and so forth. You can see all the different options that you have there. In this case, right here, I have it's set up where it's two columns. One's a little bit wider than the other. And in this first one is where we display that job list. And this is where I can come in now and define which processes this person is gonna be able to run. And in this case, just as you saw in the demo, there's this process called block security account creation and equipment provision provisioning there. I'll I'll click back over there just really quick so you can see how those showed up over here. So it's just a, you know, little section where they can run each of those items that are defined within the definition of it. You can also, for each of these, determine, what the height is. You know, if you want it small, medium, large, or or even larger. In this case, it's large so that I could show those three items in there. If if if there are more items that that that can be displayed in that, you'll see a scroll bar, and they can actually scroll down on that. So you can add as many items as you need there. David, quick question. Yes. Yeah. So question is coming from Keith. So they will have no way to update a variable. Can they update variables within self-service? If if there are variables, those will show up on that when you do the run. They'll be able to add those variable values at that point. So just just like you could when you're manually running any kind of item, those variables will be available just as they were there. Okay. Great. Thank you. You could you could really think of it as similar as, you know, being able to run it from here is no different than right clicking and just running it manually from the definition screen. So we'll have all those same options. Okay. Just a quick note on this. Even if you're not licensed to use self serve service views, it will show up. You'll be somewhat limited. You'll only be able to set up one user to be able to run that. And, you'll see a on this screen, there'll also be just a a little toolbar here that shows that it's not licensed. So you can at least try it out, see how it feels, and get familiar with that. And then, then you're if you get licensed, all those will go away. You'd be able to set up as many users as you're licensed for, and and that, nagging toolbar will not be there. But but you can try it out even if you're not licensed. Okay. Just one last thing just to quickly show you. When you set up a user, I'm gonna show you just quickly this self-service user that I set up here. You'll see an option now at the bottom of the screen that this is a self-service user. If they are a self-service user, the only way they'll be able to come in is through a self-service screen. So, you know, either they need to be a self-service user or a regular Xena user. And if I have multiple views, multiple self-service views set up for any person, you'll notice up here, there's a drop down, and they can go to any of those views that they want to. We'll we'll persist which view they were on last. So if you exit out and come back in, it will start with that view at the beginning. So but, you know, may maybe there is something more than just these three jobs that this person needs to do, and then they can click on that, different view from that drop down that's on the top toolbar. Okay. I think with that, that kinda gives you an idea of what self-service will look like. I don't know if there's any questions that came in on on anything else that I needed to discuss on that. Yeah. There's one more, David. For sharing, can be can be set up as a role? Yes. Yep. Sharing can be set up as a role. So you could set up a self-service role and then just assign that role to any, those users that you want. And one more self serve yes. Thank you. So, one more, will self-service take out my client licenses? It's licensed separately for than, regular client licenses. So you it won't affect your Xena licenses at all, but you will need to be licensed for, specific users through self-service. So Okay. Great. And one more. Can self-service jobs have, prompts? For example, the user to onboard. I'm not sure I understand the question. So when you click the, self-service buttons, it can it can deliver a series of of prompts, can't it? So, for example, you can put in the username, the email address, department, things like that. Well, you know you know, again, just depending on what variables you have set up for any process. When you run this, you'll have that option to enter that information. Right. Okay. Yeah. Yeah. So, that's a that's a yes to your question, Ed. Yeah. I think so. One more. For the HR example, could you pass an employee number to process when starting the jobs? Well, just as anybody else running that process, that user is part of running it. And those are available as, attributes. So, you know, if if you're using scripts or doing mapping, you can map that. Yeah. The the user that actually ran this as part of that. So yes. Yes. It is available. Brilliant. Okay. Thanks for your question, Ali. Okay. Let me just scroll down, make sure there's none more. I think I got them all. Okay. Okay. Then I can move on to some of the other new functionality that will be part of four five one here. Thank you. We'll start with some of the add additional items we've added to processes. I'm gonna come in here and just start a new process. If you notice over here on a root process, there's a new section we have in here called dependencies. This is no different almost than coming in here. Let let's say I didn't want anything to run-in this process until a certain dependency was met until another process had run. You know, currently, the way to do that is you put that process dependency at the top and then add, you know, additional items in here and then set them all to be dependent on that other process running. What you can do now is set up dependencies at the process level. And let's come in here, and it looks no different than setting it up within a process item. You have the same things. You can select the process and all you have all these different the same options that you would in a process dependency item. But what this right here does, if if I set this up here let's just let's just temporarily put a quick something here. Give it a name. Let's do the basics there, and I'll select okay. Having this here, I no longer need to have this here at the top level. And the the benefit of using it at this level is it will keep the process from taking an active slot. You know, if you have a limit, we, you know, we have a I think it's a limit of about 2,000 active processes that can be running at any point, which, you know, that can be modified. But what this right here will do is it won't even be in that group until that process dependency has been met. So it's basically being held up till till that dependency is met along, you know, with any, you know, other time time dependency. So so, anyway, so just, yeah, just just that new item that you can have there. You'll also notice on the the root process here that you can specify a priority now. Now this will only take effect if you are getting close to you the the the max number of active processes again that you can run. So let's say you were down because of some disaster recovery thing, and you're coming up and there's gonna be more than 2,000 items that possibly might go active. Setting the priority, it will pull those with a higher priority prior to the any of the others. So it just just gives you an option to make sure that there's certain processes that they're gonna run prior to others if there's any kind of disaster recovery or if or if you're just, having a a huge amount of items running at any given point within the day. But you can give those now a priority. David, Keith asks, will these show up with a reference to a process? With a reference. Well, it'll display as a column. You know, if we come over here to operations, there there there will be a a column there for the priority, and they can also use that in filtering within process views. So that that ability to pro the to filter, you can also filter by that. So that's some additional logic you can use for being able to filter, use, and search by. Thank you. Okay. I'm gonna exit out of this. Okay. We've given some new options. Let me let me drill into this process a little bit. More. David, one more before you go on. I think Keith come back on this one. From authoring, if I say show references for a process, will they show? Oh, references is basic oh, is is this for the process level dependencies? Is is that what we're talking about? Or Yes. Yes. It is. Yes. That's what it is. Yep. Yep. Just just as any, you know, any anytime you're referencing something, whether outside, that will show up in the references. That's correct. Alright. I think we got it now, Keith. Thank you. Yeah. You said that. Yeah. I was thinking yeah. We were still talking about priority there, so I'll just get a little. Well done. Okay. Connected. Okay. I'm gonna go here, and we're gonna take a look at triggers. And I'm gonna drill into this event trigger. This has been reorganized just a little bit. You're gonna notice there's a new section in here called conditions. In there, we pulled off something that was, previously underneath options, this ability to conditionally disable a trigger. But you're gonna notice on the event trigger, there's an additional options in there, being able to enable a conditional script. And what this gives you the ability to do is to do some preprocessing on this event that came in to determine really if you wanted it to be used fire off this process. And just to get an idea of some things that you can do within this script is you can pull any attributes from the event that came in and compare it, like, you know, you can in this case right here, I'm basically saying if the the file name of the this is a directory monitor. So I'm saying if that file name that, came in for the file that we found includes next day, I'm saying, okay. We're actually gonna say event dot deferrent till next day. And what this will do is you'll notice if we if the an event comes in and it hits this, you'll see that it's be it's gonna be scheduled for the first thing, for the next day. So if I go into look at the next day schedule, I'll see that that's out there and scheduled. You can also and just in this example, it's just, you know, a dumb example here. But if if the file included a delay in it, I'm actually gonna say, go ahead and just get this in the schedule, but defer it for thirty minutes so it's not gonna run for thirty minutes. Or if it came in with skip in this case, I'm just saying let's just go ahead. I don't even wanna process this. I don't care. I don't want this process to fire off if it contains that name. But but, again, now this is you know, what whatever type of event you're looking at, you can compare those attribute values against anything to determine how you wanna possibly handle that event that came in. So it just gives you some abilities to further, determine how you wanna deal with that event that comes in. David, question from Spencer. Is next day the next calendar day or the next production day? It is the next production day. Okay. Got it. Thank you. Yep. Good question. You see, I'm just I'll just show you a quick example here. We'll come out here to directory monitor here. Here, I just have some test files that I I set up as an example. You'll notice here this one the first one contains the delay. So you you should see that one being scheduled for thirty minutes after we receive the event. This one right here, test data to skip, because that contains skip. We shouldn't even see something that's scheduled for that one. The next day one, we'll see that one getting scheduled for the next day. And this one right here, because it doesn't match any of those strings and because I'm not doing anything else otherwise, it should just go immediately into the schedule. So let me just copy these here real quick. We'll come back here and paste them. I'll watch those and they're still hopefully, they get picked up here pretty quick. Need some of that. Okay. There we go. So now if I come over here to operations, Oh, it looks like I need to to be on the correct day here. Okay. Okay. You'll see here that the directory monitor process was fired off twice. K. The one that went active, I I went ahead and took it and mapped the file name into the alias just so we could easily see here which one, caused this to be fired off. So you can see here that, again, the one that didn't have any of those that match for what I was checking, that one was fired off immediately. The one that had the delay, you can see that that's scheduled for thirty minutes from right now. And if I go and look at my next day, you can see that here the next day, process was added into that next day. So, again, just gives you an idea of what, control you have over here for events that are coming in at any point. Okay. I'll move on to the next item here. Let me come back here to our previous day or current day. Okay. We've done some changes for being able to see predecessors and successors or, you you know, we've called them dependencies and dependents prior to this. But what I'll do is I'm gonna come in here into process b. I have four processes that I've fired off here. This one right here has a dependencies in it for other processes here. And if I wanna see what those are, I can right click on this now, and I can come down to view and click on predecessors. And when I click on this right here, you can see that within my process b, which I just selected, that it has a dependency in there a process dependency in there for process c and for process d. And process c has a dependency in it for process a. So if I wanna see, you know, maybe why something hasn't been fired off here, I can click on this right here now. It'll give me the details of what that dependency is within process b and then also show me currently any items for process c that are running out there for the current day. So I can see maybe, you know, maybe, help me understand why this hasn't run yet. And, you know, as I click on the different items, now it's showing it for process d and now for process a. So it just gives you a way to to better see how those dependencies work within the the the current schedule. Any questions on that one? And it works the same way for successors. You know, if I if I clicked on process a in this case, I'd I'd see the the the succession of who anybody that's dependent on process a. Yeah. David, couple of questions if you can. So Keith says, is there a way to extract from the tool? To so sorry. To extract that from the tool. And, well, you you know, you you can always print, you know, this list right here, you actually have the same abilities you have from, the processes list. You know, you can view the properties of this process that's in the list. You have the operations that are available here, the views. But you you can print these lists. I I when you say extract, is there something more that you're you're asking for? In specific, it's the predecessors and successors. Also, a report in a sense that shows those? I think Keith is looking to extract that from the tool. So maybe, maybe Paul or maybe, some other mechanism. He says yes. So a a a report. Okay. Yeah. Currently, yeah, this view up right here is just a view. We we could we could take a note on that. And may maybe you could give us some, deep just a little more details on what you're specifically looking for on that and something that we could look at. Yeah. That sounds like it needs an idea. The office, mapped that one out. Okay. Great. Question from Mende about the events. Is that for all event types or just directory monitors? That's for any any event that can come in, whether it's a user event, a directory monitor, any other type of monitor in there that generates an event to come in. Okay. Great. Yeah. Yep. That that could be anything. So, yep, depending on the the type of event you're expecting to come in there, that's where you make sure sure you're just pulling the types of attributes that are part of that event to to perform any logic there. No other questions at the moment and no follow-up on that question. So I think we're good. Okay. Yeah. And then they says thanks. Okay. We're done. Thank you. Okay. Awesome. Okay. I'm gonna show you some additional triggers we've added into our actions. Again, just a quick review of actions. Actions can be fired off from task. They can be fired off from a process, and they can also be fired off from triggers within the action. And I'm gonna click over here on on our triggers here. We've added in here some additional triggers, one for an orphaned task. So if a task goes orphaned, they can have an action fired off. Or if a service goes unhealthy, they can have a trigger fired. This this trigger will fire off this action. Or if it they have a disconnected agent. To to help better understand how the disconnected agent, logic works is it's not gonna send the event immediately when a when a, agent goes disabled. If if it's been dis if it's been unconnected for longer than five minutes or if during that last five minute period it's been going up and down, then we will fire off this disconnected agent event. At that time, basically, we're assuming that there's some problems with that agent and and somebody needs to be notified. And just like, let let's come back here to the to the, action level here. From an action, you can fire off any number of action items, and those can be, alerts, SNMP traps, and email. You can send an event. You can have a log written out, run a process. And, again, let's just look at the one that I have set up here. It is basically you know, I have it this going off to some person here. And what I've done is I've mapped in what agent name is gonna be used when this email is fired off. So at the at the action level, I've set up a variable called agent name. And then setting this up is what that gives me is now within this trigger. I'm gonna click on action variables. Because this is a an agent disconnect, when I'm inserting a token here, I have the option to map any of these things regarding that agent that's gonna be disconnected into this action variable. And then once that's been mapped, those action variables will be resolved for these action items. So you'll you notice what, what, information we had available for the disconnected agent. If I do this for a unhealthy service let's go into one of those really quick. You'll notice on this one, I actually set up the error message, what the service name is, and what the agent name is so that I can pass all that information along to this action item. Now that information will be mapped into that. And then at the trigger level, I'll come into this, and this is for an unhealthy service. Now I go to these action variables, and I've mapped the error message that came from that agent, what the service name is that's unhealthy, and what the agent name is. So if I come into these, you'll you'll notice now when I come down to agent, there's a a little bit more information that I can use to map because it's an unhealthy service unhealthy service trigger. So, anyway, yep. Depending on, you know, the type of trigger that you specified here, you have different information that you can map into the action variables. But, anyway yep. So that basically you know, you you get an unhealthy agent. You have the ability now to send an email, create an alert, an SNMP trap, or whatever you like for that unhealthy service or if an agent's disconnected or an our task has been orphaned. So those options are all available now. Any questions you're seeing, Paul, coming in on that? No. We're good at the moment. Let me just refresh and make sure. No. We're good. We're good. Okay. Okay. Great. Let's see. Next on the list, we have added a number of new rights. Prior to this version, anybody had the option to create views within operations, but we have added rights now for the ability to to actually set up these views, whether it's within alerts, milestones, process, or a task. So, you can turn that option off for a user and not allow them to create those views if you'd like to. We've added a right for the ability to create a user owned folder. If you only want somebody, you you know, if if somebody does have a right to create folders, but you don't want them to be personal folders so that they're kind of hidden down there, you can turn that option on, within within a role. Right? And that will prevent a user let's I'm I'm just gonna kind of just show you an example here. If I came in here and I did not have that right, by default, you would not see any owner in here, and they would have to come in here. That option, the user option, would not be available, and they would have to select a role and specify what role will own this folder. And, again, basically, that's making it so that that person just can't have any personal folders out there that nobody else can get to. We also have added a right for the ability to be able to enable and disable a process even though that user doesn't have the rights to modify the process. So, you know, if it's an operator that, you know, that you don't want them being able to change the details of a process, but you do want them to possibly be able to enable or disable that so that it doesn't show up in the schedule, You can you can give them that right now. Keith says very nice to the previous item, David. Okay. Great. Great. Glad that's something that somebody can use. Another thing that we've added on all of the file based tasks is an option to put in there a a login that will be used to determine if that user has rights to, either create, move, or do whatever to a file within that. So, for example, let's say we're using the, AWS s three task and we wanna pull a file down from AWS to a local directory. You can force that user to have to specify the the login that will be used to determine if that user's credentials have the rights to write to that given directory. So, you know, basically, any place where we're dealing with files that need to be written to a a given directory, they you can force the users to have to specify an OS login that will be to use to determine if that user has rights to that directory. So it just gives you a little more way to secure directories that files are being moved from, deleted from, or added to. Okay. This one kind of goes along with the the last thing I mentioned. You know, I I know lots of times, our customers had to deal with cleaning up users that have left the company and have to deal with finding these personal folders or items that the that that user's created that have to be cleaned up before they can delete that user. So let's let's let's say, for example, here I've got this user, user's name is Joan. This user's gone out, and in their private folder, they've set up a task. They've created another personal folder out here called my stuff. It's it's it's something that nobody else can see, and they've created a system command in there. And now that user's left the company. And let me go ahead and just close that. We'll come here. So if I come down to users now, I can click on right click on that user, and we'll say, let's delete this user. You'll see an option that comes up now where it's gonna basically notify you that any folders that were owned by that user are gonna be added to a new folder underneath the current user that is prefixed with underscore deleted and then followed by that user's name, which will contain any private items that that user had. So let's let's let's let's go with this example here. I'll say yes. That user was now deleted. I refresh my folders over here. I'm gonna click and expand this. You'll see a new folder that was created over here, deleted for Joan. If I expand that or click on this, you'll notice now here's that item that was in that user's personal folder, and then also here's that private folder that that user created that has and and now I can do whatever I need with that. If I determine that we don't need to do anything with those, I can just come here and delete that folder. Or if it is something that's being used by other items, then I can move it into a a a more visible folder. So just just an easy way for that, user to be able to be deleted now. Makes it very easy. Okay. Let's move on quickly here to the next item. Underneath operations now, you'll notice that there we have views added now for tasks. Within those views, you know, you have filtering options just like you have under others. You know, you can filter by name, alias, value, status, agent type, and so forth. So just just a way you can set up views that will include just filtered, lists. And, again, just just like I mentioned that we have rights now for being able to create those views that that also applies to this new tasks views. I'm getting a nice here from Monday. I think that's related to this task new task view, David. Okay. Great. So it's going down well. Okay. Another option that we've added, for those using LDAP I'm gonna expand this right here really quick, and let's click on user security. If I am using LDAP as my authentication method, you'll notice down here, we've added a couple of, additional items that you can specify. You can specify, what attribute within LDAP contains the username, what one contain contains their email address, and what possibly contains their phone number. And what this will do is if a user's coming in the first time through LDAP and we automatically generate a Xena user in that case, rather than just giving it some default information, we'll actually now pull And and and, again, this is only for those items that were specified here within the scheduler properties. But if those have been populated, we'll pull from this attribute name specified the username, and that will be used used for the name of the user within Xena. This one right here will be used for the email address that's added into that user's, record, and then the same thing for the phone. So, basically, you know, you you don't have to go back into that record and update any of this in case you're using this at, you know, within processes for, being able to email something or or whatever. And, also, the the the other thing that happens with this right here is if a u when a user logs in and if any of that information has changed within LDAP for any three of these, it will update the record with that information. So, you know, you can basically just maintain this information within LDAP itself, and it will automatically update the that information within Xena. So just an ease of use thing there. David, question from Alex. Is is the phone for a text notification? We don't have any way of doing a text notification, but it's just if you wanna map it in to any kind of task, you have that ability. So it's, you know, just any place where you can map user information. Like, for example, you know, anywhere within a process, you have access to the user, which is basically the user that fired that off. And you can map any of that user's information into any process variable, which can be used again then by any any task. You can pass it along to any task or any subprocess or whatever you need there. Okay. Thanks. Okay. Another just quick little piece of information here. Now within agents, we can specify a maintenance window. Once that's enabled, you know, basically, anytime we we the the time matches the calendar and the time range, there is not gonna be anything new that's sent down to that agent. So when you know, if you're specifying, for example, from two to five on Saturdays, nothing can run. But, basically, that means from two to 05:00 on Saturday, nothing's gonna be sent down to that agent. Well, in the in the case where, let's say, you you're you're there on Saturday, the it's 02:15, and you know all the maintenance that's, has been completed on that agent and you wanna be able to continue running things on that, you'll be able to easily now just from the, the list here being able to come in and resume that. So you don't have to wait till the end of that maintenance period. So just just a an an ask that we'd received from a customer there. And then finally, just some miscellaneous things I'm gonna mention here. You know, if you hover over any item up here on the top now, you'll notice that it now displays the full name. We've we've always just for example, here under definitions, let's, just open here just doing like this right here. In this example right here, you know, we always just show what type of definition it is followed by the ID. And the the whole reason for that was because those names can be, in some cases, I've seen extremely long. And with that, that would take up the whole tab bar up here. So what we've done is, like, again, like I mentioned, we we display the type followed by the ID. But now if you wanna see that name, you can easily just hover over there and quickly see what the full name of that is. So if you have a long name, you can see those up there. On our REST web task service, we've also added the the patch method as an option in there. From within a process diagram, you you also have the ability now to print in either landscape or portrait mode. And then there's just been some, additional items that we've added to reports. But, again, these are all available from our release notes here, so you can come through and quickly just see all the new items that have been added to our April release here. And, Paul, we'll be just going over some of the new services that we've added here here in just a minute here. But I I guess I'm I'm kind of wrapped up there on the on the demo, Olivia. I guess, next, we're gonna go through a quick polling question regarding the the self-service. So I'm gonna stop sharing here, Olivia, and I'll let you take over. Thank you. Yeah. Well, we're kind of switching gears here back to self-service. We're gonna feel, load up the poll for us. You you guys will see, yeah, the poll tab pop up, kinda where the chat is still on the right hand side. So the poll question that we wanted to ask you, just because, you know, self-service, like Paul said earlier, was democratizes information across depart across departments. So what tasks could other departments schedule on their own using self-service automation? Like, what do you if you're about to use self-service information, what tasks would you think, would be better for those other departments to handle? So if you'll just answer that for us, we'd really appreciate it. So some of the answers we have are password resets, report generation. Paul, I know you mentioned this too. Like like, HR or anyone else needs to have a new employee onboard, like setting up accounts, granting access to systems, transfer files between different systems. Or if you think you have a whole other use case, we'd love to hear about it. So if you wanna just pop in the chat, I'd love to hear, sure we can do a lot with self-service. So let's see. I've even used self-service to set up ACH runs on request, in in some credit unions. So it's, yeah, it's a lot of opportunity. That is it it is a lot of opportunity. It's kinda one of those things where when you open it up to other departments, like, you kinda see more of the value the more you open it up. So it's really cool. So we're just gonna give that just a few more minutes here. Oh, and David here in the chat says, like, all ad hoc requests. So agree. Yeah. Okay. Accessing reports is an is another example. I worked at, with a with a Swiss bank. We we created over a thousand self self-service buttons and put all the reporting, at at users' fingertips. Yeah. It's it's really amazing, and, I'm just gonna give the poll just a few more. I don't think I can see the results. So I don't know, Paul or David, if you see the results yet, but I'm sure we can. We're using a new platform. So not yet? Okay. All good. We're we're still, figuring out how to use this platform, so thanks all for your patience. So okay. My trusty, right hand woman here, Ruta, actually just sent me them. So, actually, most so we got a tie here, ironically. So we have 11 votes to report generation and then also another 11 votes to transfer files between different systems. So, hey, that's pretty cool. Makes sense. Yeah. That makes sense. Would would you think, Paul, would were those your top in your top two use cases, do you think? Yeah. Certain certainly up there at the top, creating virtual systems, think on demand, running running ad hoc tests, all those kind of things, it would be up there as well. Okay. But that's good. It's good feedback. Yeah. Very good. So I think that we're gonna close that poll. Thank you all for your for your feedback. Really appreciate it. So I'm just gonna share the screen again. So you'll be able to see Paul's gonna dig into some of the the new integrations that we have within the 04/1945 point one release. If you'll take it away. Thanks, Olivier. So, yeah, I won't dig too deeply. But, luckily, we have David here in in case we have technical questions. So AWS EventBridge, SQL messages and batch, and then, AWS mainframe modernization, and then just your data factory are just five of the integrations, the cloud integrations that we've been able to get into the April release. I really wanted to say that, when when we introduce these integrations, we're really, giving you the ability to to execute tasks, to interface to those those services and tools. And when we monitor, the request and then we get success failure, this kind of thing, and then that can be embedded in other workflows and tasks. So it's a it's a it's a it's a complete, circle in terms of the features and functions there. There's loads of other things we can do with some of these. There's probably too much to go into today. If there are technical questions, then feel free to put them into the, into the chat. Really just an into an introduction to say, look. Those five are there at the moment. The main thing I wanted to say is we're really big on cloud integrations. We've got a a a really impressive road map mapped out for the next two releases. Cloud integrations feature very significantly in those, road map plans. If you specifically want anything, then please let me know either directly via email or you know, a a really good option is to join our customer ideas, trial. So we're trialing this with some customers. If you want to go on and email me, or or Olivier. And that that gives you the ability to add enhancement requests directly into the ideas portal, which is exactly the same tool as we use internally. So we see your idea. You can monitor the status. You'll see status changes, without necessarily going to to to support to say, hey. What happened to this request, this enhancement request I put in three months ago? You'll be able to see that change, add comments. And, also, I think this is a really a powerful, feature because it builds a real community around Xena and Enterprise Orchestrator. You'll be able to vote on other tasks and other enhancement requests that other other customers have have requested as well. The votes don't necessarily, equate to the the order that we do things, but it's a strong indication, and we love that customer feedback. And at the end of the day, we're building this for you. So let me know if that's of use. And if you have any quick questions on, on the integrations, fire away. So I have one question from Sherry. Will Xena add the capability to talk to multiple domains for user authentication? We have one domain for the server and one domain for the user authentication. David, is that something you could take now? Yep. Well, that's that's something we have on our list of enhancements. So that's something that we're looking at. Okay. You'll see an idea out there. Yeah. Yeah. Yeah. Yeah. Sherry, thank you for your question. Let me know if you want me to want to be part of the customer ideas portal, and you'd see that request, within the list at the moment. Yeah. We we would yeah. We've received that from a number of customers, so that's something that we are actively looking at. Great. Thank you, Dave. Okay. And I guess that shows any more questions? Nothing else. I don't think there's there's any more questions, but I think that really just shows how powerful that portal's gonna be. Like, everyone's gonna be able to vote. You get to see your peers enhancement, so we gotta vote on on that one. So that's really good. Alrighty. And Sherry says that's good news to hear. Yep. We want we'll we'll add we'll add your, your name to that one as well, Sherry. Thank you. Okay. Olivia, back to you. Yeah. So just real quickly here. I know we have about six minutes left. So I just wanted to quickly share some updates within the Xena and Enterprise Orgashire community, like, how you can stay connected to us. We have a few promotions and just I was gonna mention the community just real quick. So, hey. If you would like to see receive a $25 gift card, for fifteen minutes of your time, if you'll just write a review about if you have Xena or if you have Enterprise Orchestrator, if you wanna just submit a review, that would really help us and get kinda help your peers also make informed decisions about these products. So I'm just gonna put this in the chat here. Okay. So if you'll go to those links sorry that those did not hyperlink. But if you'll just copy and paste that link, you'll get to you go to the the survey review and just spend fifteen minutes, taking the the survey. That would really help us. So thank you. Lastly here, I thought I'd share with you, the Xena and enterprise orchestrator community. Also, if you're part of Zeek, you have Zeek running, we have those forms for you. And this is really a great place. If you have a question, we have our experts on here that are on this webinar actually, David and Free. I've seen them pop up. Those product experts and David, I think, is in there too. Those product experts are in the community. So if you have a question or, want a how to guide, we we try to post every week on how to's, product updates, etcetera. So just staying connected to all of us, it's a great great place to do that. So I'm gonna also put that in the chat. Oh, it is hyperlinked, Martina. Excellent. So I'm just gonna put another hyperlink in the chat for you guys. So here we go. Okay. There we go. So excellent. So I wanna keep you updated on that. And lastly, so when you before you leave the webinar, a five question survey will pop up just about, your experience with this webinar. And, also, we have a question in there about, what kind of enhancements or what would you like to see more of in this product, which I think is really, impactful. So if you'll just take the the five minutes to answer those questions, we'd be really grateful. And if there's no other questions, which I don't see there is, I just wanted to say thank you so much on behalf of all of us here at Rocket. Thank you so much for coming, and giving your time to us. I will, unless there's anything else from David or Paul, I don't think there's anything left for me. We're good. Thanks, everyone. We're good too. Thanks. Okay. Thank you all for coming. Have a great day.