We are very proud to announce the release of Xoom 3.11.4. This release contains a number of very significant bug fixes, an extensive re-implementation of the treatment of circular dependencies, it finally makes it possible to open any XSL file in Xoom Explorer without copying it to Reports folder first, and contains a number of other improvements. Details below the line.

Bug fixes

• Addressed the situation when items depending on other items that are created within the same deployment do not register as created on second pass, resulting in multiple deployments. The bug was in cache invalidation, which was rewritten in order to correctly handle various dependency scenarios encountered during deployment, whether it is about main or contained items.
• The treatment of the items of non-existent types is now more robust, with explicit warnings and explanations given in each particular case.
• Circular dependency handling code has been rewritten on all levels of the system, allowing such situations to be handled robustly and efficiently. Even circular dependencies in Service Optimization scheme are now resolved and deployed with errors, with the deployment automatically split into multiple steps that needed to be handled manually in the past.
• Items with subset types that only come into existence during interpretation and that contain references on those contained items within themselves (e.g. Agents Manager in Service Optimization) are now handled more efficiently, without needing additional passes to correct initially created bad references. These additional passes were invisible in the past, but the change brings a performance improvement.
• When errors occur during the last stage of deployment of Service Optimization objects, in particular when using Settings Migration Tool, the failure is no longer silent. Instead, the item remains on the list with the relevant error message.
• Service Optimization objects that contain properties that don’t exist in the target system are now successfully deployed with those properties removed. A warning is logged to report what happened in each such case.
• We now report an error if XoomXML that is being analysed or deployed contains duplicates of top level items as the final state is genuinely undefined in such a case given that XoomXML is declarative in nature.

Progress reporting in Settings Migration Tool

In addition to reporting the stage and pass during deployment, Settings Migration Tool now also reports how many items out of what total have already been deployed, and which item is currently being deployed. The progress is also logged by stage and pass as well as item by item, allowing subsequent performance analysis and the planning of how long each deployment will actually take.

Transformations in Xoom Explorer

Xoom Explorer’s transformations drop-down box was so far populated when the tool was started by scanning for any XSLT files in the Reports folder. In this release, we introduce an option at the bottom called <Browse> which opens a File Open dialog and allows the user to select an arbitrary XSLT file. The selected file is also added to the top of the options in the drop-down box (including its relative path from the Reports folder) for the rest of the application’s lifetime.

To make it easier to see the options, the drop-down now also resizes according to its contents.

Other

• A number of additional interpretations have been added to the knowledge base, and some incorrect interpretations have been corrected.
• OQL tweaky now support default type in situations where the type is not always explicitly defined in the configuration.