BlackBerry AtHoc Networked Crisis Communication. Release Notes

Transcription

1 BlackBerry AtHoc Networked Crisis Communication Release Notes Release 7.6, September 2018

2 Copyright 2018 BlackBerry Limited. All Rights Reserved. This document may not be copied, disclosed, transferred, or modified without the prior written consent of BlackBerry Limited. While all content is believed to be correct at the time of publication, it is provided as general purpose information. The content is subject to change without notice and is provided as is and with no expressed or implied warranties whatsoever, including, but not limited to, a warranty for accuracy made by BlackBerry Limited. The software described in this document is provided under written license only, contains valuable trade secrets and proprietary information, and is protected by the copyright laws of the United States and other countries. Unauthorized use of software or its documentation can result in civil damages and criminal prosecution. Trademarks Trademarks, including but not limited to ATHOC, EMBLEM Design, ATHOC & Design and the PURPLE GLOBE Design are the trademarks or registered trademarks of BlackBerry Limited, its subsidiaries and/or affiliates, used under license, and the exclusive rights to such trademarks are expressly reserved. All other trademarks are the property of their respective owners. Users are not permitted to use these marks without the prior written consent of AtHoc or such third party which may own the mark. This product includes software developed by Microsoft ( This product includes software developed by Intel ( This product includes software developed by BroadCom ( All other trademarks mentioned in this document are the property of their respective owners. Patents This product includes technology protected under patents and pending patents. BlackBerry Solution License Agreement Contact Information BlackBerry AtHoc 2988 Campus Drive, Suite 100 San Mateo, CA Tel: athocsupport@blackberry.com Web:

3 Contents CHAPTER 1: INTRODUCTION 1 CHAPTER 2: NEW IN RELEASE API changes 2 AtHoc Account 3 CAP messages 3 Cloud and delivery services 3 Cross browser support 3 Desktop App 3 DISA APL compliance 4 Integrations 4 Management system updates 4 Mobile app updates 7 New documentation 8 Self Service 8 User sync client 8 CHAPTER 3: RESOLVED ISSUES 9 CHAPTER 4: KNOWN ISSUES 11 CHAPTER 5: BLACKBERRY ATHOC CUSTOMER PORTAL 19 i

4 Chapter 1: Introduction These release notes contain information about new and changed functionality for BlackBerry AtHoc Networked Crisis Communication Release 7.6. For more information about BlackBerry AtHoc or its related functionality, see the BlackBerry AtHoc documentation available at: 1

5 Chapter 2: New in release 7.6 The following sections describe new and changed features in the BlackBerry AtHoc product suite. API changes API version 1, SDK The following enhancements were added to the API v1/sdk: New delivery options to include organization codes for accountability officer alerts Device Name was distinguished from Device Common name in Alert Tracking The ability to get the status of a specific alert Alert templates indicate if they are selected for mobile publishing SDK access tokens from the V2 Auth Services can be used as validation. This enables developers to use both V1 and V1 APIs in a single application. SDK unlocks a locked account automatically after the time limit defined in the Security Policy settings page. For more information, see the BlackBerry AtHoc SDK Specification. API version 2, preview The user sync web API V2 is available in preview mode and supports the following actions: Synchronization of distribution lists Synchronization of users Creation of organization hierarchies Authentication using OAuth2 A new API endpoint which returns version numbers for the management system and APIs was added. Accountability Officer APIs which enable viewing and setting user status for Accountability events were added. The Sign In page is Mobile responsive. The Change Organization Grant type, which allows one user to retrieve access tokens for any organization that they have operator access to, is supported. The Auth Code Grant type is supported. The User Sync API supports partial user import. The API does not require the SDK Role if the application is created in the System Setup (3) organization. Note: To enable the user sync web API preview, contact your BlackBerry AtHoc account manager. 2

6 AtHoc Account Accountability event Change Status dialog and User Status history When an accountability event is live, an operator can change the status of one or more users from the accountability event Users tab. The Change Status dialog has been updated to display the history of status updates for the selected user. When an accountability event has ended, an operator can view the status history of impacted users. CAP messages Community Warning System (CWS) CAP messages now include a <uri> element so that when a "More Info link" is included in the publisher, it is passed to IIM. Cloud and delivery services French Canadian text-to-speech for telephony is now available on AtHoc Cloud. New SMS Short Codes were introduced. Performance improvements for multi-page text messages were made. Retry logic if a carrier does not support SMS concatenation was added. Support for TLS 1.2 for outbound s through PSS was added. Cross browser support BlackBerry AtHoc no longer requires Internet Explorer to access Settings pages.all pages are available on the following supported browsers: IE 10, 11 Edge Safari (Mac) Chrome Firefox Desktop App Desktop pop-ups that use the default delivery templates now resize to correctly display alerts that include a map image. Desktop delivery templates For new installations of BlackBerry AtHoc release 7.6, the following desktop delivery templates were removed: Amber Desktop Popup Weather Template 3

7 Gray Desktop Popup Green Desktop Popup Red Desktop Popup Yellow Desktop Popup Black Desktop Popup White Desktop Popup Tan (Brown) Desktop Popup Blue Desktop Popup Orange Desktop Popup Desktop performance optimization Delivery of alerts to desktop users was optimized so that 100,000 online desktop users can receive an alert that contains a map. DISA APL compliance The following items were added to support DISA APL compliance: SQL Server AccessPolicy enforcement. Shutdown events are now logged in the diagnostic log. Audit records are generated when an unsuccessful attempt to access a security object occurs. Integrations The RMG Digital Signage device page was updated to the latest UI. A new gateway and device were added for BBM Alerts. Management system updates Alert placeholders When creating an alert placeholder, selecting a default value is no longer mandatory. When an alert template contains a placeholder with no default value, an operator must now select a value for the placeholder before an alert can be published. Alert publishing The Quick Publish and Review and Publish pages were updated to allow quick editing of the Title and Body of an alert. Alert templates An option was added to Desktop Popup and device options in an alert template to include a map image in an alert. 4

8 An option was added to explicitly choose to make an alert template available for publishing to the Mobile App. Auto-populate K for address in giant voice key endpoints When a key endpoint is being created for a giant voice device, the mandatory K value is now autopopulated in the address field. BBM Alerts gateway and device The BlackBerry Messenger gateway and device were added to the management system to support the BBM Alerts integration. For more information, see the BBM Alerts Installation and Administration Guide. Custom placeholders in duplicate alerts The custom placeholder selection for duplicate alerts was removed. Disclaimer editor updates The System Disclaimer and Organization Disclaimer editors were updated to provide a rich text editor which supports adding styles and images. Previously, theses editors were XML-based. addresses on User Details dialogs addresses on User Details dialogs are now clickable and will open the local client if installed. Export Sent Alerts Users with Report Manager Operator permissions can now export the data in the Sent Alerts page to a CSV or Excel file. External operator permissions The Advanced Operator Manager settings page was updated and renamed to External Operator Permissions. The External Operator Permissions setting page includes the following functionality: Enables an administrator to give an operator who is not in the current organization operator permissions to the current organization. Provides the same user experience of creating an operator through the Users page. Shows only operators who are based in a different organization. Supports User Base restrictions, which was not possible in Advanced Operator Manager. Feature enablement The ability to enable or disable features at a system, enterprise, or individual organization level was added to the BlackBerry AtHoc management system. You must have system administrator permissions to enable or disable features. Feature enablement is inherited from parent organizations by default. Feature enablement on an enterprise organization is inherited by its sub organizations. You can override these inheritance rules by explicitly enabling or disabling a feature on an enterprise or individual organization. 5

9 Features can be enabled or disabled from Settings > System Settings > Feature Enablement. Layouts settings The following sections in the Layouts section of the General Settings page have been updated to display as a dialog on the page instead of as a separate window: User Details - My Profile User Details - Full page Default Columns - User Page Default Columns - User Reports Map image attachment improvements Direct access to the details of an alert, including maps, in Self Service from and desktop alerts was added. Desktop pop-ups are dynamically resized if a map is included in an alert. An option was added to alert templates that enables operators to choose whether to include a map image in a delivered alert. Point locations, such as those generated from the Mobile app, are supported. Mass device gateway The default CAP parameter in the Mass Device Gateway settings pages now includes the correct Sender (BlackBerry AtHoc Alerts) when "Copy Default Settings" is selected. Mobile App settings page The Mobile App settings page was updated so that each mobile feature in the Advanced Features section includes its own menu to select a distribution list. This enables administrators to select a different distribution list for each advanced mobile feature (Emergencies, Check In, Reports, and Tracking). RMG Digital Signage settings The RMG Digitial Signage device settings page was updated to display information about zones instead of endpoints. The RMG Digital Signage device options page was updated to replace the Alert Delivery type with an Alert Severity selection. The following severity colors are supported: InformationalPurple HighRed LowGreen ModerateOrange UnknownGrey Note: You must update NDS with the Digital Signage NDS 2.0 patch to enable these updates. For more information, see the BlackBerry AtHoc Digital Signage Installation Guide. 6

10 System default delivery template System default delivery templates can no longer be changed from the System Setup (3) organization. If you need to change a delivery template, duplicate the default delivery template or create a new custom delivery template. Two-factor authentication Two-factor authentication is supported in Self Services and the BlackBerry AtHoc management system. The setting to enable two-factor authenticationis available in the "Enabled Authentication Methods" section of the User Authentication settings page. The operator audit trail was updated to include entries for two-factor authentication sign-in. A verification code can be sent to , text, or phone based on the delivery methods configured for your organizaion. User import enhancements Importing users from a CSV file or through the User Import API was updated so that the import continues even if duplicate users are present. Previously, when duplicate users were present, the entire import would fail. Now, when duplicate users are present, the import will continue to import non-duplicate users and an error is displayed for the duplicate users. Importing users from the user manager with a CSV file or with the User Sync API was updated to allow import of users with partial or invalid data. If data is missing or invalid for a user entry, the rest of the user's information is still imported. Mobile app updates Mobile app release 4.2 for ios and Android A New REPLY option was added for Accountability Officers to confirm availability. The following operator capabilities were added: o o o View the current Alert Type and Alert Severity associated with the operator's chosen template. Edit the alert severity and alert type before publishing. Review the alert severity and alert type for published alerts. Support was added for 3D touch (ios) and App Shortcuts (Android) to send Emergency notices. MDM AppConfig can now push out the AtHoc cloud URL to support data sensitive UK customers to connect only to the UK AtHoc cloud. High severity alert sound reliability for ios devices was improved. Customers can now choose the alert templates to be available for publishing in the Mobile App. FedRAMP security fixes. The default address (support@athoc.com) was removed from sending Admin logs flow. 7

11 The following Mobile App versions will be deprecated after November 15, 2018: o o o o o o 3.1.X. (for ios and Android) 3.0.X and 3.0.X.X 3.2.X 3.3.X 3.4.X 2.5.X New documentation The following new documents are available on the help.blackberry.com portal: BlackBerry AtHoc API Quick Start Guide BlackBerry AtHoc Smart Card Authentication BlackBerry AtHoc User Sync Client Guidelines Self Service Self Service deep link from Alert Details and map images Self Service was updated so that clicking an alert from an or desktop pop-up takes the user directly to the alert details page in Self Service. If the alert includes a map, the user can click the map to go to an interactive map in the alert in Self Service. User sync client The existing CSV Importer Tool and LDAP Sync Modules were combined into a single User Sync Client. The User Sync Client can connect to an LDAP Directory or to CSV files in a file directory. The client is built on the LDAP Sync Module and contains all functionality that existed within the CSV Importer Tool, including the ability to connect through a proxy, the ability to parse multiple CSV files, and the ability to send out an when the sync is complete. 8

12 BlackBerry AtHoc Networked Crisis Communication Release Notes Chapter 3: Resolved issues The following issues have been resolved in BlackBerry AtHoc Release 7.6. Description Disclaimer text on login screen should not expose the JavaScript code when the disclaimer text contains combination of ' and " quotes. Placeholder dropdown selection is available even when "Show as read-only and prevent publisher from editing" is selected. When responding on behalf of others for an accountability event, if the comment exceed the 500 character limit, no error is displayed. Remove the unique key constraint on device name in DLV_DEVICE_TAB. The association between an endpoint and a mass device user in an alert template is lost when the organization is duplicated. When a System Setup (3) alert folder which is associated with an or sub organization alert template is deleted, the dependency pop-up is not displayed. The focus shifts to the top in the Create Blank Alert page when an organizational hierarchy is selected by advanced query in the Targeting section. If an alert is not ready, it is not loaded in edit mode after clicking on the Edit option from the Review and Publish page. Alert publishing to a non-restricted distribution list from an operator with restricted permissions is allowed. A user tracking report with events shows two entries "Sent" and "Responded" even if only one user with one device was targeted. A disabled accountability officer does not get displayed in the Details tab on the event dashboard. The Alert List SDK response displays an incorrect start and end time for a draft alert. The default severity is not changed for Emergency, Check-In and Report on the Mobile Alert Settings page. The "Update status on behalf of user" button stays enabled even if a restricted logged -in user can view 0 targeted users. The Import User page shows a spinning wheel if the previous import contained an excessive number of errors. On desktop alerts, the title text should not wrap in the middle of a word. A Weather Alert rule is displayed as Enabled on an export CSV file even when the rule is not enabled. The pie chart on an event Summary tab does not show the percentage of users who responded for disabled and deleted users. Notes 9

13 Chapter 3: Resolved issues Description The Distribution List Report displays deleted dynamic lists that were not part of the alert targeting. A welcome message is not displayed on the Desktop App even if the "Show Welcome message for first-time sign-on" setting is enabled. The Display Name in the head of user details window is not displayed when opened from the Add/Block user dialog. An advanced search in Sent Alerts with a date range specified does not provide the correct results. Status updated once through for an accountability event is updated twice in the ARCHIVE_USR_ATTRIBUTE_VALUE_TAB. The ALERT-TRACKING-DETAILS SDK Response and the "User Tracking Report with Events" contain duplicate records. Notes The "Show Welcome message" option was removed from the Desktop App settings page. The Sent Alerts page is slow on Alerts4. 10

14 BlackBerry AtHoc Networked Crisis Communication Release Notes Chapter 4: Known issues This document lists known issues in BlackBerry AtHoc releases. The following table describes issues that were first noted in version 7.6. Subsequent tables in this document list all other known issues, organized based on the product version that first exhibited the issue. Version 7.6 There are no known issues in this release. Version 7.5 Alerts and Alert Templates When using Internet Explorer, if you select to block and then unblock a user on the New Alert screen, the interface flickers. Version 7.4 Alerts and Alert Templates The IPAWS out of the box template does not get triggered after upgrading to release 7.4 when a custom template that was linked before the upgrade is made not ready or gets deleted. Integrated Weather Alerts A Connect organization does not get targeted by weather alerts when the Override Geo Information check box is selected. Make a change in the database to select the new out of the box alert template to be triggered by IPAWS alerts. Version 7.3 Account 11

15 Chapter 4: Known issues When creating an accountability event, if you add custom text to the device options for SMS, accountability officers receive an alert on their SMS device with the SMS custom device text instead of the accountability officer event message. Alerts and Alert Templates The values for Instruction or Response type placeholders are not rendered in an IPAWS custom alert template. On Safari, the Publish button on an alert Review and Publish page falls to the bottom of the screen. Connect When a response option includes a special character, the desktop app removes any text after the special character and the response is incorrectly added to the "RE: Others" category in tracking. Version Alerts and Alert Templates After pressing the browser back button on the New Template page, the user lands on last visited page instead of on Template Manager page. Version Patch 90 Alerts and Alert Templates Reports Session on Activity Log and Inbox pages (SignalR) behaves inconsistently. Version Patch 89 Users 12

16 BlackBerry AtHoc Networked Crisis Communication Release Notes An error is displayed when a user search is performed with the following special characters:! { } ^ Maps Migration from a release 88 to a release 90 template displays broken breadcrumb in Location Summary of the map. Other Duplicate organizations do not have the same failover URLs as the original. In the Schedule section, date time issue on set date and time radio button. In FireFox, the Results Based Targeting pop-up is not displayed when the bar chart is clicked in Delivery Distribution by Devices (Chart.) Version Patch 88 Alerts and Alert Templates RBT alert - The fill count settings of the original alert should not be preserved while RBT. Escalation using multi-select picklist should target each user as per attribute order. Export to PDF file border extends to the next page in case of fill count alert. Import/Export SDK: Targeting severity based default delivery template is not supported. Maps The picklist attribute created from the shape layer does not add to the count of user attributes. Users [UAM] The dates specified in min/max range for a datetime attribute are not reflected correctly in Self Service for a VPS where the VPS time is different than the system time. Version Patch 87 CP1 CHF3 Other 13

17 Chapter 4: Known issues Operator Password Change page: Clicking on Update when session is timed out does not show session timeout message on the login page. Version Patch 87 CP1 Alerts and Alert Templates Firefox - The counter jumps from 54 seconds to one minute while replaying the recorded audio. Scenario quick publish to all connected organizations: The Review and Publish page does not show newly connected organizations. Users After granting an operator the System Administrator role in System Setup, you can no longer edit permissions for that user in their base organization. EUM Search: Search shows invalid results when the searched text contains a closing curly brace. Import/Export The alert will still go to all connected Organizations. This issue does not occur when editing the alert first. Keep all System Administrators in System Setup, or create the user in the home organization before granting System Administrator permissions. Import does not support commas (,) in a device display name. Import does not support attribute names with the period (.). Importing users updates the profile with changes for the geo location point, but does not update the displayed location name. Mobile App The organization logo does not propogate to the Mobile App. 14

18 BlackBerry AtHoc Networked Crisis Communication Release Notes Other Browse - Play does not work the first time the user uploads the audio if the file is not fully uploaded Time Zone in PID 3 System Settings is misleading or wrong. GET-DISTRIBUTION-LISTS does not work for Administrator. Multiple active sessions for desktop client leads to an incorrect record for "response ignored by the system." Slow performance of Home Page with 500,000 users - Usercounts. There have been many improvements on the Home Page, but performance might be slow for 500,000 users. Version Patch 87 Alert Templates, Publishing, Inbox, Sent Alerts The Sent Alert Details view does not show the selected details for the phone, including Options settings. After an upgrade, an alert template with Emergency/Secure set up for phone does not have the "Select if the alert has no response options" check box selected. When targeting mass devices with key option and regular end points selection, the Review and Publish page appends a comma (,) to the end point display name. For example:,ati_pole. The Review and Publishing process does not validate on Targeting section's readiness when publishing the Draft Alert. Draft Alert: Unable to save the selected value of the placeholder. (Firefox) Alert/Scenario > Personal and Mass Devices options: Should not allow applying the custom text input with length validation error. Placeholders at Org level cannot have same name as Placeholders at level. User Management and Roles 15

19 Chapter 4: Known issues User Attributes: When a shape layer name is modified, the SP creates a new user attribute instead of renaming the existing attribute. Work around is manually running the SP: 1. Log in to AtHoc and navigate to Settings > Map and Layers > Shape Layers. 2. Click the Add a Layer link. 3. Enter a layer name. For example: Cities 4. Click the Import Data link. 5. Import a shape layer file. 6. Select the Predefined Zones check box and save. 7. Log in to the database server and run the following stored procedure exec dbo.utl_create_attribute_from_layer <provider id>. Where <provider id> is the 6-digit identifier for the organization in which this attribute should be created. For example Return to AtHoc and navigate to Settings > User Attributes. 9. Verify that the attribute with the layer name is created (attribute should be of type multi-select picklist). 10. Check the values for the attribute. The values (and the number of values) should match the number of shapes added in the imported shape layer file. Advanced Operator Manager role: an Operator with only the System Administrator role cannot view the details of existing operators and no authorization error is displayed. Creating attributes from shape layer does not display an error if a custom attribute already exists of type non-multi picklist. Grant Organization admin roles to the System Admin on System Setup (3). Before uploading a shape layer, administrators should ensure layer name uniqueness to avoid this issue. 16

20 BlackBerry AtHoc Networked Crisis Communication Release Notes On running the SP to create an attribute from a shape layer, the attributes' names are incorrect when more than one shape layer exists. SDK SDK: Telephony extensions (like Stop Calling options or Require PIN/Validation) are not applied. Default values are used. Devices Clean MSI: Out-of-the-box devices (aside from MIR3) appear as enabled with an empty device metastore on VPS (3,5,6). Reports and Tracking If you add the Organization attribute to Report Column Layout, the detailed users view hides the attribute when you click the pie chart. Import/Export SDK import: Date time attribute values are expected to be in the system timezone. Other Confusing message on login page when the base URL for the system is not valid. After running the SP to create a custom attribute, administrators should modify Display Names to be unique and meaningful. Always import Date-Time values in the system time zone. Version Patch 86 R3 There are no known issues for this release. 17

21 Chapter 4: Known issues Version Patch 85 R3 There are no known issues for this release. Version Patch 85 There are no known issues for this release. 18

22 BlackBerry AtHoc Networked Crisis Communication Release Notes Chapter 5: BlackBerry AtHoc customer portal BlackBerry AtHoc customers can obtain more information about BlackBerry AtHoc products or get answers to questions about their BlackBerry AtHoc systems through the Customer Portal: The BlackBerry AtHoc Customer Portal also provides support via computer-based training, Operator checklists, best practice resources, reference manuals, and users guides. 19