@DarrellE This is where you would define a region. A region in a text adapter is basically the screen characters from position X through length Y. In your automation, you can then get the text of the region and parse it the same way (looking for your success message or whatever).

A basic overview of the text adapter;

Basically, you define each screen by identifying a match region (text on the screen at a specific position that you use to identify it). Once you have a screen defined, you can identify fields, regions, or partial screens. A field is defined by the emulator and are usually the areas where you are able to type into. Think of these like text boxes. You can retrieve and set their text properties as well as determine if they are enabled or not. A region is an area on the screen that you want to identify. Think of this like a label. You can retrieve its text and if it is defined in the exact coordinates that the emulator lets you type, you can also set its text. A partial screen is an area of the screen (usually one that would contain other regions or fields) that you want to repeat in some way. A partial screen has a match region that you define as well.

One common trick I like to do with the text adapter (if this works with your emulator), is to wait for the NewScreenShowing (NSS) event at the emulator level. This is especially helpful when you have a scenario like you've described where you are submitting some data and returning to the same screen. The NSS event will fire when the screen has been refreshed.

Hopefully this helps. Let me know though if you have any questions.