Solutions Handovers
Legacy system bridge
Work moving into a system that has no API, driven the way a person would drive it, without a person doing it.
01 / What it looks like running
Start to finish, and where a person still comes in.
01 / Trigger Record approved upstream
02 / Automated Queued for the desktop robot
03 / Automated Screens driven the way a person drives them
04 / Automated Result read back and confirmed
05 / Automated Failures reported with a screenshot of where it stopped
06 / Needs a person Anything the old system asks that nobody anticipated
Automated Needs a person 4 of 6 run without anyone
02 / What stops happening
6 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Someone opens the old system
- They re-key what was already approved elsewhere
- They tab through screens in a fixed order they memorised
- A typo goes in and is found weeks later
- They confirm it saved by looking
- The cases the old system was never taught to handle
03 / Built on
In your tenant, under your licences.
- Power Automate Desktop
- Power Automate
- SharePoint
Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.
Does yours run like this?
It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.