INFO: In Navigation between screen [FromScreen] and screen [ToScreen], Alternate Screen [AlternateScreenForSameEnterKey] has no direct navigation to [ToScreen]. [AlternateScreenForSameEnterKey] will be treated as an Exception Screen. |
When analyzing all navigation within the set of recordings connected to the active project, the code generation framework identifies alternate screens for a particular action. A typical example is a screen that says "CUSTOMER NOT FOUND" and assumes that the Enter key will be pressed to return to the prior screen. In a Web Service transaction trying to get to a Customer Details screen, this is an Exception Screen since there is no way to continue with the current request.
If you have such a screen displayed in a recording and you have not set its NavigationType=Exception, you will see this message. If you see this message for a screen that is not an exception, but more like an informational screen, you may need to record a successful transition from the keyscreen->informational->results (details) screen. If such a navigation exists in any recordings, the generation framework should pick it up, but if by any chance you started a recording and stopped when the informational screen appeared, the framework has no way to know that the enter key will get from the informational screen to the results screen.
