Screenshot Automation Plan

Analysis date: 2026-03-09

Executive Summary

The documentation has 325 old-style image references still using numbered filenames (e.g., configuration-guide-image84.png), plus 27 <!-- robot: TODO --> markers in 11 files indicating screenshots that need automation. The existing robot-manifest.json has 264 entries (256 automatable, 8 marked not-automatable). This report categorizes the remaining ~159 un-automated screenshots and identifies which can be added to the robot manifest.

Current Robot Manifest State

Not-Automatable Entries (in manifest)

Manifest Entries by Guide

<!-- robot: TODO --> Markers (27 total, 11 files)

These are screenshots in the markdown files that have placeholder markers but no manifest entry yet.

Category Breakdown

Third-Party (16) -- Cannot be automated

These show external application UIs (Azure Portal, Duo Admin, OneLogin, JAMF, Okta) that are outside xAssets and cannot be captured by the robot.

Automatable (8) -- Can be added to robot-manifest.json

These show xAssets screens reachable through normal navigation.

Note: Items 1-6 are data-dependent -- they show multi-step software title creation workflow. The manifest entries already exist for some of these with simple ClickMenu steps, but the TODO markers suggest the actual screenshots have not been captured yet. Items 3-6 require specific demo data (a software title being created step-by-step) to look right and are more accurately categorized as data-dependent.

Manual Only (3) -- Cannot be reliably automated

WS8 Categorization: Remaining 325 Old-Image References

From the earlier WS8 analysis (BusClassNET04/claude-reports/ws8-screenshot-categorization.md), the 325 remaining old-image references break down as:

Consolidated Automation Potential

Combining the TODO markers with the WS8 old-image analysis:

The 26 Automatable Screenshots (not yet in manifest)

These are from the WS8 "Capturable by Robot" list plus the TODO marker items that are genuinely automatable:

Note: Items 17-21 and 23 require the Help Desk module to be enabled (settings toggle) and items 23, 26 are manual-only, reducing the truly automatable count to approximately 22.

Recommendations

Priority 1: Quick Wins (high ROI)

1. Update 58 MD references that already have new equivalents -- script-assisted find/replace
2. Add ~22 simple navigation entries to robot-manifest.json -- straightforward ClickMenu/PrintScreen patterns

Priority 2: Medium Effort

3. Enable Help Desk module in test environment and capture 6 Service Desk screenshots
4. Create demo data setup script (AMSX) to populate test data for the 111 data-dependent screenshots
5. Break data-dependent screenshots into batches by workflow (transformation editor, query editor, financial workflows, etc.)

Priority 3: Ongoing Maintenance

6. Third-party screenshots (57) should be manually verified annually -- SSO provider UIs change independently
7. Icon/fragment images (97) should be gradually replaced with CSS-styled equivalents or Unicode symbols

Estimated Impact

• Current robot coverage: 264 / (264 + 325) = 45% of all documentation screenshots
• After Priority 1: 264 + 22 = 286 automatable, 58 refs updated = significant visual improvement
• After Priority 2: 286 + ~80 data-dependent = ~366 automatable = 62% coverage
• Maximum theoretical: ~430 / 589 = 73% (excluding third-party, icons, and manual-only)