Rational Developer for System z

Comparison of results: Flow recording and screen operations recording

Creating an Extract action or an Insert action during flow recording creates additional artifacts beyond those created for these two actions during screen operations recording.
You can create an Extract action or an Insert action in two contexts:
Note: Also, you can create or modify an Insert action manually in the screen operations editor (see Adding an action).

If you create an Extract action or an Insert action during screen operations recording and you want to use the Extract action or the Insert action in a flow, then after you have completed the screen operations recording you must create a mapping for the action by playing back the screen interaction containing the Extract action or Insert action during a flow recording (see If you select a screen interaction).

The reason is that while screen operations recording creates only the Extract action or the Insert action in the screen operation for the current application screen, flow recording also configures a variable to be used with the action and creates a mapping that describes how the Extract action or Insert action is to be implemented. The variable is stored in the variable message file for the flow. The mapping is stored in a mapping routine that is associated with a terminal of the Invoke screen operations node for the current application screen (see Mapping routines in terminal flows).


Feedback