The steps in this topic include in the appropriate places a reference and a link to each of the five issues described in the preceding topic, Part 1. Preparations for flow recording).
For the steps in recording a screen operations file see Recording a screen operations file.
To make a flow recording:
For more information about both of these options see a) Provide screen descriptions in the topic Part 1. Preparations for flow recording.
Open the host editor if it is not already open (see Opening a host connection).
Verify that the session is connected (see Connecting with a host system).
Verify that the host editor is in flow mode (see Screen operations mode and flow mode).
If you plan to use any existing screen descriptions, then load
the most recent versions of your screen descriptions by clicking the Reload
Screen Descriptions icon
(see Currently loaded
screen descriptions).
.If necessary, edit the characteristics of the working flow (see b) Edit the working flow in Part 1. Preparations for flow recording).
If you have not already done so, verify that the current working set includes the screen operations files that you want to use (see c) Select the working set of screen operations files and Using a working set).
Navigate through the host application to the application screen at which you want to start recording.
Click the Start Recording Flow icon
to
start recording.
If the current host application screen is unrecognized, and you have not selected the check box Automatically capture new screens in the Service Flow Projects preferences window (see Providing screen descriptions for recording) then the host editor opens the Screen Not Recognized window.
If the Screen Not Recognized window opens, then follow the steps described in the subtopic 1. Unrecognized screen before recording begins.
If the working flow already contains a recorded flow path, then the host editor prompts you with either one or two additional windows (see e) Add to the flow path or record a new flow path):
Do you want to add to the working flow '<flow_name>'?
Select "No" to create a new flow.
If you clicked Yes in the preceding window, then the host editor next displays the Record Path Into Existing Flow window, which contains the following two options:
Select this option if you want to record a sequence of nodes that is not connected to any flow node in the flow path (see Disconnected paths) .
If you selected this option, then follow these steps:
to the
already existing Invoke screen operation node that
you selected.If you want, you can now create Extract actions that extract data from the already existing Invoke screen operation node. These Extract actions are associated with the new output terminal that the host editor added to the existing Invoke screen operation node.
If you are creating a new flow, then the Progress Information window opens for a few seconds, then closes. This window indicates that the host editor is preparing to launch the New Flow Recording wizard.
The New Flow Recording wizard opens. On the first (and only) page of the New Flow Recording wizard, enter the following information:
Into this input field type the name that you want to use for the new flow that you are about to record. When you complete the recording and save the new flow, the new flow is stored into a file having the name that you specify here plus the extension .seqflow (for example, MainFlow_0001.seqflow).
In the Interface Resources group:
Click one of the following options:
Create all new resources
Click this option if you want to create all new resources and name them using the default names.
Reuse one or more resources
Click this option if you want to select one or more existing resources or if you want to create one or more new resources with a name other than the default name. The resources are:
Interface Operation
The interface operations file and the interface operation for the flow (see Basic information about operations).
Input message
The input message file and the input message for the flow (see The input message of a flow).
Output message
The output message file and the output message for the flow (see The output message of a flow).
Variable message
The variable message file and the variable message for the flow (see The variable message of a flow).
Automatically expose insert and extract variables in the interface operation messages
Select this check box if you want the host editor during flow recording to automatically add to a flow's input message or output message a message element corresponding to the variable that you select for a new Extract action or Insert action (see Updating an interface message with a variable from Extract or Insert).
In the Terminal Resources group:
Into this input field type the name of the screen operations file that you want to use as the working screen operations file during flow recording.
During flow recording, as you navigate through the terminal application, then your keyboard input is recorded into the currently loaded screen operations file (see Recording a screen operations file).
Also during flow recording, if a screen operation in the file matches the currently recognized screen description, then you can play back a screen interaction from that screen operation (see Finding screen interactions for the current application screen).
After flow recording is completed, when you save the flow, the screen operations in the currently loaded screen operations file are saved to the screen operations file on the workstation's hard disk (see Saving a flow).