Extract screen text: Full Text, Native, and OCR scrapers, font formatting, and hidden text extraction.
Traditional / Ad-Hoc Approach
Manual human clicks, brittle unmanaged scripts, zero centralized control, and missing fault tolerance.
Enterprise UiPath Standard
Production-grade execution, dynamic Unified Target selectors, automated retry recovery, and centralized governance.
Screen Scraping extracts text from UI elements using three distinct scraping engines: Full Text (extracts all text including hidden), Native (captures visible text with formatting), and OCR (optical character recognition). Key Sub-topics Breakdown: • Subtopic 1: 3 Text Scraping Engines: Full Text (fastest), Native (coordinates/formatting), and OCR (rasterized images) • Subtopic 2: Speed vs Accuracy Trade-offs: Extracting hidden text, font positions, and text bounding coordinates • Subtopic 3: Screen Scraper Wizard: Interactive inspection of legacy Win32, Java, and terminal application screens In enterprise automation environments, Output / Screen Scraping guarantees reliable execution within the UiPath ecosystem. Key Sub-topics Breakdown: 1. 3 Text Scraping Engines: Full Text (fastest), Native (coordinates/formatting), and OCR (rasterized images) 2. Speed vs Accuracy Trade-offs: Extracting hidden text, font positions, and text bounding coordinates 3. Screen Scraper Wizard: Interactive inspection of legacy Win32, Java, and terminal application screens
Choosing the correct scraper ensures 100% text accuracy and enables reading text that human eyes cannot see (hidden DOM attributes).
Full Text reads directly from the API/DOM tree. Native captures Windows GDI text rendering. OCR uses computer vision to decipher pixel shapes.
Zero unmanaged credentials, explicit timeout ceilings, and structured audit logging.
This enterprise architecture diagram illustrates the execution lifecycle and component boundaries for Output / Screen Scraping:
ENTERPRISE AUTOMATION PIPELINE (Output / Screen Scraping):
┌────────────────────────────────────────────────────────────────────────┐
│ Design & Governance Plane: UiPath Studio & Orchestrator │
│ • Packages (.nupkg) • Modern Folders • Credential Assets / Queues │
└───────────────────────────────────┬────────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────────────────┐
│ Execution Plane: UiPath Robot (Attended / Unattended Agents) │
│ ┌───────────────────────────────────┐ ┌────────────────────────────┐ │
│ │ UI Automation (Simulate / Chromium)│ │ Data & API Processing │ │
│ │ Unified Target & Object Repo │ │ LINQ / HTTP Web Requests │ │
│ └───────────────────────────────────┘ └────────────────────────────┘ │
└───────────────────────────────────┬────────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────────────────┐
│ Enterprise Exception Handling & Telemetry Sinks │
│ • REFramework States • Try-Catch / Global Handler • Audit Logs │
└────────────────────────────────────────────────────────────────────────┘At a global enterprise handling over 75,000 monthly transactions, operational teams implemented Output / Screen Scraping to resolve critical production bottlenecks:
Manual intervention caused processing delays and human error in mission-critical transactions.
Deployed Output / Screen Scraping with automated retry rules, dynamic error recovery, and end-to-end audit logging.
Eliminated 98% of manual touchpoints, achieved sub-second execution latency, and maintained 99.9% uptime.
Evaluate the trade-offs, performance SLAs, and production constraints when deploying Output / Screen Scraping: