Exam Prep

10. Process Flow Decision Cheatsheet

Next up is process flow and decision stages. We've already covered the decision stages quite a lot. So I'm just going to cover the inputs and outputs to our page and the multiple stage, just in case you're not familiar with it and what to look out for in the exam. The first one is that we're going to create a new page and what this is going to do is to get an answer promise from a number. So just do this as you get the answer and press the finish button. Now let's go over to that get an answer page. I'm going to lay it out as per the standard template I use, which is going left to right and the blocks. This template is not in the exam, but it's just something I like to use when developing my processes. It keeps it nice and neat and gives a bit more real estate. Now I've got to start and end here. So what I want to do is take a number, either one, two, or three, and output the text, which will be yes, no, or maybe. And if it's not one of those numbers,we're going to output the text error. So what we'll do first of all, in the beginning, we're going to add an input. We're going to name this input "selection number." It's going to be of the data type number and hit that erase icon to store it in an input here. Then what we're going to do is we're going to use the achoice stage and, depending on what your selection number is, we're going to set some text either yes, no, or maybe. So do this as set selection text. So what we're going to do is we're going to add in a selection number equals zero for no. The number zero. The selection text should be "no." This selection number is equal to one. Then it's going to be yes. And finally, if the selection number is two, this is going to be maybe. And in the exam, they'll actually try to andtrick you here by making the formula incorrect or making some look slightly similar. So keep an eye out for that in the exam. And then what you'll notice here is that we now have this selection text and these little purple diamonds on that. So what happens with a multi choice?The first diamond represents the first option in this list. The second one represents the second option, which is yes. The third is for the navy, and so on. So what we're going to do is we'll add a calculation stage, call it set selection text. Yes. And what we're going to do is we're going to store results in selection text and we're just going to simply score the text in the quotation marks. So this one will be the second choice. So connect this up to the middle one here. So this is yes. Remember, copy and paste that calculation stage. We'll do one for set selection text to no set the expression for no. Hit okay. Do one more for maybe. The expression will be "maybe." Hit okay. Then connect maybe up, then no up. So that is going to store that in the selection text data item. So make sure you create that data item with a little eraser icon. And then let's just line this up so it looks a bit nicer, neater. And then what we'll do is we'll add an anchor, we'll connect all these up, and that's going to go onto the end stage. Otherwise, if you don't provide a number which is zero, one, or two, we're going to throw a custom exception to the user. We'll do it all the same type of business exception. So we'll create a newexception type exception in detail. You have input the wrong number. Please use zero one or two. Hit OK. Then connect the start stage to our process. Let's save that just to make sure I've got the changes and let's just run over it. So we've got this starting input as a selection number. It's going to go through the set selection text. If it's zero, it's going to set the selection text data item to no. If it's one, it will set it to yes. If it's still set to "Maybe." Otherwise, we'll make an exception. And at the end, we're going to add an output called selection text. Call this a data type for text. We'll get the value from the selection text. So drag that on there, hit OK. Now what happens if we go to our main page and we have Getano? We can put the input as, say, selection number one,the output selection text, hit that eraser icon, hit OK to create that data item on this page. And now we have all of that logic contained within that single get answer page. So if we run through our process now and see if selection number one sets a text to yes, we'll pass that back as an output to our data item. And I've missed building selection texts, so let's just tidy that up. selection text, copy that, make sure we update our page input page output and I'll also update that get answer.So just keep an eye out for that because there will be typos in a bulletproof exam and they will actually test you on that. So this is the main thing to keep in mind: pages or processes can have inputs and outputs. So you can make a page for a particular function that might be used several times. If you don't have a true false decision from a normal decision page, you can use a choice page, which will have multiple results when you add each row in there. The first row will correspond to the first diamond here, the second one to the second diamond, and the third one to the third diamond. If none of them match, it will go to this other stage where you can either choose to throw an exception if it's an invalid option, or it might be a valid option and you continue processing. So just keep these features in mind when you're tackling the exam because they will ask you about them. And it's just important to remember the order that these diamonds come in and also make sure that all this looks correctly. Any example So we'll try and trick you with that.

11. Wait Stages

So just recap in on the process flow decisionmaking steps and Blue Prism. Remember the decision stage is simply true or false. You probably know this one off by heart. The next one that's not used so much is the atoy stage With this, you're able to add as many decisions as you want for a choice. Remember, the dotswill indicate the first dot is in the first row. The second dot is in the second row. So when you drag a connected stage out of it, it will actually sortof text for the description of that row. The choice is that if none of them match, it will go to the otherwise stage. So you want to make sure you have something coming up there to handle the scenario when a selection isn't what you expected or doesn't match any of them. Finally, the page stage will go to another page in the process. The key fact to remember is that you can have input and output data items into pages and objectsfor the existing, so keep an eye out for that.

12. Wait Stages Cheatsheet

Alright, time to take a quick look at the wait stages. So I've got this application model here, which you can download in a lecture on this course. It's just for Notepad, whereby if we launch the Notepad application, we've got Notepad here, and we've also got an element for the input area. So if we highlight like that, simply enter that input area here. So one of the questions I'll ask is if Notepad isn't launched yet and we want to write some text to it, how do we wait for the right time to actually write text to it while it's loading up? The obvious solution is to wait for the stages. We can set up a waiting stage here. We can wait for 5 seconds. Then we can connect our right stage and call it right to notes pad. We simply add in the input area the element and value as hello. Connect that up, and we're done. Right, super simple. Just wait 5 seconds and then it will be right. But what happens if it doesn't load? What if the application is having a bad day and Notepad takes 10 seconds to load instead? For example, Plus, you want to optimise if Notepad is already open. You don't want to be waiting for 5 seconds when you could be writing text to it. Because that does cost money in blueprint licencing time, you might have already noticed. But there's a simple way around this. If we open up the properties, we can actually wait for the input area to load if we drag it on for a condition. There are multiple conditions here. We can check if it exists, we can check the window attribute, or get the window text. So we simply need to check if it exists. If true, and it does exist, then it will move on to the next stage, and it will wait up to 5 seconds until it's there. So we can say 10 seconds instead. Hit okay. And now you'll notice you have this little circle dot between the wait stage. Now what you want to do is connect that up to write to Notepad. Then at the timeout, you want to connect up exception because that means it didn't load in time. And any exception, we'll do that as a system exception, and we'll call it the detailed Notes Pad did not load in time. Hit okay. And now what happens? We've got a notepad open here. When I run this application from the start, This object, it's immediately going to write to Notepad, so we can see here Hello Rode, Instantly, it didn't need to wait an arbitrary number of seconds because of what this waste stage will do. It will wait to see if Notepad exists. If it does, boom. Moves straight to the notepad on the right. So in Notepad, what we've done now is just go to the menu, and if we go to the right to Notepadagain, let's try and write to it and see what happens. Because the open menu is open, we can't actually access the input area. It's going to go up to 10 seconds,and then it's going to throw an exception. Because it's timed out, there's Our custom acceptance note pad did not load in time for the change of messaging around that. But this is a recommended method for the wait stage in Blueprsm. You wait to check if a window exists. Then you take your actions. You don't wait for only 5 seconds. You set a timeout value. might be 5 seconds. might be 10 seconds. Once the time is up, you throw an exception. That way, you immediately move onto the next stage. That way, your process runs as fast as possible.

13. Retrying as per Blue Prism template

So just a recap on wait stages: always use the element action check to exist within a timeout before moving on to the next step. So you can actually check. If that element does exist, you immediately move on to the next stage. Which is right to note that you do not use an arbitrary notepad timeout to wait. If an application loads and if the application elementcheck fails, you always want to find an exception. So this is a pattern recommended by Blue Prism. It's an absolutely great pattern. It's absolutely invaluable. So just remember this when you're usingwaiting stages and if you encounter any questions, questions on them during the exam.

14. Knowledge of the Blue Prism templates

Alright, it's time to briefly touch on some Blue Prism documentation, mainly around exception handling and the retry. The good thing is we've already covered a lot of this, so it's just showing you what the expected Blue Prism template is because they might ask you questions around any example. So it's good to know how you should retire when you encounter exceptions. So the main one to look at is the subpage exception handling. It's in the process of a basic instruction template. Download it in this course or get the latest one on the Blueprint website. And the gist of this is, if there is any sort of error, you go into recover, go to retry. You can retry up to three times if you keep getting exceptions over the retry limit of free.That's when you throw an exception here. And Blue Prism has kindly enough,actually provided an example process. So you can also download this. So this is the example here. And this is the first step in the process. It's recommended that you throw an exception within a page, you preserve the type and details of the current exception. What that will do is bubbleup to this main page here. So I've got work step one, work step two, work step three, and so on. If any of these is an exception, they'll go into recovery mode or capture the details of the exception, so we can see the exception type, the exception detail, it will resume and it will mark this item as an exception. So that way, if you're processing 100 orders and for some reason, ten of them have issues with data quality and they throw exceptions, you can mark those ten items as exceptions for later manual review, where the rest will be completed. So the key facts are the retry limit of three is recommended unless you need it set. Otherwise, if it goes over that, you throw an exception, which will go back to the main page and mark that item as an exception. Otherwise, if it's successful, mark it as completed. So I won't run over this one, but it will be attached and you can review it yourself in the document.

ExamSnap's Blue Prism AD01 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Blue Prism AD01 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.