After you process forms in the program, you want FORMS to transfer data from those forms to an outside system, either by saving it to a file or by sending it to the outside system via a DLL or VBA function.
Most often, a Transfer job writes data record by record (that is, form by form) to a file. (You choose the file name in the Transfer job description, not in the transaction description.) The text below is a simple way to symbolize it.
Data from form 1
Data from form 2
Data from form 3
Data from form 4
Data from form 5
Data from form 6
...
You specify the contents, layout and format of the data in the standard transaction description.
Then, you save the transaction description with the form definition.
Every form definition must have a standard transaction description. The exception is form definitions that are to be used only in sets with questionnaire set logic for which you have defined a set transaction description.
There is no need to mention standard transaction descriptions in the Transfer job, even though the Transfer job is where they are used, because they are automatically linked to form or set definitions specified in the Transfer job.
Creating a new standard transaction description