In this section, the process for coupling an EASAP to underlying software applications to be run in a batch mode will be discussed in detail. This process involves three main steps:
In addition, other actions, such as sending an email message, communicating with databases and Excel spreadsheets or managing files, will be presented.
This section contains a few examples of typical scenarios in which you will need to manipulate user inputs. In these examples, you will see how data processing objects can be put to use to achieve the desired data manipulation.
EASA drives software applications in their batch mode. Therefore, pre-existing batch input files must be available for an EASAP to work, and these files may need to be modified by an author to work properly with an EASAP. Batch input files only need to be modified if they contain settings or commands that are affected or dependent on user inputs.
The Processes branch features some of the same objects found in other branches, namely Data Processing Actions and Event Processing Actions.
The final step in coupling an EASAP to underlying software applications after manipulating user inputs and creating template batch files is to actually run the software applications using the appropriate commands.