We are pleased to announce the release of Xoom 3.12.2. This is a minor patch release containing the following bug fixes and improvements:
- The minimum version of SXP Extensions for Service Optimization has been bumped to 5.4.0 in order to ensure that the functionality introduced in Xoom 3.12 is indeed always available regardless of whether this is a new installation or an upgrade of Xoom. The most important impact of this change is on SOT Toolkit users.
- Added minor changes to the knowledge base in order to improve support in particular of central settings in the Custom category.
We are proud to announce the release of Xoom 3.12. The combined main purpose of this release has been to update the Service Optimization extensions, including introducing functionality that enables SOT Toolkit to perform measurements related to optional hours. Details are listed below.
Continue reading Xoom 3.12 has been released
We are proud to announce the release of Xoom 3.11.5. This is a minor release containing functional improvements and bug fixes. Details below.
Continue reading Xoom 3.11.5 has been released
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.
Continue reading Xoom 3.11.4 has been released
We are happy to announce the release of Xoom 3.11.3. This is another important hotfix that contains a number of bug fixes and other changes:
- Fixed the bug where during the analysis references to non-root items (such as Service Optimization’s multi-value collections) resulted in an erroneous reporting of bad references.
- When XoomXML is loaded for analysis or deployment, items belonging to types that are not known to Xoom are now identified, an error is reported, and the items in question are then excluded from any further processing.
- Dramatically improved the performance of analysis prior to deployment.
- Introduced detailed logging of errors during the update of the current configuration representation after the changes to the configuration have been made by Xoom.
- Stack trace is now always included in the exception entries in the log files, making the understanding of errors encountered during the use of Xoom easier.
We are happy to announce the release of Xoom 3.11.2. This is an important hotfix that fixes the following bugs:
- Fixed a bug where any reference to any new contained items (such as for example a reference to any property in a new collection) loaded into Settings Migration Tool was mis-identified as a bad reference during analysis on Xoom 3.11 server.
- Fixed a bug that caused an unknown method error being reported for GetDepthLimitedOuterXml method, resulting in deployment failing to complete.
- Prevented a few situations in Settings Migration Tool that could cause a Null Reference Exception to be thrown.
We are very proud to announce the release of Xoom 3.11. This release contains significant performance improvements and many new features, as well as a number of stability enhancements and bug fixes. It consolidates the functionality offered by Xoom 3, including the capabilities needed for Service Optimization Tuning Toolkit, as development moves towards cloud-friendly and truly multi-product Xoom 4 and beyond.
Continue reading Xoom 3.11 has been released
We are happy to announce the release of Xoom 3.10.6. This release brings two notable new features: transition to ZanyScript 2 in knowledge base processing, and the introduction of a much more powerful mechanism for filtering collections and items that shouldn’t be retrieved or deployed by Xoom.
Continue reading Xoom 3.10.6 has been released
This is a minor release containing an important change required in automated upgrade scenarios.
When the upgraded scheme contains one or more properties that don’t exist on the old system, deploying a XoomXML from the old system would previously cause those properties’ values to be deleted. The behaviour has been changed in this release, and those properties will now keep the value they already have in the updated system. This avoids the need to pre-populate the XoomXML file with up-to-date data prior to deployment in such scenarios, which is a cumbersome and time consuming step.
We are not currently aware of any situations where this change is undesirable since persistent differences in the scheme only ever happen in upgrade scenarios.
We are excited to announce the release of Xoom 3.10.4. This is a maintenance release addressing the following issues:
- XoomProcessor (xp.exe) is now truly a stand-alone executable. Previously it expected nlog.config file to be located next to it.
- Changes in scheme implementation now enable Xoom to create custom multi-value collections with non-standard table names. This functionality is useful in upgrade scenarios, in particular where the two versions in question are quite far apart and custom collections in the old version were created using non-standard tools, typically by hand-crafted SQL scripts.
- Xoom now correctly handles scheme deployment with extensive use of xoom:set special form, such as deployment of all user-defined properties using xoom:set in upgrade scenarios. Previously, there were circumstances where false differences were identified during deployment (although not deployed), and the deployment was sometimes cut short and had to be done in stages.
- Assignment collection on the list of excluded dictionaries (a Service Optimization setting) is now handled correctly.