eBiss 3

When defining a complex field as not a list and assigning the attribute MapTrigger, the multiple occurrence of this complex field in the of this complex field in the JSON file results in multiple documents being created in eBiss.

Previously, splitting objects into multiple documents was only possible at the top list level. Especially in the course of the API connection, feedback can now be provided for each document.

By activating the Recognize multiple documents property in the XmlReader/XmlReaderEx, XML files can be divided into multiple documents by the XmlAnalyzerEx. If the option is activated for the reader, the XML message (file) is divided into several documents at the point at which a complex field is defined as not a list and provided with the Attribute MapTrigger.

An active time-controlled event listener without scheduled times led to many errors in the log up to the impairment of the eBiss service. of the eBiss service.

These errors have been fixed, both in the execution of the events and in the time-controlled event listener. The scheduled event listener can now only be activated with a valid start time and is deactivated if the last scheduled time is deleted or is converted into an exception.

In the Map Debugger, you can now also create rules “from” and “to” the instance view using drag & drop. Previously, this was only possible on the object definition.

For lookup values with more than 400 entries that are the same in the first 5 characters, only the first 400 entries were displayed. This error has been fixed:

• The first 6, 7, etc. characters are also searched for. characters if the result set is below the maximum number and
• the maximum number for the selection lists has been increased to 1000 entries.