Recall that during flow recording the host editor creates for each new action that is created one or more mappings that describe how the operation that is specified in the action is to be performed (see Overview of creating an action).
The mapping or mappings that are generated for each of the four actions are described below. You can see and edit these mappings if you open the primary mapping file for a terminal flow and view the appropriate mapping routine.
"Fields" data structure: A mapping for an Input action, an Extract action, or an Insert action uses a message element that contains subelements corresponding to all the fields in the particular application screen for which the action was created. There is a subelement for every field in the application screen (whether the field is used in the mapping or not) and each subelement has the name (the custom name if any, otherwise the default name) of the field that the subelement corresponds to: Field2, Field 136, Field162, and so on.
The mapping routine that contains these two mappings is associated with the input terminal of the Invoke screen operations node that corresponds to the application screen where the input occurred during flow recording (see Implementation of Extract actions and Insert actions).
b) Input action:
These mappings are located in the same mapping routine that contains the mappings for the AID key (see AID key action).
c) Extract action:
This mapping is located in the mapping routine associated with the output terminal of the preceding Invoke screen operation node or Assign node (see Implementation of Extract actions and Insert actions).
d) Insert action:
This mapping is located in the same mapping routine that contains the mappings for the AID key and Input action (see AID key action).