Blue Prism Developer study plan

Map the Blue Prism process lifecycle from process definition through object layering, and label where each design artifact belongs

Draft a page-and-stage hierarchy for a two-application process using main pages, sub-pages, and reusable object calls

Define naming, versioning, and folder conventions for a small process and apply them to a skeleton

Identify the decision points that belong in Process Studio versus Object Studio and justify each placement in writing

Build a multi-page process in Process Studio using decision, choice, loop, and calculation stages correctly

Wire process and object inputs and outputs with explicit data types and default values

Configure a work queue with key fields, priorities, and deferred item handling

Refactor a duplicated block of logic into a reusable sub-page and verify behavior is unchanged

Build an object in Object Studio with separate pages for launch, login, navigate, read, and close

Apply spying modes appropriately for a browser and a desktop application, and document which mode fits which element

Use wait stages and attribute checks instead of fixed delays wherever possible

Trace a run stage by stage and correct at least three defects found through stepping and breakpoints

Design an object interface contract listing actions, inputs, outputs, and expected exceptions

Implement a read action that returns a typed collection and a write action that confirms success

Handle a multi-window or multi-tab application by attaching to the correct target consistently

Test each action in isolation using a manual test harness before calling it from a process

Classify exceptions as business, system, or recoverable, and route each to the correct handling block

Implement a recover-and-resume block around a fragile application step and a retry with a bounded attempt count

Write meaningful exception detail into work queue items so failures can be diagnosed later

Define a case-level exception strategy that decides between retry, mark exception, and terminate

Configure a process for Control Room scheduling, including triggers, session limits, and resource targeting

Explain how work queues behave under multiple concurrent sessions and identify contention risks

Set up logging, audit, and environment variables so a process runs across two environments without code changes

Draft a release checklist covering package import, credential handling, and rollback

Apply design best practices to remove hard-coded values, deep nesting, and hidden dependencies in an existing build

Introduce a reusable utility object for common actions such as logging, file handling, and data conversion

Review an object for spying fragility and replace at least two brittle element matches with stabler attributes

Produce a peer-review checklist that another developer could apply to your build

Complete a timed end-to-end build from a written requirement without referring to notes

Diagnose and fix three injected faults in a supplied process using stepping, breakpoints, and logs

Answer scenario questions on session management, exception escalation, and governance controls

Consolidate weak areas from earlier weeks into a personal revision sheet