The new view of all active sessions has been added under the group “Logging”. All sessions are listed here:
The administrator can see which user started the session from which computer, or if it is a job, from which EventListener the job was started.
Previously, the RuntimeSession was not always terminated after the session timeout, and the first time a session was started, the job was started twice internally.
The session handling of the eBiss website was revised. There are now two “Timeout” values:
There is a new option that sent error messages can be set to “done”.
Nullable fields that were not set were always considered set when evaluating via XPath evaluation. Thus, boolean always returned “true”, e.g. with
//Items [boolean(@NullableNumeric)]
And following evaluation always returned a result, even if @NullableNumeric was not set:
//Items [@NullableNumeric]
The error has been fixed.
The CC-Mail address at the partner is used when sending via the SMTP channel.
Navigating from a reference in a read-only field to an item that opens a new window resulted in to a window that was moved behind the current window or disappeared when the focus was maintained. This is corrected.
When searching for fields in types, attributes and parameters of attributes are now also found. Thus a search for e.g. “MapFrameDocument” is possible.
The XPath field can now also be of a type, e.g. “Date/Time Value”, if the field is to be used for the document date (MapFrameDocumentDate).
JSON Reader has been expanded to include:
New mapping function ConvertToDateTimeFromString and extension of the mapping function ConvertDateTimeFromString for use without formatting parameters.
The mapping function GetAllTasks threw an error if the mapping was executed in the debugger without message. Now only a warning is written to the log that the message is not present.
An evaluation of faulty messages via an EntityTransformer was not possible, because the EntityTransformer interrupts the processing in case of a task at the document. This has been fixed, so that documents selected via an EntitySelector with an error (task) are processed like non-errored documents. Unless another error (task) occurs.
So it is now possible to evaluate transformation errors created via AddError in a separate branch with GetAllTasks in the mapping, create a response message and send it back to the customer.