xMatters Bamboo Operations Centre 1.5.3 Release Notes

Contents

Document Overview

Release Overview

Issues Fixed in This Release

Document Overview

These release notes are for the following xMatters release: 

Version: Bamboo Operations Centre v1.5

Release date: October 2, 2013 

NOTE: This document is subject to change after the initial release. If you would like to be alerted when the document is modified, click Following in on the Actions menu to the right of this document, and then select the Inbox check box. 

Release Overview 

Availability:

This update will be available to all xMatters Bamboo clients as of October 3, 2013. Please contact your xMatters enablement representative to request an upgrade. 

Issues Fixed in This Patch Release

To see details about an issue, click the related link in the Details column:

Reference  Issue Fixed
Details
BAM-946 A "technical difficulties" error occurs when creating an optional alert profile without any selected data groups Details
BAM-936 Clicking the "Email Account Details" button in BOC unexpectedly resets password Details
BAM-938 Device registration fails after a new Bamboo install Details
BAM-661 Export Audit Log includes only one line Details
BAM-926 iPhone clients may be uploaded without a corresponding APNS certificate Details
BAM-940 Users added through the API do not work with some functionality Details
BAM-939 Bamboo Operations Centre unable to use Google Maps geocoding Details
BAM-935 Publishing causes duplicate BlackBerry PIN items and client synchronization time outs Details
BAM-655 Message templates page not displaying correct text Details
BAM-630 Contacts not sorting by title Details
BAM-937 Updating password in BOC may require another reset after first login Details
BAM-945 Changing the country for a mobile/phone clears any previous number Details
BAM-948 Clicking the "Back" button on "Mandatory Alert" page results in a "Page Not Found" exception Details
BAM-955 Add support for latest Tomcat version to Bamboo web.xml Details
BAM-956 The thirdPartyContacts value should not be required when creating a scenario Details
BAM-957 Team API does not validate whether Scenario exists before saving Details
BAM-958 Incorrect entity type named in DEBUG messages Details
BAM-959 Intermittent failures in contact/third-party and contact/emergency APIs Details
BAM-962 Access restrictions are not correctly implemented Details

Details For Issues Fixed In This Release 

A "technical difficulties" error occurs when creating an optional alert profile without any selected data groups

An issue was identified when creating an optional alert profile where no data groups were selected. The process should succeed if the selected user does not belong to any data groups, or return a "User does not belong to this alert's data group" message if the user belongs to a data group. This issue has been addressed, and related error messages updated to be more informative.

Clicking the "Email Account Details" button in BOC unexpectedly resets password

Clicking the "Email Account Details" button in the Bamboo Operation Centre would reset the user's password, and send them an email with information about how to login and create a new password. This was not clear from either the button label or the BOC documentation. The button still works as intended, but it has been relabeled to make its function clearer, and the documentation updated to explain the process.

Device registration fails after a new Bamboo install

An issue was identified where device registration would fail on new Bamboo installation; this was due to a versioning mismatch within some of the Bamboo file namespaces. This issue has been addressed.

Export Audit Log includes only one line

Some customers reported that their exported Audit Logs consisted of only a single line. This issue was to traced to how the Audit Count Limit field on the System Administration > General Configuration page was incorrectly processing the default value of 0, which should have been interpreted as meaning "no limit". The logic in the page has been updated to correct this issue.

iPhone clients may be uploaded without a corresponding APNS certificate

The Bamboo Operations Centre was incorrectly allowing administrators to upload an iPhone client to their deployment without the corresponding and necessary Apple Push Notifications Service (APNS) certificate. This would result in thge BOC being unable to register as a push notification producer. Validation has been added to the upload process that will check the iPhone client and APNS certificate and prompt users to supply any missing files.

Users added through the API do not work with some functionality

Some users added via the REST API (i.e., the Persons operation) would not appear to function correctly for some features, such as Locate My Team and messaging. This was traced to an issue in the way the logic within the API handled the save process. The API calls have been updated to address this issue.

Bamboo Operations Centre unable to use Google Maps geocoding

An issue was reported with the geocoding system used in the Bamboo Operations Centre to determine the longitude and latitude for locations. This was due to a change in the way Google handled the related web service. This issue has been addressed.

Publishing causes duplicate BlackBerry PIN items and client synchronization time outs

An issue was identified where BlackBerry devices would accumulate duplicate PIN items in their API repository data. The increased data would slow down the Bamboo client synchronization, ultimately causing time outs or low memory warnings. This was caused by the Bamboo publish mechanism creating a redundant PIN item each time the data was imported to a device, even if the contact already had the information. To address this issue, the publish mechanism was updated to only append BlackBerry device items that had not already been appended to the repository.

Message templates page not displaying correct text

The message templates displayed in the BOC would truncate any text in the Subject or Message fields that followed an ampersand, though the text would still exist and be displayed on a user's device when the related message was sent. This made it difficult to properly review and edit the text within the message template. To address this issue, the related fields in the message template have been URL-encoded.

Contacts not sorting by title

An issue was reported where clicking the "Title" column would not sort contacts alphabetically as expected. This issue has been addressed.

Updating password in BOC may require another reset after first login

An issue was identified where a password reset would occasionally require a user to reset their password again after logging in with the new password. This issue has been addressed.

Changing the country for a mobile/phone clears any previous number

Previously, changing the country for a mobile or phone device in the Bamboo Operations Centre would replace the contents of the phone number field with the new country code and discard the existing number. The page has been updated so that changing the country for an existing phone or mobile will update the country code within the field, and retain the existing number.

Clicking the "Back" button on "Mandatory Alert" page results in a "Page Not Found" exception

An issue was reported where clicking the "Back" button on the Mandatory Alerts page in the Bamboo Operations Centre resulted in a "Page not found" error. This issue has been addressed.

Add support for latest Tomcat version to Bamboo web.xml

Some users were reporting an issue with logging in to Bamboo after they upgraded to the latest version of Tomcat (v7.0.42). The Bamboo web.xml file has been updated and tested to ensure compatibility.

The thirdPartyContacts value should not be required when creating a scenario

An issue was identified with the scenario API where the system was returning a runtime error if the thirdPartyContacts list was empty, despite this list not being required. The system should now initialize the list properly.

Team API does not validate whether Scenario exists before saving

An issue was identified where it was possible to create a team using the API and attempt to assign it to a scenario that did not exist in the system. When attempting to save the team, the system would return a blank error message. The team API will now validate that the specified scenario exists, and will return an error message indicating a failure if the scenario does not exist.

Incorrect entity type named in DEBUG messages

Some components were displaying an incorrect type in the DEBUG logs; for example, creating a third-party contact would result in a DEBUG message indicating a new plan category. This issue has been addressed.

Intermittent failures in contact/third-party and contact/emergency APIs

An issue was identified where two similar POST requests to the contact APIs would result in a runtime exception. This was due to the way the system assigns an ID to each request using a timestamp; if requests were similar enough and received at the same time, the ID would be the same. This issue has been addressed, but users should still attempt to ensure that each person's contact devices have unique names.

Access restrictions are not correctly implemented

The way in which Bamboo stores information about the creation properties of Plan Templates, Role Templates, and Plan Categories could result in some users encountering an "Access Denied" error when attempting to use or modify the components they created unless they had super administrator permissions. The application will now permit anyone with the correct permissions to use or edit these components.

xMatters Reference

JDN-4615 Originally created by Don Clark

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk