Once an EASAP has been selected under the Applications Menu, you use the Authoring menu to further develop the selected EASAP. There are eight selections under the Authoring menu:
By selecting EASAP Builder under the Authoring menu, you can open ‘EASAP Builder’, the main tool for developing EASAPs, by clicking on the EASAP Builder link. More details on EASAP Builder are provided in Using the EASAP Builder.
The Files selection under the Authoring menu (shown below) takes you to a page used to upload, open and edit files used in the selected EASAP. Examples of when you will need to use the Files page are located throughout the remaining chapters of this guide.
A couple of common uses are:
The Add File to EASAP section of the Files page is used to upload files from your computer on to the EASA Server where the selected EASAP is stored. First, the file name and path must be entered in to the ‘File to upload:’ input box, either by typing it in or by using the Browse button. After the file name and path have been entered, click on the Upload button to copy the file from your computer to the EASA Server.
Note: Files can also be uploaded within EASAP Builder using the Files Tab. In fact, the EASAP Builder method offers greater functionality and is the preferred approach.
The Current Files section of the Files page contains a table showing the files currently stored on the EASA Server for the selected EASAP. When a new EASAP is created, the following files are already present:
selection.gif All other files must be uploaded to be shown in the Current Files table. The Current Files table has the following five columns:
Clicking on an Open button () in the Download/Open column will display the file in a new window, while clicking on a Download button () will cause a pop-up window, as shown below, to appear requesting to either open the file or save it to disk.
The Template Editor selection under the Authoring menu takes you to a page containing a table of all files that have been designated as possible template files in EASAP Builder. From this table, you can modify individual files using the Template Editor tool.
The Template Editor table (below) has the following three columns:
The Testing selection under the Authoring menu takes you to the page containing every tool associated with testing. The Test EASAP and Analyse EASAP buttons open the EASAP for troubleshooting purposes, while the Application logs under them opens an event log for the particular EASAP. The table of all the test runs submitted for the selected EASAP on the bottom is called Test Results. This table has the following nine columns:
The figure below shows an example of the Testing page. For more details on testing EASAPs and submitting test runs, see Testing EASAPs.
The Publish selection under the Authoring menu allows you to:
The last three actions mentioned above are all accomplished by a single button click. For more details on publishing EASAPs, see Publishing EASAPs.
The Publish History selection under the Authoring menu takes you to the page containing a table showing all versions that have been published for the selected EASAP. An example of this page is shown in Figure 2.13. The Publish History table has the following six columns:
Note: If you delete an EASAP from the History table, you disable Users from accessing this version, which they may have used previously. Although this action may be warranted, it may be a good idea to notify the Users in your organization first.
The Backup selection under the Authoring menu allows you to:
You should use the Backup capability on a regular basis, especially before embarking on a number of significant changes to the EASAP after having tested it and gotten it functioning properly.
The Backup History selection under the Authoring menu takes you to the page containing a table showing all versions of the selected EASAP that have been backed up by the author (shown below). This table is essentially the same as the Publish History table, except that the Version number here represents the backup version and is not the same as the published version number.