Chapter Two, blue prism essentials. In this chapter, we'll be talking about process diagrams, process studio, object studio and application modeler. process diagrams. robotics process automation tool. Blue prism, creates business process workflows, called process diagrams. This is how a process diagram looks like.

So these diagrams are corollary to flowcharts we use in designing and analyzing business processes of any IoT project. However, these diagrams in blue prism are not simply two dimensional graphical representation of operations. They act as software programs, utilizing the core programming concepts and creates the operational process flow for us. Thus, it's a program in graphical form, making it easier for RPA developers to create comprehend, analyze, modify, and scale up business capabilities. So, we have like these stages is what we call them and we drag and drop them into the panel and we create the workflows. Right?

A quick fact that blue prism RP tool is based on Java programming language. Thus, it inherits all its capabilities, and inbuilt functionalities, making it easier to establish and implement a program logic. process to do process diagrams are created in the area within blue prism called process to do this is what the process studio looks like. It looks pretty similar to any diagramming and vector graphics application available in market today, like Ms. Visio, gliffy, lucid chart etc. A process studio comprises of following bars or tools bars. First is the menu bar.

Let's maximize this for a second. So menu bar same as other applications, Windows applications, it includes options like File, Edit, View, to debug and help and all these stuff. Right These provide drop down menus to have capabilities like you know, saving a file are selecting all the stages in one go some finding and to making some changes to the stages or some application functionalities, cetera, et cetera. Okay, next is the standard toolbar. This is the toolbar right below the menu bar right with icons like save or print or to zoom or to refresh and all those stuff. These provide like several computing options like these and can come very handy when you are working on the entire program at once.

Next, is the format toolbar. This toolbar is generally available to the right of this standard toolbar. And here, you can set some formatting options like making the content bold, italics, underlined, or you know, setting some font name with all the application with all the stages within the application that you have used, you can use these formatting options. Next, is the control or we also call it the debug toolbar. So this toolbar has the buttons to play or to like go or to resume, or to stop a work, a process flow that's being worked upon or being executed right now. And these like also provides capabilities to reset to step into a program or step over a program and to debug it like right now, it may have like some syntactical errors, those can be viewed right away through this toolbar.

Next is the stage panel. So, stage panel, all these stages are included in this stage panel. And these stages are the ones that constitutes the actual process, right all these stages are dragged and dropped here, and this through this stage panel and we create the process flow accordingly. The last is the process flow designer or the main panel, this is the panel where we get the stages from the stage panel. And we create our entire logic of of the process that needs to be executed the bot right. So, each process diagram is created in the process to do pages.

The first most page of every process to do is the main page. We can create many subsequent pages by simply right clicking and creating the new page and we can put the page number According to the New page will be added. And it helps in keeping the overall program the diagram neat, tidy and manageable. Also, when you are creating a process, it's always a highly recommended practice to give comprehensible names to the stages. So that you know, during debugging or if some one else is looking at your project that your work, they should be able to comprehend and make meaningful, you know, information take meaningful information out of the process that you have created. Right.

A quick thing to note is that main pages executed first and all subsequent pages with the process to do or referenced through it. We refer to those pages using this page stage. And we put that in the workflow and once the process execute this stage, it gets redirected to the page which it is redirect which is referencing to the stages referencing. Okay. objects to do. All IT operations require intercommunication with external applications.

The interactions with these target applications doesn't take place in process to do, but rather in a separate area called objects to do. Let's see where our objects to do resides. This is how our blue prism application looks like. And go here and all the objects in here are indeed objects to itself. Let's open one. Object studio contains business objects which are nothing but the diagrammatical programs interacting with applications and performing actions.

On them. One business object provides interfacing with only one external application. Note, a business object is only used by process flows to be leveraged for automation. Each business object has two pages by default, initialized and cleaned up. We can add as many pages to a video as we want, like we already have launched a name in here. But that depends on the different capabilities that we intend to equip our bot with.

These pages can directly be accessed through the corresponding process flow diagram. That is, Business Objects don't follow the same hierarchy like main page, page one, page two, and so on. All the pages within the Beals are at the same level and can be accessed independently by the process flows. Application modular application module is the functionality to create application models within objects to do application model exposes the UI elements of a target application to blue prism program. Let's see where it resides. This is where the application model is.

And here are like the different UI elements that we have used. And here are these attributes corresponding to those UI elements. So the elements are identified and selected by the user. And with the use of stages, you can perform different operations on those UI elements. And there are different interfacing modes based on the type of application or program needs to interact with. We can show them in once we are working on the new business object.

Let's see how that works. It's always a good practice to give a description as well. As you can see the initialize and cleanup for the initial features that are provided to us by default. And this one doesn't even have start and the end once connected stages. And once we click on the application moderate first and foremost asks for the application that it needs to interact with the executable file or attaching the window to an already existing application or something like that. So, these are the different modes, which are provided.

The first is the Windows application, which interfaces with Microsoft Windows based applications. It makes use of interfaces to interact with application windows Utilizing VB six PowerBuilder, Microsoft foundation class, the MFC library, and the dotnet framework. Next is the Java application. This interfaces with applications utilizing Java applets, swings and other technologies based on Java programming platform. Next is the browser based application. It interfaces with applications utilizing HTML, JavaScript and other browser based technologies and mainframe application interfaces with mainframe applications through terminal emulators