eBiss 3

Revision of the process for terminating the eBiss service during setup. It will be installed in this version, but the benefits won't take effect until the next setup.

To set the system and trading partners, you can do so in the RestGet and RestGetHandleDocument job steps.

When using variables for the certificate, the subject had to be read after resolving the variable, which has been implemented in this version of eBiss.

When saving messages from WinClient, the error message displayed when a file with the same name already exists has been improved. The issue where files were not overwritten even after the user confirmed the action has also been resolved.

To shut down the eBiss service without interrupting any running jobs, the “Smooth shutdown of the eBiss Service” feature has been implemented. This can be performed via the “Advanced Actions” menu in the eBiss WinClient or via the eBiss CommandClient using the “–SmoothShutdown” option. During a smooth shutdown, all automations are first paused, and the system then waits up to 30 minutes for running jobs to complete. If any jobs are still running after 30 minutes, they are aborted and the service is terminated.

When defining types, you can use 'MapExternalName' to assign the same name to a field twice. For example, in the following code, the field name Address is defined twice:

1. As a simple field of type 'string' and
2. as a structure of type 'MyAddress'

   public String Address;

   [MapExternalName("Address")]
   public MyAddress ShippingAddress;

The structure is processed by eBiss, which selects the first matching field. Starting with this version, an error message indicating that the field name is duplicated is logged in debug mode.

When sending messages with more than 255 attachments, the excess attachments were not included in the transmission, whether using SMTP or HTTP.

The issue has been resolved:

• Up to 2,000 attachments can now be transmitted via the HTTP channel. The 255-attachment limit is too low for eBiss node-to-node communication.
• In both cases, if the limit is exceeded, the message will not be transmitted and a task will be created.