Export a report when it is ready.

1. Define the dates and expected output

The example screen shows Northstar Reports, a fictional app with Start date, End date and Generate report controls. Its sample dataset covers 1–7 September 2026, with dates entered as YYYY-MM-DD.

Choose a small known date range and identify the file, rows and totals you expect. In your own application, confirm the download location and whether a save dialog needs to be handled.

2. Enter the range in the correct fields

Use Wait For Window to identify the report application. Target and focus Start date, replace its existing value and type the required date. Repeat for End date, then select Generate report.

Check that the displayed inputs are correct before proceeding. Use Window Click for a stable field position inside the window, or a tested image or text target where that better suits the interface.

3. Wait for the report, then locate Export CSV

The example app changes from Generating report to Report ready and reveals Export CSV. Capture the enabled export button as a distinctive template and set a search region that includes its possible positions.

As shown in the video, add Wait For Image with the Export CSV template, a 10,000 ms timeout and Stop Workflow on timeout. Follow it with Image Click using the same template and a 2,000 ms timeout. The separate wait allows report generation to finish before the click step. These are the example settings: validate suitable timeouts and failure handling in your own application. The recording demonstrates the successful run; test the missing-button case separately.

4. Verify the file, not just the click

Check the application’s export status and the actual output. A message saying Download requested does not prove that a file was saved. In the local example setup, Saved locally identifies a saved export; the browser-only path requests a download that still needs to be checked.

For your workflow, choose the available file or on-screen checks and validate them against the expected date range, rows and totals. Do not describe the task as complete until the output has been confirmed. This written guide does not provide a prevalidated workflow package.

5. Test the conditions that can change

Use harmless sample data and a single export while setting up these cases.

• Increase generation time and confirm that the workflow waits for the expected state.
• Move Export CSV within the search region and confirm that only the correct button is clicked.
• Suppress the button and verify the configured timeout outcome.
• Enter an invalid date range and confirm the error path.
• Check the saved file for the expected period and contents, including any duplicate downloads.
• Revalidate display scale, focus and file location in the actual application before repeating the task.