On some systems, changing the column Size in table Message from int to long causes an error because the size is present in the index “Message_Manual_4”, “Message_Manual_5” and/or “Message_Manual_6”. This error has been rectified.

Exceptions/errors that occurred after the EntityIfCase does not create a task. This issue has now been resolved.

Extension of the job step PartnerImport to include the import of addresses and TypeSets.

Some JSON messages were not being displayed. This issue has now been resolved.

eBiss jobs containing a ExecuteExternal or a ExecuteExternalProcessor could not be saved. The error has been rectified.

For SFTP receive channel , several file patterns can be specified under File pattern, separated by “|”.

The mapping function GetTemplatePartnerDetails has been added.

Extension of the eBiss API to allow querying of TypeSets from the partner.

From this version onwards, the Job Step RestPushHandleDocument can be applied directly to an EntityObject from the mapping, without the document having been saved in a message. The object is transferred in JSON format.

The lookup values have been expanded to include the creation date.

If “Use as template” had been enabled in the AS2 send channel and a certificate had been stored, the certificate was hidden but still used. In other words, when sending a message via the AS2 send channel, the certificate stored in the EDIInt address was not used. From this version onwards, the certificate associated with the EDIInt address is applied and a thethe following warning is issued in the log:

• A recipient certificate file “<filename>” configured on the channel “<channel name>” will not be used because the channel is configured as “Use as template”

Furthermore, when the debug log is enabled, the fingerprint of the certificate used is displayed.

An error occurred during caching when multiple analysers of the same technical type were used under different type names, and where the subtype was not returned by the technical type.

In such a scenario, if two messages were processed within a job to which different subtypes were to be assigned, the first type recognised was incorrectly applied to both messages.

This error has been rectified.