eBiss 3

If after a drag/drop of a file to the message basket the Refresh button was pressed or a manual parsing of the message was performed, then an error occurred. This error is fixed.

When enabling the “AS2 Log” in the EdiInt address, different paths were created where the log was stored. As directory name:

• for the incoming messages the Id from the EdiInt address was used and
• for the outgoing messages the name of the EdiInt address.

The inconsistency is fixed, in both cases the name of the EdiInt address is used now.

If you went to the message view right after starting eBiss Client and filled the filter there so that no message was found and then went directly to the trading partners, no trading partners were displayed. This error is fixed.

Revision of the Error states (TaskState / TaskMessage / TaskMessageSeverity). documentation.

The errors:

• WrongDbVersion: were removed. No task is created for the error.
• DbIsDamaged: changed from value 8900 to 9900 so that the error is in the range of FatalStart(9000) and FatalEnd (9999).

The ChannelSender has been extended with the option:

• Do not change status: The status of the message is not changed, either to “Sending”, “Sent”, “Acknowledged by partner”, etc…. The history entries are written. If the flag is active, then “Do not reset status” is also active automatically.

In the course of the change “No 'callback' from service to client” in version 3.7.279 there were repeatedly dropouts in the log. The determination of when the log output is complete was not optimally implemented. This bug is fixed.

If the root property of the type was not in the JSON, the JSON data started one level later, then the JSON structure was loaded but could not be processed in the mapping. The error is fixed.

Furthermore, when selecting to load a file from the mapping, the type *.json was included.