Process Design and Build
Start from the process definition, not the canvas
Blue Prism development begins with a documented, atomised process definition. Before building, a candidate should understand the distinction between a Process (the orchestrating artefact that lives in Process Studio) and a Business Object (a reusable, application-specific component in Object Studio). Design decisions hinge on this split: anything that touches an application interface belongs in an object; anything that encodes business rules, routing, or human work queues belongs in the process.
Core building blocks
Know the standard stages and when each is appropriate: Start/End, Action, Decision, Calculation, Data Item, Collection, Loop, Choice, Multi-Calculation, Block, Note, Anchor, Exception, Recover, Resume, and Page. Understand Page as the unit of modularity and Block as the unit of encapsulation and reuse. A common design trap is a monolithic main page; good design decomposes work into named pages with clear entry and exit conditions.
Data modelling
Understand data types (Text, Number, Date, DateTime, Time, Flag, Binary, Password), initial values, and the difference between a Data Item (single value) and a Collection (tabular, with defined fields and a key). Be able to explain when a Collection beats a set of data items, and how Collection fields are typed and filtered.
Traps to watch for
Questions often test whether you place recovery logic at the right level, whether you confuse a Decision stage with a Choice stage, and whether you understand that process design must be testable page by page. Another frequent trap: assuming the process should own application logic that belongs in an object.
Rule of thumb
If a page cannot be described in one sentence with a clear input and output, it is doing too much. Split it before you build it.