Blue Prism Solution Designer study guide
Blue Prism Solution Designer · Work through your exam, one topic at a time.
The Blue Prism Certified Solution Designer credential is aimed at automation professionals who move beyond building individual processes and take responsibility for the shape, structure and quality of a whole Blue Prism solution. Typical candidates already understand how processes, objects, work queues and exception handling fit together, and now want to show they can architect a solution that is maintainable, testable and governable across its lifecycle. The Blue Prism Solution Designer study guide has 5 sections and about 1,566 words.
01Solution Design
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.
326 words, about 2 min02Process Design
Process Design is about structuring the process diagram itself: the main page, sub-pages, stage types, decision logic, loops, and exception blocks. Candidates must know the standard stage set - Start, End, Action, Decision, Calculation, Multi-Calculation, Choice, Note, Block, Collection, Loop, Page, Read, Write, Navigate, Code, Exception, Recover, Resume, Anchor - and when each is appropriate.
353 words, about 2 min03Object Design
Business Objects encapsulate application interaction. Candidates must understand object layers (the object, its pages, and actions), the distinction between action stages exposed to processes and internal sub-pages, and the conventions for naming and parameter design.
292 words, about 1 min04Solution Delivery
Solution Delivery covers the lifecycle from build to production: packaging a release, moving it between environments (development, test, production), and operating it. Candidates must understand release packages , versioning, the contents of a release (processes, objects, queues, credentials references, environment variables), and the import/export process.
303 words, about 2 min05Governance and Control
Governance is how an organisation keeps its automation estate safe, auditable, and aligned to business risk. Candidates must understand role-based access control (roles and permissions for designers, controllers, and administrators), the audit trail of changes, and the separation of duties between build and release approval.
292 words, about 1 min