Create a UiPath Queue
UiPath Orchestrator Queue Tutorial
Hi, I’m Cameron Kenzie at Cameron. MCNC on Twitter. And I wanted to talk to you about QS and UI path. And specifically, I want to show you how to create one, and I want to show you how or read some data off that Q as well. So if you want to work with queues, the first thing you need to do is create a queue and I’m here in orchestrator, cloud UI path.com.
You click on automations queue, and then you just click the plus button and name your queue. So I’ll call it the insights. And then you can add a description if you really want. Um, do you want a unique reference? This will allow you to, um, make sure that only specific requests go to this queue, specify your auto retry.
Most want to demonstrate the basics here. So I’m just. Create this very, very basic queue. So the queue is now been created. And then the question is, how do you actually write to that queue? Well, it really couldn’t be easier. All you have to do is go into UI path studio and create a new orchestration proces
UiPath Flowchart Tutorial
Don’t create a process, create an orchestration process because the default process won’t work and I’ll call it, add message to queue. That would be the name of my project. I’ll open the main window and I’m going to search over here for the ad queue item and get reference. So I’ll move this over here. I didn’t do the connection.
So let’s connect these two up. That looks nice and handsome. And then over here, I just double-click and I specify all of the different properties that I need. So a double-click to open it up. There we go. And now it wants to cue name. And of course the Q name just maps to insights queue that needs to be in quotations normal priority.
I’ll give it high priority and then you can have an expression to, uh, save the output to, I’m not going to worry about that now, but I am going to worry about what I actually put into this queue. And you can see this collection here. You can code it in so I can say, you know, email and the value is email@example.com.
And then we could have a priority.
Actually. I don’t want to say priority because that would confuse us with the queue priorities. So I’ll say status, and maybe this person is diamond status, and then maybe we could have, you know, interests and then maybe their interest is UI path. And there we go. Let’s take a look at that. Here you go one extra one there that’ll just delete.
Okay. Now this looks handsome. So email, status and interest. And so that’s been set to the collection and I can just now save that and click the run button. It’ll just take a moment to run, notice that it started and it finished. And now with that completed, I can head over to UI path. There’s my queue. I’m going to take a look at that queue view transaction.
And you see that there’s one new transaction here. That’s the one that I just wrote. And if I take a look at the details on that, you notice that the email, the status and the interest are all configured there. So diamond UI path mail at MCNC, which is exactly what I configured here in the collection where it actually says collection.
So I just click on this and there you go, email status interests. And so that’s all been pushed up to the. Now, how would you read that? Well, that’s just done in a new UI path studio projects. I’m going to go home. I’m going to close this project and I’m going to create a new orchestrator process and I’m going to call it process queue items.
And then when this starts off, I’m going to open the main window and I’m going to look for the activity called Q items. There it is right there. I’m going to drop it. And this get queue items. It needs to know the cue name. And of course that was insights queue. And that’s just the name of the queue over here.
Insights queue. No big mystery.
and when this get queue items runs, it wants to take all of the items in the queue and hold it into a variable. So I just highlighted the variable there and press control. K. And the little set VAR comes up, which is going to allow it to set the appropriate type. And I’m just going to call this, get queue items, output, and I’m going to need that in the moment.
So I’m going to just copy that as I can. But that gets created. Then you can see down here in the variables gets created and it’s a type I innumerable with a collection of cue items inside of it. And when you have a loop, it’s a good idea to just loop through it. Or when you have a, an Iterable object is a good idea to loop through it.
So we hear I’m going to loop through that with, for each. I’m gonna just go for each of them, the elements inside this queue. So I’ll put it down there. We’ve got a four each I think going a double-click on it. And so for each item in, well, what was that? That was each item in the get queue items, output control asks there.
What do I want to do? Well, maybe I’ll just want to get the information that’s in the queue. So how do you actually get details of that item? So we’ve got one item in the queue here. If we view transactions and then even take a look at this and view the details. You notice that we’ve got the status and the email, how do we actually pull those properties out?
Well, inside the body of this four loop here, I’m just going to add a right message much better than the left message, right line. And then in this right line, I’m just going to say, well, each queue item is listed as an item, so I’m going to say item diet, specifically. Content and just ask for the email.
And of course, this has actually given me a little warning here. And the reason for the warning is in that for each loop, you’ll notice up here that the argument type is object. Actually want that argument type to be queue item. Cause that’s what’s inside of that list.
Yeah, there you go. Right under UI path, core queue item, click control last, and then just verify down here that we’ve got the two string and I’ll just kind of take that, put it into notepad. And there you go. You can actually see the whole content of that line there. You’re going to click control S here.
I’m going to give this little. And you notice that as it runs, it’s actually pulled that information out firstname.lastname@example.org. So that’s how easy it is to just pull data out of the queue. We can even copy that, copy that, and paste it in, paste it in right there. And then of course the other fields that we’ve got is a status.
So, you know, maybe just pull out status as well.
And give it another run. You know, we got diamond and mail at MCNC. So that’s, I actually pull out the fields inside of that queue, but notice that, that object still in the queue. Right? So it status is new. How do you actually change the status and actually handle it? So no one else is going to handle it right.
Once somebody’s handled something in the queue, you don’t want, I want it handled again. Well, what you do there is you just get the transaction. Yeah. So we just look for the get transaction item activity over here. There it is just pull it in.
It’s going to ask for the name of the queue. And of course the queue, we can find that out right over here. It’s the same one hasn’t changed. So it’s the insights queue. Put that in quotes here and then have an output for the transaction items. So where do we want to store that variable again? Control.
Will allow us to highlight their first control. K allows us to set a variable and just very boringly call it trends, action item, or that creates the variable that we need. You can see it down there. Okay. And now with the transaction item available to us, we can simply go over here and just say, Hey, we want to change that transaction status of set transaction status here.
And then we would, what do we want to set the transaction status to? You can choose. I want to set mine to successful then. Of course it wants to know what transaction item we’re talking about. And we’re just talking about this one here, the transaction item I just created.
And there you go. That now allows us to not only get the information out of the transaction, but actually get, get the information out of the queue, but also get the transaction item and then change the status on the object in the queue. So I click control us there, click run, we get the information. Then we actually start a transaction.
We end it and it seems like it processed the queue. So did it really well. Let’s go take a look at it. So over here, here’s our insights queue. Well, take a look at it. So take a look at the transactions. And now you notice this transaction that previously was new, has now been marked as successful and there you go.
That’s how you handle your transactions in UI path. There you go. That’s how easy it is to create some cues and UI path, and then do some manipulation of the data on that cue as well. Now, if you enjoyed that tutorial, why don’t you head over to the server side.com? Lots of great tutorials about enterprise software development and UI path over there.
If you’re interested in my personal antics, you can always follow me on Twitter at Cameron M C N Z. And subscribe.
Learn more about UiPath Queues
If you’d like to go beyond this UiPath Queues, visit the UiPath Forum.