Blue Prism RPA Fundamentals
What the fundamentals cover
Blue Prism separates the design environment (Process Studio and Object Studio) from the runtime environment (Control Room and the interactive clients). A Process is the orchestrating diagram that drives business logic and talks to the work queue; an Object is a reusable business object that exposes Actions and encapsulates application interaction. Objects are published to a shared repository so many processes can call the same Action.
Understand the anatomy of a diagram: Start and End stages, the main page, sub-pages for reusable logic, and the stage categories (Action, Decision, Calculation, Multi-Calculation, Data, Collection, Loop, Block, Exception, Recover, Resume, Anchor, Note, Choice). Know the difference between a Collection (an in-memory table) and a Data Item (a single typed value), and between session variables and environment variables.
Traps in questions
- Confusing Process with Object: only Objects model applications and expose Actions; Processes call them.
- Assuming a stage can have unlimited outgoing links - a Decision has one or two, and a Choice has many but needs a clear default.
- Believing environment variables are per-session; they are central and shared, unlike session variables.
- Mixing up Digital Worker (the runtime identity) with the Resource (the machine plus login) it runs on.
Rule of thumb
If logic will be reused against an application, or needs to survive a change of screen, it belongs in an Object Action; if it is orchestration, retry, or queue handling, it belongs in the Process. Keep the Process thin and the Objects deep.
Worked example
A candidate is asked where to place a login routine used by four processes. Answer: publish a single Action on the relevant Object and call it from each Process - duplicating the login in four Processes breaks the reuse principle and multiplies maintenance.