EASA is continually being improved to allow organizations to build and deploy custom web-enabled applications which leverage existing software faster and more easily. This document outlines the new features being introduced in Version 5.3.
This release saw a complete overhaul under the hood for better performance, stability, reliability and robustness.
EASA 5.3 now uses JACOB, which acts as a new and modern bridge between EASA and Excel.
The result is greatly improved data exchange with Excel. JACOB gives more control and freedom over how communication is accomplished, making the process more reliable, secure and lighter on computing resources, while simultaneously making improving speed and therefore response times.
Also debuting in EASA 5.3 is another new technology named METRO, replacing the component responsible for ensuring smooth data flow between the main EASA Server and its companion servers such as Compute Servers, EASA Web Service servers and Excel Servers.
The bundled version of Java is also updated to a newer version (1.7.0_79).
Giving up the top-down structure for a more topic-focused, article-based page structure, any information you need is just a click away. A powerful search box is always there to help you find what is not on the screen while the sidebar helps you navigate the various sections.
Being an online website itself, updating the EASA Help Pages no longer requires new versions of EASA to be released.
Now you can include more in reports by exporting the parts you need into a single PDF file.
The EXPORT TO PDF object has seen the addition of a new parameter called Type: which allows the inclusion of multiple ranges, even coming from multiple sheets. The exported PDF file will have all the selected ranges presented in a tidy linear fashion.
Setting up and maintaining database connections on the Administrator Web Pages is now supported by the optimal test query generator. With the click of a button, EASA will connect to the database and if successful, will set up a short and fast query it can use to validate the setup.
Another new option enables the configuration of direct connections between EASA Applications and Databases, leaving the EASA Server out of the process, making the load lighter on the server and in turn improving performance.
Additionally, if the EASAP doesn’t use the new direct connections, it has the option to use a proxy instead. This use case will lighten the load on the EASA server, while the option of using a different port to connect is also available.
Below is a list of additional changes in this release.