- Excel Desktop Client new !
Estimated completion time → 10 minutes.
In this practical session, we will Test our EASAP from the previous sessions. Then we will Publish the EASAP and make it available for other Users at EASA→User→Applications.
Note, In many cases benign 'error' messages are sent to diagnostic files like err1-runplate.txt in which case it won't be zero length.
If the input file does not look like the one above and the cause of the problem cannot be determined, contact the instructor or EASA support representative.
At this point, hopefully we have successfully completed an EASAP run. We may close the file browsing window now examine the reported results by clicking on the View Results button () in the Output column.
The report will look similar to the image from our initial tour of EASA in Session 1.
If the report does not appear correctly, please contact your instructor or EASA support representative for assistance. Again, we may need to go back to EASAP Builder and make changes to the EASAP based on suggestions from the EASA support person. We will NOT have to resubmit the EASAP for another test: just save the changes in the Builder and then click on the Re-generate report using the latest version of this EASAP link to see an updated report. Iterate in this way until the report appears as expected.
The EASAP will now be ready for publishing.
Let's check whether our EASAP will be visible to Users on the EASA system.
Congratulations we have successfully created a network application that runs a User's input into an underlying batch process and returns an HTML formatted report with the results from the analysis.