Xoom 3.6.6

Improvements

• The References Report – ReferencesReport.xsl – now correctly treats built-in subset types (such as Logic Domain, which is subset of Setting) and convenience types (such as Agent Instance, Agent Type or Task Property) by taking their multiple identities into account. Items with multiple identities now appear in the list as many times as they have identities, each identity sorted alphabetically by ID. At each appearance in the list, the item's other identities are given, along with its dependents and dependencies (as usual).
• Added logging information for monitoring the performance of lock and unlock operations in large Service Optimization server farms.
• Added the ability to deploy individual User Settings. The new behaviour is controlled by a new parameter Product.W6.Objects.IncludeUserDefinedUserSettings, which defaults to false. User Setting templates are always included in a retrieval but this new parameter controls whether retrieval should also include individual User Settings.
  Note: This feature should be used with caution. User Settings are not really suitable for transportation and cannot be interpreted by Xoom – that is, they are retrieved and deployed in their raw form. Nevertheless, we have added this capability to satisfy a few limited customer requests and have decided to make it generally available.
• Added the ability to include two types of transactional information from the Setting Collection – Agent status and Agent triggers – that would ordinarily be excluded during deployment. This behaviour is controlled by two new parameters – Product.W6.Objects.IncludeAgentsStatusSettings and Product.W6.Objects.IncludeAgentsTriggersSettings – both of which default to false.
  Note: The need to enable this functionality is limited to advanced automation cases where the monitoring of the triggering and running of Agents is required, and would not normally be useful. By default, Settings Migration Tool excludes these settings from deployment, even if they appear in the XoomXML being deployed.
• Increased the information that the AutoCapture tool gathers in a corpus, allowing the resulting corpora to be more broadly useful. As a result, running AutoCapture takes somewhat longer than before.
• Significant improvement in retrieval with run time halved in best cases.