Prior to executing this code generation template, the following tasks need to have been performed:
1.Recordings made of the relevant screen navigations
2.Field maps made of the data that is to be returned.
3.Fields involved in navigation must have the NavigationUse extension property set. Note that any text entered into a screen that is not in a field map is assumed to be a literal to be "plugged-in" during the web service execution. Therefore, it is best to map all fields on your screens involved in the web service generator. Note that the default NavigationUse is "Ignore" so this can be left "as-is" for all data fields.
NavigationUse meaning: KeyVariable means that the value is to be derived from variable data passed into the web service. For each KeyVariable identified, a parameter will be declared on the Details method of the web service. literal means that any value used in a recording should be "poked" as literal text into the screen during navigation. Static menu screens are typical uses for the literal NavigationUse (the menu option entry field). By identifying a field as a NavigationUse=literal, you avoid needing to include this as a parameter in the Details screen.
Note- any UserID and Password fields on a Signon screen must have the KeyVariable NavigationUse property...
4.Screens also have a navigation setting that can assist in the generation of Navigation logic. The NavigationType setting for screens should be set to Exception for any screens that are error screens which require changes to the entered data prior to proceeding.
