User Tools

Site Tools


Publish an EASAP

Once we have developed, documented and Tested an EASAP, we need to Publish it for a User to access.

A Published EASAP will be available for a User under EASA→Applications grouped by CATEGORY.


Initial Release

  • Follow these instructions to publish an initial release of an EASAP, the first version number is 1.0
    • As an Author select an EASAP at EASA→Applications→My EASAPs or All EASAPs
    • Go to EASA→Authoring→Publish
    • Add any relevant release notes in the space provided.
    • Click Publish button, a message will state,
      • The EASAP has been successfully published.
    • Confirm that the EASAP has been published,
      • At EASA→Set mode set mode to User
      • Select the appropriate category under the EASA→Applications menu.
        • →The EASAP should now be visible as a selection.

A Subsequent Release

An EASAP will evolve and improve based on new requirements or user feedback.

EASA provides the capability to publish a Minor or a Major new release of an EASAP.

  • publishing a new release will increment the version number of an EASAP
    • a Minor release will increment the number after the decimal point by one
      • for example version 1.0 will become 1.1
    • a Major release will increment the number before the decimal point by one and set the number after the decimal point to zero
      • for example version 1.1 will become version 2.0
  • to publish a new release
    • log in to EASA as an Author
    • select an EASAP under EASA→Applications→My EASAPs or All EASAPs
    • select EASA→Authoring→Publish
      • → the Publish page will appear
    • type in any comments regarding this release of the EASAP in the input box provided
    • click on either the Major Release or Minor Release button
      • →after a few seconds, a message shows The EASAP has been successfully published.
  • confirm that the new release of the EASAP has been published
    • select the appropriate category under EASA→Applications in User-mode
    • start up the EASAP and look for any visible modifications that identify the new release
      • →if changes were made in either PROCESSES or OUTPUT branches, submit the EASAP to confirm the changes.

Unpublish an EASAP

  • EASA provides the capability to unpublish an EASAP and make it unavailable to the Users.
    • * Log in to EASA and set mode to Author.
    • Using the My EASAPs or All EASAPs table, select the EASAP to be unpublished using its title link in the Title column.
    • Under the Authoring menu, select Publish. The Publish page will appear.
    • Click on the Unpublish button, a message will show…
      • The EASAP has been removed from display for end users.
  • Confirm that the EASAP is no longer visible in the Applications Library in User-mode.

Version Control Issues

This paragraph will describe how EASA deals with new and old versions of an EASAP.

Old EASAP Runs

First of all, EASA automatically archives old versions of EASAPs when new releases are published to the Application Library. Therefore, results from runs made by users with older versions of an EASAP automatically retain an association with the older version that was used to generate them.

To access the appropriate older version of an EASAP, all users need to do is click on the Open button () in the EASAP column of their My Results table. Therefore, as an author, you should not need to republish old versions of EASAPs when users want to continue making runs with an older version that they have already used.

As an author, you do have control over the link between EASAP runs stored in the Results Library and the EASAP version used to make the runs. You can delete old versions using the Publish History page found under the Authoring menu in Author mode. To delete an old version of an EASAP, click on the Delete button () in the Delete column and then click on the Delete button to confirm. More information on the use of the History page is provided in the following section.

Reverting to Old Versions

Another reason old EASAP versions are maintained by EASA is to allow authors to revert back to them if new versions do not work out as well as planned. You access old EASAP versions by selecting Publish History under the Authoring menu. This selection will display a table of all version of an EASAP that have been published throughout its history. To revert to a previous version, you complete the following steps:

  • Click on the Revert button () of the desired EASAP version in the Revert column on the Publish History page to revert the development version of the EASAP to this older version.
  • Click on the Revert button to confirm.
  • To revert the published version of the EASAP as well, select Publish under the Authoring menu, and then publish the EASAP as either a Minor or Major Release.

The other capability provided on the Publish History page is the deletion of old EASAP versions, which is accomplished by clicking on the Delete button () and then on the Delete button to confirm.

Keeping Help Files Current

As you develop and publish several versions of an EASAP, you should also continue to develop the help files for this EASAP. Details on the creation of help files and suggestions for their content are provided at the Document an EASAP page.

Release Notes

A ‘Release Notes’ section near the beginning / top of an EASAP’s help files could prove helpful as versions beyond 1.0 are published for an EASAP. This section might include the following information:

  • Reasons for making modifications resulting in the new release of the EASAP.
  • Descriptions of new features and their benefits to users.
  • Listing of problems / bugs fixed from the previous release.