UiPath Computer Vision (CV) Activities
CV Activities use AI-based visual recognition to automate UI elements that standard selectors cannot reliably target.
- CV Screen Scope — the container activity that enables CV-based automation in a target window/Citrix session
- CV Click, CV Type, CV Get Text — CV counterparts to standard UI automation activities
- CV Anchor — using a stable nearby element to locate a dynamic target element
- CV Check App State — visual confirmation of UI state in Citrix environments
- CV Extract Table — extracting grid/table data from Citrix screens
- CV activity timeout configuration — handling slow Citrix rendering delays
Citrix Automation Strategy
Citrix automation requires a fundamentally different approach than standard Windows or browser automation.
- Why Citrix is hard — no native accessibility APIs, all interaction via pixel/image/Citrix extension
- Citrix Extension for UiPath — required installation for Citrix Receiver/Workspace automation
- UiPath Citrix tech support — direct Citrix component (requires Citrix extension vs CV as fallback)
- CV for Citrix — pure visual recognition without Citrix extension requirement
- Anchor selectors in Citrix — using relative element positioning for fragile screens
- Healthcare use case — Epic Hyperspace running inside Citrix, standard selectors unavailable
Image-Based Selectors and Anchors
When neither standard selectors nor CV Activities are available, image-based automation provides a fallback.
- Find Image activity — locating UI elements using screenshot pattern matching
- Click Image — clicking based on image recognition rather than selector
- Image accuracy settings — adjusting accuracy threshold to balance reliability vs speed
- Anchor elements — using a stable element as positional reference for dynamic targets
- Screen coordinate fragility — why absolute coordinates fail across screen resolutions
- Resolution-aware automation — designing for multiple screen sizes and DPI settings
Dynamic Selectors
Dynamic selectors handle UI elements whose attributes change at runtime.
- Wildcard selectors — using * in attribute values for partially dynamic attributes
- Variable selectors — building selector strings programmatically from runtime values
- Selector Editor — UiPath Studio tool for inspecting and modifying selector attributes
- UiExplorer — deep selector inspection and attribute analysis tool
- Selector stability testing — verifying selectors across multiple runs and data scenarios
- Fallback strategies — when to escalate from selector to image/CV for dynamic UI
Fallback and Recovery Strategies
Production-grade Citrix and CV automation requires robust fallback and recovery logic.
- CV primary + selector fallback — try selector first, fall back to CV on failure
- Image recognition + CV hybrid — layered approach for maximum reliability
- Check App State with CV — validating expected visual state before proceeding
- Retry Scope with CV activities — automatic retry for Citrix rendering delays
- Screenshot-based diagnostics — capturing CV failure screenshots for production analysis
- Healthcare screen automation safety — extra validation steps for Epic screens before committing data
Frequently Asked Questions
What UiPath Citrix automation and CV support do you provide?
We provide real-time support for Citrix automation strategy, CV Activities configuration, Citrix Extension setup, image-based automation, dynamic selector design, anchor selector patterns, Check App State with CV, and Retry Scope for Citrix stability. Citrix and CV automation are common interview topics and we also provide proxy interview guidance.
How do you automate Epic Hyperspace running inside Citrix?
Epic Hyperspace in Citrix requires either the Citrix Extension for native component interaction, or Computer Vision activities for pure visual automation. We help design stable automation for Epic screens using CV Anchor patterns, Check App State validation, and retry logic — while ensuring automation safety for patient data interactions.
Why do my Citrix selectors keep failing in production?
Common Citrix selector failures include: screen resolution differences between dev and production, Citrix session rendering delays, session reconnection events, Epic application version updates changing UI attributes. We diagnose the root cause and implement stable CV-based or anchor-based alternatives.
How do I handle dynamic selectors in UiPath?
Dynamic selectors use wildcard (*) characters for variable attribute portions, or build the selector string programmatically using variables. We help identify which selector attributes are stable vs dynamic, implement the right wildcard strategy, and add validation to confirm the correct element was found.
Ready to get real-time expert support?
Same-day start. Confidential. All major time zones covered.