User Tools

Site Tools


Fundamentals of the PROCESSES branch

DATA PROCESSING ACTIONS

The DATA PROCESSING ACTIONS are the PROCESSES equivalent of similar ACTIONS on under an EVENT PROCESSING elsewhere on the Tree.

  • a DATA PROCESSING ACTION may
    • set an explicit SCALAR to control logic of another PROCESSES branch object
    • conditionally extract information from a file
    • generate timestamps during the submission process

DATABASE ACTION

A read or write to a database is done via a PROCESSES→DATABASE ACTION

DATABASE ACTION is a Parent to DATABASE, which in turn is a Parent to READ and WRITE


Excel Objects

As introduced in Interacting with an Excel spreadsheet, an EASAP can interact with Microsoft Excel spreadsheets within the USER INTERFACE branch via a Cell Reference in data entry objects or via an ACTION within an EVENT PROCESSING. In the PROCESSES branch, only the ACTION approach is available. In this case interaction happens on the EASA Server during a batch EASAP submission rather than the user’s client computer during an interactive user interface session.

Changes made to an Excel spreadsheet using interactions located in the USER INTERFACE branch will not be available to the ACTIONS located in the PROCESSES branch at the time of submission. The ACTION's in the PROCESSESS branch are always applied to the original uploaded version of the spreadsheet file. Therefore, the two approaches are NOT currently designed to be used in combination.

  • The process of making EASAP's interact with Excel spreadsheets in the PROCESSES branch involves two basic steps,
    1. Defining connections to the spreadsheets from the workbook files on down to the various worksheets
    2. Performing Excel specific actions using EXCEL ACTION's found on the PROCESSES branch

PROCESSES branch objects

PROCESSES branch
CLEAR EXCEL RANGEclear values in cells or NAMED RANGES
CUSTOM PROCESS ACTIONexecute custom written Java code
DATA PROCESSINGParent for DATA PROCESSING tools
DATA PROCESSING ACTIONSParent object for other ACTION's
DATEallow the current date and/or time to be stored in an explicit SCALAR
EXTRACTextract data from a file
SET LISTset an explicit LIST
SET SCALARset an explicit SCALAR
DATABASE ACTIONperform a one time action on a DATABASE
DATABASEdefine the database on which to perform the action
 CLOSE CONNECTIONafter a READ/WRITE sequence
close the database connection
READexecute a SELECT statement in SQL
WRITEexecute an INSERT, UPDATE or DELETE 
EMAILsend an email message to Users
EXCEL ACTION GROUP Parent to an abitrary sequence of Excel-related ACTION's.
EXPORT TO PDFcreate a snapshot of a specified spreadsheet range as a PDF document and saves it on the file system
FILE MANAGEMENTminimize disk usage in EASA
IMAGE EXCEL ACTIONextract a screen capture of cell range or chart in an Excel spreadsheet for display by an IMAGE in a DIAGRAM
PROCESSrun an underlying software application
CLEAR FILESPACEminimize the disk space used by files generated from an EASAP run
DATA PROCESSINGParent object for DATA PROCESSING tools
FAILED IFdefine conditions for which the EASAP run is deemed to have failed
MONITORmonitor the progress of a process currently submitted to the EASAP queue
REPLACEMENTsearch a file for all delimited object references and replaces them with the appropriate object values
READ EXCEL ACTIONread values from specified cell ranges in Excel spreadsheets into specified LIST's
RUN MACRO ACTIONexecute a macro in an Excel spreadsheet
STOPdefine a complete mechanism for stopping the EASAP
STOP PROCESSdefine a method to stop a PROCESS
WRITE EXCEL ACTIONwrite values from one or more LIST's into specified cell ranges in Excel spreadsheets.

Order of Operation within the PROCESSES branch

  • the order of execution within a PROCESS object is always
    1. DATA PROCESSING objects
    2. REPLACEMENT objects
    3. commands specified in the Run Using: parameter of the PROCESS object
    4. the CLEAR FILESPACE object
  • the order of objects on the Tree within a PROCESS is not important.
  • the order of execution of multiple PROCESS objects is based on their order on the Tree
    • → execution order is from top to bottom, a PROCESS completes and then next is begun

Input data for the software applications being run in one PROCESS can be extracted from the output files of software applications run in a previous PROCESS using an EXTRACT.


Process View

At the bottom left of EASAP Builder are icons that allow you to toggle between Tree view and Process view.

The Process view provides a flow diagram of the objects within the processes branch and you can right click on images in the diagram to insert new objects. Parameter values of objects can be set in the lower left part of the window.

The diagram can be adjusted by dragging and clicking boxes. Please note however that their location is not saved when EASAP Builder is closed. The diagram can also be manipulated through its toolbar, which contains operations including zooming and a variety of automatic layouts.

The toolbar also allows the diagram to be annotated with any “do if” expressions The overview panel allows you to select a subset of the diagram for viewing by dragging around the shaded rectangle.