V5.4.0 released

Check for important announcements such as version, service packs and patch releases, event dates, etc

Moderators: Ian, Dave, civanderputt, jcoulson, Jon, Wai

Posts: 298
Joined: Fri Sep 07, 2007 3:44 pm
Location: Sandy, UK
Contact: V5.4.0 released


Postby Steve » Mon Oct 01, 2018 2:02 pm V5.4.0 is now available and can be downloaded using the links below.

Full Release: Studio Links:
Windows 64 bit: ... _win64.exe
Windows 32 bit: ... _win32.exe
Linux 64 bit: ... x64.tar.gz
Linux 32 bit: ... x32.tar.gz
Mac: ... _0_mac.dmg

On-premise Server Links
Windows 64 bit: ... _win64.exe
Windows 32 bit: ... _win32.exe
Linux 64 bit: ... x64.tar.gz
Linux 32 bit: ... 32.tar.gzz
Mac: ... _0_mac.dmg

Upgrade: ...

Here is a summary of changes introduced in Version 5.4.0:
  1. Support for Progressive Web Applications (PWAs) has been added. PWAs represent an exciting new technology that aims to make web applications indistinguishable from native applications when used on mobile devices: phones and tablets. As a result, a web application can be used for all devices without the need to develop separate native apps. PWA features include:
    • Make a web app page look exactly the same as a native app page e.g. by removing the URL bar
    • Automatically add a start icon to the device’s home page
    • Caching of HTML pages and web resources by a service worker so the app can start even when offline
    • Downloading of web apps from an app store
    • Support for push notifications
  2. The WYSIWYG View used to display form pages has been changed to use JavaFX as the underlying software component – previously this was using Flying Saucer. The main advantage of using JavaFX is that CSS3 styling is now fully supported, whereas in the previous release many styling attributes were not supported. JavaFX also provides future proofing as it is a fully supported Java component and will continue to support new aspects of HTML and CSS as they are developed in the future.

  3. A new PDF generation engine wkhtmltopdf has been added which supports HTML5 and CSS3. This is available for use when generating a PDF using the Javascript form.generatePdf() function or the FPL outputpage command. This is in addition to the existing Flying Saucer engine which mostly only supports CSS2. A global property PDF Engine is used to switch between these two options. This property can be changed using the Server Admin App on the Server Properties page. By default this property is set as follows:
    • New installations: wkhtmltopdf
    • Upgraded systems: Flying Saucer
  4. Support for Domain Keys Identified Mail (DKIM) has been added to email accounts.

  5. It's now possible to see how a page will look on any device by selecting the appropriate device from the toolbar at the top of the WYSIWYG View - a dropdown of named devices is available including most common devices and this can be edited to add new devices.

  6. Support for many Web Forms 2.0 features has been added. Using these features it’s possible to eliminate the input validation popup alert boxes and replace these with browser-provided input validation:

    The following Web Forms 2.0 input types are supported and can be selected as display type for a form field or table column:

    color, date, datetime_local, email, month, number, range, search, tel, time, url, week

  7. New Server Resources folders can be created in the workspace. These folders are mapped to the root of the web application and provide a means of configuring static web resources and including these in the workspace.

  8. When a client API $eb.executeFunction() call is made, the server will now be aware of the control which initiated the event – most importantly this includes setting the current row of any tables. For example, you might have a table or repeater with a delete button that first displays a confirmation popup and then invokes a server function via eb.executeFunction(). With this change the server code to delete the table row is simply tables.myTable.deleteRow() whereas prior to this change a row identifier had to be extracted on the client then passed to the server.

  9. Images can now be dragged from the tree directly onto a page. The project that the image is dragged from needs to be accessible from the target project.

  10. Resources can now be dragged from the tree into the Resources View of a form, component etc. The project that the resource is dragged from needs to be accessible from the target project.

  11. The tree is now sorted so that any folders are shown before entities.

  12. Custom attributes within HTML Element Properties can now contain &&fieldname substitutable variables.

  13. Aria label texts can be configured for all appropriate controls. This property is typically used to provide a screen reader with a label for an otherwise anonymous control.

  14. Client browsers with Javascript disabled are no longer supported. Javascript support on the client is required to execute an Ebase form.

  15. A change has been made to the way Javascript arrays and/or objects are stored as session attributes which may affect applications using client.request.session.setAttribute(“xxx”, value) or client.request.session.getAttribute(“xxx”). The getAttribute() and setAttribute() methods are now intercepted and Javascript arrays and objects are saved in serialized form – this is to prevent excessive use of memory which can result when Rhino objects representing arrays and objects are saved directly. The impact of this change is that session attributes must now be explicitly saved (using setAttribute()) each time they are changed. It is no longer true that getting an attribute, then changing the retrieved object, will update the saved session attribute.

  16. The Workflow Administration application (form WORKFLOW_ADMINISTRATOR distributed in the VerjSamples project of the default workspace) now requires a user sign-on. Any user with access to the Server Administration application will also have access to the Workflow Administration application.
This update also includes various other bug fixes.

If you are upgrading from a previous Ebase version to v5.4.0 you will be initially presented with a logon screen when you first start the studio; if you have not previously registered on the portal, click on the Sign up link at the bottom of the logon panel. If you are already registered then enter your credentials - any service plans to which you have access will automatically appear as deployment targets. If you have previously registered with the Ebase Customer Portal you should be able to use the same userid/password combination for the new portal. Once you have logged on successfully to the studio, your credentials will be remembered and you should not need to logon again unless you explicitly logout of the Portal.
1 x

Who is online

Users browsing this forum: No registered users and 1 guest