Let’s discuss about the most asked blue prism interview questions and answers
The role of a VBO is to act as an adapter to the user interface of a specific application. To accomplish this,each VBO has three main parts:
As their name suggests, actions implement the logic of a business object. As Figure 6 shows, each action contains a
set of stages along with data items holding information used by that action.
An action can be published, which lets it be called by processes and potentially other software. An action can also
remain private, making it available only to other actions in this business object. Whichever option is chosen, the
action begins with a Start stage and finishes with an End stage, as as below image shows.In between appear whatever
stages are required to carry out the tasks this action performs.
Since Blue Prism accesses applications through their user interfaces, a Blue Prism process acts much like a human user. Just as a person might interact with several applications to carry out a series of business steps, a Blue Prism process can invoke operations in several VBOs to carry out those same steps.
In some ways, a Blue Prism process is quite similar to a VBO. Like a VBO, a process is defined in one or more pages, and each page contains some number of stages and data items. There are important differences, however. The biggest one is the way in which pages can be invoked. In a VBO, any published page can be called at any time; the object exposes a set of operations that can be invoked in any order. A Blue Prism process, however, always begins at its Main page, and the pages it contains always execute in a defined order
To create a process, a business analyst or developer uses Process Studio. Just as processes are similar to business objects, Process Studio is similar to Object Studio
A process defined in Process Studio looks much like a traditional flowchart. As in Object Studio, each page in a process has its own tab, letting the analyst divide the process into logical groupings. Also like Object Studio, Process Studio allows its user to create logic graphically by assembling stages on a design surface. The tool includes a built-in debugger that allows stepping through a process, setting breakpoints, examining data items, and more.
One of the challenges in working with business processes is changing them safely. To help with this, Process Studio keeps track of the previous version of a process being edited. The user of the tool is then able to switch to a view that shows both the old and new versions side-by-side, letting her see exactly what’s different. Blue Prism also provides a process history tool that allows tracking revisions to processes over time.
Just like manual processes, automated processes need to be controlled and managed. To allow this, Blue
Prism provides two tools: Control Room and System Manager.
The purpose of Control Room is to let both business analysts and IT staff work with Blue Prism processes.
The tool lets them perform tasks such as:
Any application intended for enterprise deployment must squarely address security, and Blue Prism is no
exception. One important foundation for security in the product is role-based access control. Once a Blue
Prism administrator has defined what roles a user can act in, the system will allow that user to perform
only the actions allowed by these roles.
Blue Prism also keeps track of significant changes to its environment. Using the Audit Log Viewer, part of
System Manager, an administrator can examine records of things such as when a user logs into Blue
Prism, when that user starts or deletes a process, when that user changes her password, and more.
Another issue, especially for a technology based on presentation integration, is safely storing and
managing the user names and passwords used to log in to applications. To do this, Blue Prism provides an
encrypted credentials database controlled by a Blue Prism administrator. For example, a set of credentials
(i.e., a user name and password) might be usable only by specific Blue Prism processes started by users in
specific roles and running on specific servers. It’s also possible to use Active Directory in place of some
parts of Blue Prism’s user management mechanisms. While it’s not required, larger organizations in
particular can find this useful.
The connector’s job is to handle low-level interaction with an application’s user interface. Since
application interfaces use a variety of technologies, Blue Prism provides a variety of connector choices.
The options are:
Even in our digital era, many business processes are still carried out by people. Yet these processes commonly rely
on one or more applications, with human beings providing the driving intelligence. For example, think about a back
office that handles customer orders. Each order might require getting a customer’s name, then looking up and
validating the customer’s shipping address. Once this information is available, the next steps might be to calculate
the shipping cost and place the order. In a typical back office environment, people execute this process, often
relying on multiple applications to complete it.
But why? Just as more and more manufacturing processes are now done by robots, why can’t more and more
business processes be done by software robots? The answer is that with RPA, they can. Put simply, RPA means
using software rather than people to carry out business processes that rely on applications. Figure 1 illustrates this
As the figure shows, RPA allows replacing people with software robots. While this kind of automation can be useful
when a process uses just one application, it’s especially valuable when a process relies on multiple applications, as
in the example shown here. Rather than integrating the applications through whatever application programming interfaces (APIs) they might expose, RPA instead accesses each one through its user interface, just as a person
UiPath and Blue Prism both the tools have their respective software/Studio and they are very good. UI and BP both have visual process designers for developing the solutions.
In terms of programming languages:
In terms of Control Room/Dashboard
In terms of cost and uses: