Solution Design
What Solution Design covers
Solution Design is the discipline of turning a business process definition into a Blue Prism solution that is maintainable, testable, and safe to operate. A candidate must understand the layered model: process layers (the top-level process, sub-processes, and reusable object layers), the distinction between a Process (a diagram of stages that orchestrates work) and a Business Object (a reusable action library that talks to an application), and the role of Work Queues as the durable record of units of work. Also understand session variables, environment variables, credentials, and how a solution is packaged into a release for import into another environment.
Key concepts to name confidently: the process/object boundary, page and stage types, exception handling strategy at the solution level, data retention and audit, and the choice between queue-driven and case-driven designs. Design decisions should be justified by non-functional requirements such as throughput, recoverability, and segregation of duties.
Traps in questions
Watch for options that put business logic inside an object, embed credentials in data items, or rely on a single long-running process page instead of a queue. Questions often present a "simplest" option that fails on recovery: if the machine dies mid-run, only a queue item with a defined status survives cleanly. Another trap is confusing a reusable object with a sub-process: reuse across processes belongs in objects or shared process layers, not copy-paste.
Rule of thumb
If the same unit of work must be retried, audited, or distributed across resources, it belongs in a Work Queue. If the same interaction with an application is needed by two processes, it belongs in an object. Everything else is orchestration in the process layer.