An Ftscript consists of activities. Each activity has a context. The context may also describe error handling mechanisms (faulthandler).
Activities may take the form of instructions issued to openFT (e.g. transferFile, deleteFile) or instructions which control the workflow (e.g. parallel, foreach). The instructions are described in chapter “openFT-Script statements”.
Files, directories, scripts and partners can be stored as context objects in the context. By means of referencing, it is possible to re-use this type of context object in the activity and the underlying activities provided that these do not possess a context object with the same name. Re-use is not possible outside of the activity in which the context object is defined.
If a fault occurs within an activity then error handling can be used to supply an appropriate response. If error handling terminates correctly (i.e. without errors) then the associated activity is considered to have been completed successfully. Similarly, if error handling is terminated with an error then the activity is considered to be defective.
The general structure of an Ftscript is as follows:
<ftscript version="1">
<context>
ContextObjects*
faulthandler?
</context>
Activities+
</ftscript>
Every Ftscript has the statement <ftscript version="1"> as its root element.The root element contains the following sub-elements:
an (optional) context with context objects and a maximum of one faulthandler
one or more activities which are executed in the specified sequence
For further information on the syntax, see section “Syntax of the openFT-Script statements”.