This is a minor patch release that fixes a bug in the Service Optimization scheme implementation that previously required newly created collection’s ProductName to be globally unique. On the Service Optimization side, this requirement is only true for top-level collections, while for child collections (such as multi-values) ProductName only needs to be unique within the scope of their parent collection. The fix takes this into account and corrects the behaviour.

Xoom 3.7.5 is a patch release that includes the following changes:

• Object References are no longer sorted by object name. The decision to make this change was made due to the fact that we encountered a single case where the sorting resulted in a functional error. The sorting was previously considered (and still is, according to ClickSoftware’s product documentation) to be an entirely safe convenience feature making it easier to look up object references using Xoom tools, XoomXML files and Service Optimization Administration tool.
• Both the readability and usability of Bad References Report have been improved. By displaying the value of the element that contains the actual bad reference, the report now makes it easier to decide whether the remedy for each particular bad reference is in the configuration or in the knowledge base (i.e. in the erroneous interpretation of the configuration).

Xoom 3.7.4 is a patch release that includes the following changes:

• The installer now allows users to specify the installation directory, both from command line and via the user interface. This is the directory where both Xoom and Xoom W6 directories will be created. The default directory is: “C:Program Files (x86)Zany Ants”.
• Settings Migration Tool no longer excludes the deployment of Agents Manager and Mapper settings due to the introduction of suitable keep-target instructions that will prevent server names from being overwritten by default.

Xoom 3.7.3 is a patch release that includes the following changes:

• It introduces a new standard query called Structure, which includes scheme and object reference setting. This query is very useful for automated analysis of the compatibility of different environments and the capability of transferring data between them.
• Xoom Processor now implements a built-in custom command called GetCustomQuery. The command takes a skeleton structure as its input, and fills in the details using Xoom, exactly as though the skeleton were the body of a named query. This means that ad hoc queries can be used with Xoom without the need to define corresponding named queries.

Xoom 3.7.2 is a patch release that addresses the name of Xoom custom installation inside the list of installed applications. Instead of just “for Customer” the name is now correctly displayed as “Xoom for Customer”.

Xoom 3.7.1 is a patch release that addresses two issues:

• Message size limit has been increased in order to accommodate large document sizes encountered by some customers.
• Support has been added for correct reference interpretation in a case where one or more keys of a referenced item themselves reference another item.

We are pleased to announce the release of Xoom 3.6.6. This includes a number of functional improvements, such as an improved References report; and greatly improved performance of configuration retrieval.

Continue reading Xoom 3.6.6 has been released →

We are pleased to announce the release of Xoom 3.6.5. 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 fault; and the ability to update the key collection of an existing key property.

Continue reading Xoom 3.6.5 has been released →