This is a minor release that includes various bug fixes, and general improvements such
as: improved error reporting when Xoom service isn't running; the reporting of Xoom
misconfiguration and faults; and the ability to update the key Collection of an existing
key Property.
Improvements
- Improved error reporting in all client tools when the targeted Xoom service is not
running. The error message is now more specific.
- Added interpretations for the ClickSchedule tuning tool UI.
- Improved the interpretation of Property panel multi-value nodes in the
ClickSchedule Web Client configuration.
- Implemented basic Xoom misconfiguration and fault-reporting logic. The motivation for
this is that under certain circumstances the misconfiguration of Xoom could lead to data
corruption on the target system. The misconfiguration of XML tweakies, and of the results of
SXP calls that are required for interpreting configuration data, are now detected and
reported.
- We now allow the updating of the key Collection of an existing key Property
(in Service Optimization schema). This is consistent with the behaviour of the Service Optimization Structure Tool. The
behaviour is controlled via a new parameter Product.W6.Scheme.AllowKeyCollectionUpdates, which defaults to false.
Bug fixes
- The general bad reference (@xoom:ref="!!BadRef!!") is no longer interpreted
as a reference to an unknown type called "!!BadRef!!".
- Any types not present in the target database during deployment are now
correctly extracted from the deployed XoomXML file, preventing bogus
"Undefined type" errors.
