customer Prototyping

Just give me the assessment result

Type what you need; get the upload-ready file - no mainframe knowledge required.

A business or technical-management user who owns an outcome

The trigger. “I need the software/hardware assessment input for our renewal discussion. Produce the scan file I can upload.”

The old way

They cannot do it themselves. They file a request and wait on a sysprog, who runs the full relay. Version drift lands hardest here. If the toolkit is back-level, the business user has no way to diagnose it. A silent failure becomes a guaranteed support ticket and a stall of several days on a business conversation that has a deadline.

The Flow way

On the generate screen they type the goal. Flow assembles the Environmental/Capacity scan flow and runs it end-to-end on Play, returning the upload-ready file.

The toolkit is fetched and pinned automatically, so the back-level trap that would have stranded a non-technical user cannot fire. If a run does fail, it fails visibly and immediately. It is never silent, and it does not surface weeks later.

Payoff

Old wayFlow way
Who can run itSysprog onlyThe business user, self-service
Time to resultRequest, queue, daysPrompt, Play, minutes
Version driftWorst case: undiagnosableCan’t happen quietly