User Tools

Site Tools


Publishing EASAPs

On this page the process of publishing EASAPs is discussed, and the subject of EASAP version control in EASA is also addressed.

Publishing Process

After fully developing, documenting and testing an EASAP, you need to publish it, so that Users then have access to it. Once published, the EASAP will be available under the Applications menu in User mode in the categories that you specified in EASAP Builder.

Initial Release

The process for publishing an EASAP is very straightforward. Use the following instructions to publish the initial release of your EASAP, which will be version number 1.0.

  • Log in to EASA and set mode to Author.
  • Using the My EASAPs or All EASAPs table, select the EASAP to be published using its title link in the Title column.
  • Under the Authoring menu, select Publish. The Publish page will appear.
  • Type in any comments regarding this release of the EASAP in the input box provided.
  • Click on the Publish button. After a few seconds, you should see a message that reads, “The EASAP has been successfully published.”
  • Confirm that the EASAP has been published by setting the mode to User, and then selecting the appropriate category under the Applications menu. Your EASAP should now be visible as a selection.

Subsequent Releases

Since an EASAP can be an ever evolving tool that you modify and improve based on user feedback, you will need to be able to publish EASAP versions beyond 1.0. EASA provides this capability and gives you a choice for either publishing a ‘Minor’ release or a ‘Major’ release of your EASAPs.

The numbering system for Minor and Major releases is as follows:

  • Minor releases increment the number after the decimal point by 1. For example, if an EASAP is currently on Version 1.0 and you publish a Minor release, then the new version number becomes 1.1.
  • Major releases increment the number before the decimal point by 1 and set the number after the decimal point to 0. For example, if an EASAP is currently on Version 1.1 and you publish a Major release, then the new version number becomes 2.0.

Use the following instructions to publish a Minor or Major release after the initial release of your EASAP:

  • Log in to EASA and set mode to Author.
  • Using the My EASAPs or All EASAPs table, select the EASAP to be published using its title link in the Title column.
  • Under the Authoring menu, select 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, you should see a message that reads, “The EASAP has been successfully published.”
  • You can confirm that the new release of the EASAP has been published by setting the mode to User, and then selecting the appropriate category under the Applications menu. You should then start up the EASAP to look for any visible modifications that identify the new release. If the modifications to the EASAP were in the Processes or Output branches, then you may want to perform a test submittal of the EASAP to fully confirm that the new release performs as expected.

Unpublishing an EASAP

There may be times when you will want to make an EASAP no longer be available to users. EASA provides this capability to “unpublish” your EASAPs.

Use the following instructions to unpublish an EASAP:

  • 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. After a few seconds, you should see a message that reads, “The EASAP has been removed from display for end users.”
  • Confirm that the EASAP has been removed from the Applications Library by setting the mode to User, and then selecting the appropriate category under the Applications menu. Your EASAP should no longer be visible as a selection.

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 Producing EASAP Documentation 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.

Page Tools