Object Studio and Application Integration (Spying, Web, Citrix, APIs)
Spying modes and application types
Object Studio wraps a single application. You must know the application types (Windows application, Web, Java, mainframe/terminal, Citrix/virtualised) and the spy modes: Win32, Accessibility, UIA, HTML, Region, and Active Accessibility. Match the mode to the technology: HTML mode for browser DOM elements, UIA for modern Windows apps, Region mode for anything that exposes no accessible elements (often Citrix).
Attributes and element stability
Spied elements carry attributes; robust automation matches on stable attributes and avoids volatile ones (dynamic IDs, coordinates). Prefer element paths that survive layout changes. Understand the difference between attaching to an already-open application versus launching a new one, and why you should always detach/close cleanly.
Web and Citrix specifics
For web, know that HTML mode reads the DOM and is generally preferred over surface/region automation; wait-for-element patterns beat fixed sleeps. For Citrix and other virtualised environments, elements are pixels - you rely on Region mode, image matching, keyboard navigation, and surface automation; text may need OCR or clipboard tricks. These are slower and more brittle, so design for generous waits and explicit verification.
APIs
For API integration, Blue Prism typically uses a Web Services or HTTP-based object: you build the request (endpoint, method, headers, body), send it, and parse the response (often JSON or XML) into a collection or data items. Know that authentication tokens and endpoints belong in environment variables, and that response parsing needs defensive handling for missing fields.
Traps
Questions love the 'which spy mode' decision and the assumption that Citrix exposes DOM elements (it does not). Another trap: hard-coded sleeps instead of wait stages, and matching on dynamic element IDs.
Rule of thumb
Spy the most structured layer available; fall back to region/surface only when nothing else works.