PA009
Mandate API or object-property-based bot integration over screen-coordinate targeting to prevent silent failure on interface changes.
CyberTRIZ analysis · Process contradiction PA009 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Greater Process Coverage by RPA vs. Lower Screen-Change Fragility
Business Context. Extending RPA coverage to more applications increases the surface area exposed to screen and interface changes, each of which can silently break automated workflows that rely on fixed visual or field references.
Process TRIZ Resolution. Rather than relying on brittle screen coordinates, organizations should build bots using resilient identification methods, such as underlying object properties or application programming interfaces where available, reducing sensitivity to visual changes.
Applicable TRIZ Principles
Principle 28 (Mechanics Substitution) replaces fragile screen-coordinate targeting with more resilient identification methods.
Principle 11 (Beforehand Cushioning) anticipates interface changes by building in tolerance for minor visual variation.
Principle 5 (Merging) combines API-based integration with RPA where APIs are available, reducing reliance on the interface entirely.
Expected Outcome
Broader coverage sustained
Lower fragility to interface changes
Fewer unplanned bot failures
Reduced emergency maintenance
Decision Indicators
Bots frequently fail after routine application updates.
Screen-coordinate-based automation dominates the automation portfolio.
Available APIs are not used in favor of screen automation.
Failures are discovered only after significant downstream impact.
No resilience testing occurs before deploying new bots.
If several of these indicators are present, the contradiction is likely active and the Process TRIZ resolution above should be evaluated.