When creating a type from an XML file, the “AsTextDefault” property was not evaluated correctly, which meant that default values were not imported into the XML without subsequent adaptation. This concerns e.g. the following constructs: <XmlTag>Value</XmlTag>
Improved error message in the XML reader in case elements are not found.
The following message appeared in the servcie log on some systems:
This is a consequence of the display of CPU usage in the dashboard. The message is now only displayed as a warning with a hint to the dashboard and the number of messages has been significantly reduced.
The order of the columns in the article details has been revised.
There is now a hint if no type has been assigned to the XML Analyser.