Question 1
A developer is building a process that interacts with a legacy desktop application. During testing, the 'Type Into' activity occasionally fails because the application's input fields are slow to become active after a window appears. The current implementation uses a fixed 'DelayAfter' property, which is proving unreliable. Which approach provides the most robust solution to ensure the input field is ready before typing?
Answer and explanation
Correct answer: C
The 'Check App State' activity is specifically designed for UI synchronization. It can be configured to wait until a specific UI element appears, disappears, or meets a certain condition (like being enabled) before executing activities within its target-found block. This is more dynamic and reliable than a fixed delay or a simple timeout on the target activity itself. A 'Retry Scope' would re-attempt the entire action, but it doesn't solve the underlying timing issue gracefully.