Automate a defined interactive task
Robot Replay is an enquiry for automating interactive work in the Robot portfolio. Consider it where a stable operational task still depends on a person following prompts. The task must first be understood well enough to describe its inputs, expected screens, completion evidence and exceptions.
A replay design differs from a conventional batch command because a changed prompt, unexpected message or revised application layout may alter the interaction. Begin with a bounded task that the application owner authorises for unattended operation. Keep credentials and business data out of demonstration recordings unless their handling has been approved.
Test prompts, interruptions and evidence of completion
Record the normal path and deliberately introduce supported exception cases in a test environment. Check what happens when required input is absent, the application is unavailable or the expected completion message does not appear. Avoid treating a finished replay session as proof that the business transaction succeeded.
Acceptance should connect the replay outcome to an application-level result that an operator can verify. Agree who updates the automation after an application release and who handles an interrupted session. MMC can help scope the selected task and handover procedure; custom application changes and continuous operation should remain explicit items in the proposal.
Evidence to request for this scope
- Confirm current Robot Replay availability, supported interfaces and application constraints before ordering.
- Demonstrate one normal interaction and an unexpected prompt without using production transactions.
- Retain the application validation, exception instructions and owner responsible for maintaining the replay.