Pass Your Blue Prism AD01 Exam Easy!

Blue Prism AD01 Blue Prism Developer exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Blue Prism AD01 Blue Prism Developer exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Blue Prism AD01 certification exam dumps & Blue Prism AD01 practice test questions in vce format.

Exam Prep

5. IsStopRequested

All right, let's take a quick break and review everything we just went over for debugging. The first two buttons are step over and step out. The first step in the process will always proceed to the next stage in the process one at a time. If there is a subpage or subprocess, it will actually go into that page and execute the rest of the stages one at a time. Next up, you have Step Over, where if you click on that, it will also run this process one stage at a time. The difference is that if it comes across any pages or subprocessors, it will run them all automatically and proceed to the next stage in your current page. Finally, we have stepped out. If you're in a subpage or subprocess, it will run the rest of the stages until the end of that page and then go back to the parent page you were in to continue running the process by clicking on one of the Step buttons again or the Run button. Then you have Breakpoint, whereby if you right-click on any stage in a process and select Breakpoint, it will highlight it in a red box, and then if you're on the process at that stage, it will immediately break and stop. So you can continue debugging the process either one step at a time or by hitting a Run button to run it to the very end. Finally, if you go to the Debug menu and select the Break on Exceptions option when you're on a process, if it encounters any errors or acceptance at all, it will immediately break and pause the process for further debugging by you. And finally, a few useful bits of info Remember, within an exception, if you click to reserve the type and detail of the current exception, it will retain the internal blueprints exception and hold on to that. or if there's any other exception below it, it will hold onto that to throw back to you to debug later on. Looking at the screenshot here, keep all your recovery stages in blocks. That way, if an error occurs, it will immediately jump to the stage, and then you can go on to your exception or you can try and recover from it. Finally, always have a resume stage if your exception will retry the same logic. Otherwise, Blueproofing will throw an error. It can only hold one exception at a time. So if you look at this page of bad processing down here, you can see it's going to retry up to three times, and we have this resume stage when we're trying to retry in our normal processing. The recommended retry accounts are Three and Blue Prism. And finally, try to ensure all your exceptions bubble up to the main page. So if I throw an exception in this bad process, the main page here has a bad process, and it's contained in a block, which can then recover and then throw an exception. If we wanted to, we could try to recover by relaunching the entire programme and rerunning everything. It's a recommended way to handle exceptions. in a blue prism.

6. IsStopRequested Cheatsheet

Next up is the "is stop requested" function. What this does is check if a safe stop has been requested in the current session. If you're not too short, that is, don't worry, I'm about to take you through it now. So I've got an empty process. Here what we're going to do we're going to drag adecision stage to the end we're going to call it stopand underneath functions in environment you'll see this is stop requestedso drag that into the expression this is going to returntrue or false and basically what it means if you're runninga process in the background in a queue and let's justsay it's processing 100 orders and for some reason you're atorder 60 and you want the process to stop you wantto make sure you safely stop it. Close down the application. Finish off the current order you're processing, and the way you can do that is by using an ESOP requested function, and what this does is it will check if you have requested a safe stop of the process; if you have, it will then execute that path of the safe stop; otherwise, it will continue executing the process. So let's hit OK, and what we're going to do is drag some anchors onto our process, and we're going to simply let the process run forever until we request a stop. So let's drag and connect this all together so that we simply have an infinite loop. Four stop swap that around switch so that if it's yes, that means a safe stop has been requested and we can do any cleanup and the process; otherwise, keep running this process forever. So what we need to do is double click on the process information on the main page. We need to publish this process to the control room Because this stop request can only be made from the Blue PrismControl room, let's go there now. So go to Blue Prism, let's go to the control room, and you can see we have this as a stop request. To run this, simply drag it from the control room under set management into your desktop computer, the CME desktop, and see what happens. That's going to add it to the queue as "pending" to run this process; all we need to do is hit "start" to run that, and when we request stop, that's when your stop requested will be set to true and it will finish the process. So if we hit "start," we can see this is running; we double-click on it. We can see the logs; we only have one stage, which is "stop," which is always false because we haven't stopped the process. So we can see this process will keep running until we right-click and hit "request stop," at which point it's completed, and we can see if we open it up here. Remember, we have that decision-stage stop. When we right-click and hit "Stop this process," it says, "Hey, you, the stop requested is true." Let's stop this process. So that's how you can safely stop a process in the Blue Prism queue, and from the process in the exam, they might ask you, "Hey, you're processing an order 61 out of 100, and you want to stop the process." How do we safely clean up and stop the process? Just remember the requested function.

7. Environment and Session Variables

Alright, so just a quick review. a stop request. It will safely stop a blueprint process. It is triggered when you are running a process in the queue and you right-click and select "Is Stop Requested?" When a process receives a stop request, it will complete the current item you are reprocessing and perform the clear cleanup activities. Say you're processing Order 61 out of 100 orders. It will make sure it finishes processing that order and is safe. Close down the application you're running and the process.

8. Environment and Session Variables Cheatsheet

Alright, the next two items we are going to look at are environment variables and session variables. The first are environmental factors. This is found in the system under process environment variables and what they mean. So you have a website link, say, www.oracystem.com, and you have two separate versions. One is a test version, which is a test environment, and one is production, where actual real data is being used. Obviously, if you make a process and migrate it from test to production, you don't want to be modifying the process. So instead, what you can do to change this is create environment variables. So let's create one here. We're going to name this ordering system URL. We'll have the typetext and call it the description. The orderingsystem URL value will www dot orderingsystem.com." Once you've done that, hit Apply. And this is going to create an environment variable in the current loop. With them set up to use this, we're going to go home to the studio. I've got this environment and session variables empty, so I'm starting a new one. And what we'll do is drag a data item, double-click on that, and from exposure, select environment. So what that will allow you to do is, if you drop down this name, you can select any of the environment variables you have created, and once we select it, it sets the value here. You can't actually change it because it's a read-only variable. So we can see that we have our ordersystem.com chest here. Assume we have another blueprint serviceset up and have migrated this processover to production. We can change this environment's URL to ordersystem.comproduction, and that will actually change it in our process, wherever we're actually reading this from. So we could then use the URL to load up the ordering system, website, place some orders, and so on. So the key factor to keep in mind is that you create them in a system tab, you can change them at any time, and you can have two different instances of blueprints set up where the values will be different for a test system and a production system. Next up is session variables. Let's drag a data item onto here and do the exposure as session data type will do a number, and we'll do 100. and we're going to call this loop count. What this allows us to do is similar to what istop requested if we can actually change this variable's value while the process is being run. So let's hit okay, and let's actually create a decision stage for another data item that we will call the current loop. We're going to set this other type of number as the initial value. We're going to create a decision here. So what we're going to do is if the current loop is greater than or equal to the loop count, we're going to end this process. So current is greater than the loop count for the name hit. Okay, we'll connect that to the end. And then what we're going to do is add a calculation under here called increment loop count—current loop plus one—added on to that store in the current loop. And then what we're going to do, we'regoing to drag an action onto here. And I've got a custom action set up, which you can actually download in this lecture or in this course. What it is is called "Wait." And we have an action in here called "Wait Five." And this is just going to take 5 seconds. The reason I'm creating that is to show you a demonstration of this. Otherwise, Blueprint runs way too far sometimes, and you can't actually see what session variables actually do easily. So what it's going to do is it's simply goingto keep on looping over until we hit 100. So if we go to the start, let's speed it up a bit. Wait 5 seconds after pressing the run button. The current loop is two. It's going to go around, and it's going to keep on incrementing. Its current loop is three, and so on. And that's going to run until it hits a hundred.But what we can do with the session variable is actually change this loop count to something different while the process is running in the control room. So let's stop that now. And just quickly before we head back to the control room, make sure we select to publish this process to the control room. Let's save that process. Now let's go to the control room. You can see that we've got our environment and session variables. Let's drag that over to CMU's desktop. We'll see if it is pending. So click on this "Show Shift and Variables" button. Let's start this And we can see it's running. And now we can see our loop count here, which is 100. So if we double click on this, we can see it's running through loops two, three, and so on. And it's going to run until it hits 100 loops. But what if we want to change that to ten while the process is running? Simply right-click Edit value, edit this to ten, click Modify, and we go back to our running process. We can see the loop counter at ten. We double click on that, go to the logs, and we can see we're up to eight. Now let's close that down and give it a few more seconds. And let's see that actually finish atloop count of ten instead of 100. So we can see that's been completed. So if we double click and go to our logs, we can see we go up to loop count ten. This current "more than loop" account is true. and we finish our process. So you can actually change your data items while the process is running in the control room by exposing them as a session variable. And you might want to do that in scenarios where you want to only process 100 orders at a time. But you decide, Hey, we don't have enough time to process 100 because we have another process that wants to run. We can only process 50 in a given time frame. So use a session variable. Then you can control it in the actual control studio and change it on the fly.

9. Process Flow Decision

Okay, so just a quick recap. Environment variables are used to differentiate settings between environments. For example, test versus production One example is its ordering system environment. The URL for the test environment is "ordering system." The comtest username is test, the password is test, but in production, the URL is the ordering system. login username is "admin," and the password is "super secure password." This way, if we set it up as an environment variable and we migrate the process from test to production, it will automatically use the production environment variables, and we don't have to manually update the process every time we migrate it. So super useful. Finally, the session variables and a data item can be changed from the control room while the process is actually running. Remember our example of a loop count, which was done by going to the control room, selecting the running process, using the show session variables, and then right clicking and editing it? So we changed our loop count from 100 to our process. Instead of running 100 times, we edited it to only run ten times. So this is used for situations where you might have a long-running process and say you only want to process 100 orders at a time, but you have another process you really need to run urgently. So instead, you tell it to run only ten orders. So the next process can run straight after it. But you're still able to process orders without stopping the process manually. It will just run through until it hits that limit.

Go to testing centre with ease on our mind when you use Blue Prism AD01 vce exam dumps, practice test questions and answers. Blue Prism AD01 Blue Prism Developer certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Blue Prism AD01 exam dumps & practice test questions and answers vce from ExamCollection.