A User uses the Applications menu to select a published EASAP to run.

An Author uses the Applications menu to create, modify or delete an EASAP under development.

• click New to create a new EASAP.
• a Create New EASAP page will appear
  • click Create

• new EASAP's default name takes one of two forms
  • New EASAP
  • New EASAP (1) (or higher integer to create a unique default name)
    • → give the EASAP a relevant name, see GUI of an EASAP to rename an EASAP

• To modify an existing EASAP,
  1. click EASA→Applications→My EASAPs
  2. select an EASAP from a table of EASAPs for the current User Group
  3. the Selected EASAP page appears with a link to the EASAP Builder
  4. click the link to open the Builder

• the table of My EASAPs has the following columns
  • EASAP→ click on a thumbnail image to select EASAP for further development
  • Title→ name given to EASAP that acts as a link to select it for further development
  • Directory→ directory on EASA Server in which EASAP is stored
  • Last Modified→ date and time the EASAP was last saved
  • Version→ version number if published, ‘Development’ if never published or ‘Unpublished’
  • Author→ name of the EASAP Author
  • Update→ click Update () to import an *.easap file
  • Export→ click Export () to export an EASAP to a *.easap file
  • Delete→ click Delete () to remove the EASAP forever

The EASAP Builder is the EASA development environment see EASAP Builder

The table of My EASAPs may be searched by name.

• click Import () for an EASAP to be brought to the Update EASAP page
• click Browse to select an *.easap file for the updated version of the EASAP
• click Import to update

If a warning message appears after updating an EASAP which states 'a certain software item does not exist', modify the PROCESSES branch of the EASAP ( Couple EASA to a software application) or add the missing software item in Compute Server Configuration, see Configure a Compute Server.

When you click on the Export button () for an EASAP in the table on either the My EASAPs or All EASAPs pages, you will be brought to the Export EASAP page. On this page, you first determine the content of the exported EASAP by selecting which of the three optional modules you wanted included,

1. Backup version files
2. Published version files
3. Test run files

Next, click Export and then save the exported EASAP as a *.easap file on a local drive.

Export is a prerequisite to the Import EASAPs functionality, which imports an *.easap file, as described at Importing EASAPs.

EASA→Applications→All EASAPs takes you to the page containing a table of all existing EASAPs. The table of All EASAPs behaves in the same manner as the table of My EASAPs. (see My EASAPs).

An Author may restrict other Authors from opening their EASAPs under All EASAPs by applying a password to protect it in PROPERTIES

Several example EASAPs are packaged into EASA and are accessible via the All EASAPs page. These example EASAPs are provided as references for you when you begin authoring your own EASAPs.

These example EASAPs will not necessarily run in your EASA system because they may require underlying software applications to which you do not have access. However, if you do have the right software applications, some of the examples can be made to run on your system.

The Import EASAPs selection under the Applications menu takes you to a page that allows you to import a new EASAP into your EASA system. The process for importing an EASAP is relatively simple. All you do is select the *.easap file, which contains the EASAP of interest, using the Browse button, and then click on the Import button to add the EASAP to your EASA system. The new EASAP will then appear in the table under My EASAPs. EASAP files (*.easap) are generated using the Export EASAP functionality as described in Exporting EASAPs.