The process we are not rewriting is still a 3270 conversation

One process is becoming a service. The process next to it is still a 3270 conversation we will keep for now. How do channels call that one?

Automate it as a terminal Screens Flow in [[product:ol-integration|OL Integration]]: identify screens, send AID keys, map fields, and branch on the screen you actually get. That is a live session method, not a map ScreenFlow and not a replatform. AtomIQ can draft that flow from COBOL and BMS when you want the analysis first. Keep this flow only for the process you have chosen to leave on the screen.