Sample work · AI & Automation
GUI Automation: Entering orders into a legacy application without an interface
An operating robot enters orders from a CSV file into a legacy application via the user interface. It recognizes dialogs and errors, waits when the database is locked, and resumes after a crash without duplicate data entry.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Entries via application windows without access to its database
- Dialogs such as a locked database or mandatory field errors are recognized and handled
- Progress is tracked; after a crash, a reconciliation is performed instead of duplicate entry
Download auftraege-beispiel.csv
For permitted workflows only: with the software owner's consent and without bypassing security locks. If the user interface changes, the robot requires maintenance.
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Legacy application (tkinter, separate process, no API) with login, customer search, mandatory field form, 'database busy'/validation error dialogs, slow saving, and a crash after the 12th commit. 30 CSV orders via the user interface (pywinauto win32
Limits
What this sample does not cover, so nobody expects more:
- Permitted workflows only: Operating robot only with the software owner's consent or when the license allows automated operation; no bypassing of CAPTCHAs, login blocks, or other …
- UI changes break the robot: it knows mask titles, tab order, F keys, and dialog titles; an update to the legacy application requires maintenance. The only thing intercepted is that it notices …
- Tk applications (like this one) have no accessibility interface: field contents are not readable for the robot, posted mouse clicks do not work. Checks are therefore performed via the text of the …
- Keyboard messages are sent directly to the windows (no SendInput, no focus stealing). Some programs read keys only via the actual keyboard state (Ctrl/Alt combinations, DirectInput …)
- No duplicate entry depends on a reconciliation option in the UI (here, document search by external document). If the legacy application has no search by a unique identifier, after a …
- Screenshots via PrintWindow work even with obscured windows, but not when minimized and not after a crash (then only log line)
- One robot, one application instance, one Windows session; locked screen or logged-out session stops it. Throughput here approx. 1 record per second (incl. slow saving)
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.