Welcome to the Author's Pages.
Authoring in EASA is a broad subject and this page represents an index of pages to specific topics. Some of the larger topic pages are split into a collection of sub-topics.
The topics below cover the Authoring concept and provide a high-level overview of the stages involved in building an EASAP.
EASAP Builder is a graphical tool used by Authors to construct EASAPs.
The GUI of an EASAP as it shows in the web browser is achieved by arranging and setting objects in the EASAP Builder Tool.
In the below pages, the EASA Expression Language and the use of Units of measure will be discussed in detail.
In this section, the tools available within an EASAP to process events and then perform associated actions will be described in detail. By including event processing into an EASAP, you have the ability to make its user interface be much more interactive, and less reliant on only batch-type submissions.
In this section, the tools available within an EASAP to process and manipulate data are described. The data to be processed can be data entered by users or data read from a file.
A major usage of EASA is to incorporate Excel spreadsheets into web-based EASA Applications (EASAPs) and to deploy them out to end users via a browser.
In this section, the concept of producing diagrams in EASAPs will be discussed in detail. Diagrams can consist of lines, shapes, colors, text and even imported images.
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.
In this page, the methods for producing output from an EASAP will be described. The true value of an EASAP to users will be found in the contents of this output. Therefore, output generation is a very important part of an EASAP.
In this section, techniques for producing a well documented EASAP will be presented. Producing an EASAP with readily available, high quality documentation is one of the keys to it being easy to learn and use. Therefore, authors should plan to document their EASAPs properly.
A quality EASAP should not only be easy to use, but also reliable and robust. Even if an EASAP is simple to learn and easy to use, it will not gain acceptance by users if it does not work properly or if it tends to fail too often.
On this page the process of publishing EASAPs is discussed, and the subject of EASAP version control in EASA is also addressed. After fully developing, documenting and testing an EASAP, you need to publish it, so that Users then have access to it.
On this page, the capabilities available for allowing users to submit parametric studies with EASAPs are discussed. A parametric study can be useful for examining the effects on results of systematically varying certain input values using Parametric Ranges.
EASA contains functionality that allow its content to be integrated within other applications, such as SOA, PLM systems, workflow tools, CAD software, etc. Both EASA applications (EASAPs) and results generated by these EASAPs can be made available to these other applications.
In this section, the creation and use of custom code within the EASA Application Programmers Interface (API) will be described in detail. By writing custom code, the functionality of EASA can be extended beyond its current set of capabilities.
The SQL Wizard is divided into two separate modules, SQL Read Wizard and SQL Write Wizard. They allow you to create Database actions populated with children Read and Write actions respectively.
This page consists of a series of authoring examples that can be used as a reference.