Rational Developer for System z, Version 7.6

Screen interaction

A screen interaction is a sequence of actions that is performed to process a particular application screen. The default name of an screen interaction is of the form Screen Interaction n, where n is an integer, for example Screen Interaction 0, Screen Interaction 1, Screen Interaction 2, and so on. You can assign a different name.
For example, suppose that you are recording a screen operations file (either by itself or at the same time that you are recording a flow) and you perform certain activities for a particular application screen. In the following table, the first column shows the activities that you perform, the second column shows the individual action that the host editor records for each activity, and the third column shows the screen interaction that the host editor creates to contain and identify this sequence of actions:
Table 1. Building a screen interaction
Activity performed for a particular application screen: Action that the host editor records: Screen interaction that the host editor creates to contain and identify the actions:
You type "ainq" into a field. Input action ("ainq")
Screen interaction
You type "1" into the next field. Input action ("1")
You press the Enter key. AID key action (Enter)

If during screen operations recording or flow recording you visit the same application screen more than once, but perform the same activities at each visit, then on the second and subsequent visits the host editor (recognizing that a screen interaction containing this exact sequence of activities has already been created for this application screen) does not create additional, duplicate screen interactions.

In contrast, if during a screen operations recording or a flow recording you visit an application screen several times and perform different activities at each visit (for example, the application screen might be a menu, and you might select a different menu option at each visit), then the host editor creates a different screen interaction (Screen Interaction 1, Screen Interaction 2, and so forth) for each visit.

Note: Although each screen interaction is assigned a default name when it is created, such as "Screen Interaction 0", you should assign a more meaningful and memorable name to each screen interaction that you intend to use in a flow recording. Then, when you are doing the flow recording and the host editor allows you to select from a list of screen interactions a single screen interaction that is going to be used to process the current application screen, you can look at the name of each screen interaction in the list and hopefully remember from the name what actions the screen interaction performs.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)