Recall that an action is stored inside a screen interaction, which is in turn stored inside a screen operation, which is stored into a screen operations file (see The screen operations file and its subcomponents).
and enter the required
information the host editor creates an Insert action.
and enter the required
information the host editor creates an Extract action.When you use the first method -- flow recording -- to create actions, the host editor creates for each new action one or more mappings that describe how the operation that is specified in the action is to be performed (see How actions are implemented in mappings: AID key, Input, Extract, and Insert). If the action is an Extract action or an Insert action, then the host editor also prompts you for the name of a variable to be used in the mapping.
(During flow recording, all the actions that are created during one encounter with an application screen are stored into a single screen interaction, which is stored into a screen operation. The mappings generated from each action are stored into a mapping routine that is associated with an Assign node or with an input terminal or an output terminal of an Invoke screen operation node. After the flow recording is complete, when you save the recorded flow, the screen operations are stored into a screen operations file and the mapping routines are stored into the primary mapping file for the flow.)
In contrast, when you use the second method (screen operations recording) or the third method (the screen operations editor) to create actions, then the actions are created the same as in flow recording, but the mappings are not created (see Comparison of results: Flow recording and screen operations recording).
To create the necessary mappings for a set of actions that you created for a particular application screen using the second or third method, you must associate the screen interaction containing the new actions with the appropriate screen description during flow recording, by playing back the new screen interaction when you reach the particular application screen and the host editor recognizes the appropriate screen description.
Also, if the screen interaction contains any Extract action or Insert actions, then for each Extract action or Insert action the host editor will prompt you for a variable to be used in the mapping for the action (see Recording Extract actions and Insert actions during screen operations recording).