@Mani BharghavI am not aware of a public system that you can use. I know many years back the University of Michigan Library made theirs accessible, but I am not sure if that is still the case. The best advice I can give is that it really is pretty easy to understand once you get access to a system to test with. Essentially, you just need to remember a few things. The first is that this adapter is backwards from the others. This means that you don't start it until the application is up and running. The second is that this adapter (at its simplest) is really just text on a screen at a specific location in the string. When you match a screen, you do so by text being at a specific place. A Partial screen can be an area that appears on every screen (or most anyway) or a repeating section that appears on one screen (like a list or grid). I have not encountered many of the former use cases, but the latter comes in handy frequently.

Here are a few tips;

1. To locate the DLL to use, I like to use Process Explorer to look at the DLLs loaded into the emulator. Find the "HLLAPI" one and place that in the text adapter property after you've setup the short session name in your emulator.
2. The NewScreenShowing event is a powerful one to wait for as it fires whenever the screen changes in some way. This is helpful when you are navigating between a screen and a results screen where you might either encounter the current screen or a new one.
3. You can nest partial screens inside of each other. You do this because you want one to contain the repeating section of the screen (usually rows). The outer one does not repeat while the inner one does. You would use the key of None to refer to the outer screen.
   1. You might use this trick when your match region for a partial screen is ambiguous outside of the area where the partial screens are. Maybe all you have is a regex date for example and the same format occurs elsewhere on screen.
4. I prefer to define partial screens as an entire row of the screen if possible. It just makes it easier to conceptualize.
5. When defining a partial screen, immediately identify the match region, or you may need to start over.
6. I have seen some emulators that had their fields defined in different positions from where they were actually located. I prefer to fill out the field in its entirety before I define it, so I can be sure it is accurate (i.e. use all characters in the field until you can't enter any more). If it is inaccurate, I would define a region at the actual location and length.
7. You don't really need to use fields unless they can become disabled, and you need to check that in your automation. There are other reasons too, but this is the most common obvious benefit.
8. There is usually a reset key that you use to back out or fix an error in your data entry. Users will know what it is. It is typically Escape. When you need to send this key, send Reset instead of Escape.