Version 3.0 maintenance 20 release note


New HTTPS call APIs

New APIs have been added to HTTPTool to help calling HTTPS URLs, the first one takes username and password parameters for HTTP basic authentication, the other takes a Java keystore (as stream) for SSL client authentication using certificates.

New API web services endpoints

New API endpoints for REST/SOAP/RAW and JSON web services are now available in the generic web UI webapp:


Unlike the I/O endpoint (/io) that uses integration credentials and unlike the other web services endpoints that use server's authentication, these API endpoints are using token-based authentication with explicit login and logout.

The AJAX lib has been updated to be able to use these endpoints (as the new "api" webservices gateway type).

These endpoints makes the webservices gateway webapp useless unless you need advanced, server-managed, authentication mechanisms.

Remote data sources

It is now possible to easily configure business objects pointing on remote datasources:

Description of configuration items as Markdow

The Description fields present on configuration items objects have been updated to long string with markdown rendering. This will allow to generate formatted functional documentation.

In this version, it has been done on the following objects:

In next versions the principle will be applied to other configuration objects.

Refactored content and resources JSPs as servlets

The PUB_content.jsp and PUB_resource.jsp JSPs have been refactored as /content and /resource servlets for better compatibility.

The JSPs have been left for backward compatibility but they now just forward the request to the servlets.

Module from URL

It is now possible to get a module package (either as ZIP or as XML) from an URL.

As long as the URL field is set the file is downloaded and stored locally as the local module file each time the module is saved.

This is, for instance, the case when clicking on the Import module action button, which triggers a save prior to its execution.

PDF publication header and footer as resource

It is now possible to use disposition-level image resources for header and footer images used in PDF pubications:

If these resources do not exists the legacy content resources are used instead.