BlackBerry AtHoc Release Notes 7 · 2019-07-23 · Self Service for Mojave Mac OS • A Self Service redirection issue for Mojave Mac OS was fixed. Split two-factor authentication

BlackBerry AtHocRelease Notes 7.7

Last Published: March 2019

2019-07-23Z

| | 2

Contents

Introduction.......................................................................................................5

New in release 7.7............................................................................................ 6

Management system updates........................................................................... 7Acknowledge responses for extended alerts.......................................................................................................7Alert publishing for GETS-enabled phone devices ............................................................................................. 7Dependents............................................................................................................................................................. 7IPv6 support............................................................................................................................................................8New device types and gateways.......................................................................................................................... 8Organization-specific smart card regular expression..........................................................................................8Phone format library and validation update.........................................................................................................8Self Service for Mojave Mac OS........................................................................................................................... 8Split two-factor authentication settings............................................................................................................... 8User import............................................................................................................................................................. 9User sync client...................................................................................................................................................... 9

API changes....................................................................................................10API throttling.........................................................................................................................................................10

Cloud and delivery services............................................................................ 11

Desktop clients............................................................................................... 12

Documentation................................................................................................ 13

Integrations..................................................................................................... 14

Mobile app 4.3 for iOS and Android................................................................ 15

Self Service.....................................................................................................16Manage dependents.............................................................................................................................................16Mobile responsiveness........................................................................................................................................ 16

Resolved issues.............................................................................................. 17

| | iii

Known Issues..................................................................................................20

BlackBerry AtHoc customer portal.................................................................. 28

Legal notice.................................................................................................... 29

| | iv

IntroductionThese release notes contain information about new and changed functionality for BlackBerry AtHoc NetworkedCrisis Communication Release 7.7. For more information about BlackBerry AtHoc or its related functionality, seethe BlackBerry AtHoc documentation on docs.blackberry.com at the following URL: https://docs.blackberry.com/en/id-comm-collab/blackberry-athoc.

| Introduction | 5

https://docs.blackberry.com/en/id-comm-collab/blackberry-athoc


New in release 7.7The following sections describe new and changed features in the BlackBerry AtHoc product suite.

| New in release 7.7 | 6

Management system updates

Acknowledge responses for extended alerts• Users can respond to an alert when the alert end time is extended beyond the original configured end time.• The end time of an alert can be extended up to five minutes before the original configured end time.• Supported on email, mobile app, SMS, and TAS callback devices.• Alert summaries and reports display the extended end time and the responses captured during the extended

alert time.• This feature does not apply to accountability events.

Alert publishing for GETS-enabled phone devices Government Emergency Telecommunications Service (GETS) is a calling card program that provides authorizednational security and emergency preparedness (NS/EP) users improved call completion on the public landlinenetworks.

GETS supports national leadership, federal, state, local, tribal and territorial governments, first responders, andother authorized national security and emergency preparedness users. It is intended to be used in an emergencyor crisis situation when the landline network is congested and the probability of completing a normal call isreduced.

• Alerts can be published on GETS-enabled phone devices.• GETS is supported only on landlines, and not on mobile phones.

GETS configuration

• Create a GETS PIN in Settings > General Settings > Customization > Phone Call Setting.• Enable a GETS device in Settings > Devices. Select a phone device and then select the Enable GETS option in

the Details section of the device settings page.

DependentsFor organizations that are responsible not just for their personnel but also for their family members, BlackBerryAtHoc has introduced the ability to send alerts and events to users who are outside of an organization. Dependentusers are added in the BlackBerry AtHoc management system attached to the personnel (sponsor user) and canbe targeted in events and alerts.

• The Dependents feature can be enabled in the feature matrix and per alert or event template. It is disabled bydefault.

• Dependents can be added and viewed in the BlackBerry AtHoc management system and in Self Service.• When a sponsor is moved, deleted, enabled, or disabled, their dependents are also moved, deleted, enabled, or

disabled.• Dependents are attached to their sponsors and cannot be targeted explicitly. Dependents can only be targeted

in alerts or events their sponsor is targeted in.• Sponsors can add, delete, and update their dependents in Self Service.• Targeted dependents can respond to an alert or event from Self Service.• Existing users can be added as dependents using the User Import process or API.• An operator's user base can be configured to include or exclude the ability to manage or target dependents.

| Management system updates | 7

• Sponsors and dependents are displayed as a list in all user lists and reports. A sponsors column can be addedto allow sorting by family.

• The number of sponsors and dependents are displayed in the pie chart, reachability report, and summaryreport.

• The number of sponsors and dependents are displayed on the home page.• The Status History in Self Service displays both sponsor and dependents.• Accountability officers and accountability managers can update the status of dependents in events.• Targeted users calculations include targeted dependents.• User synchronization methods support dependents.• Self Service dependents pages are 508-compliant.• Dependents user interface screens are localized.

IPv6 support• The AtHoc Crisis Communication suite is compatible with IPv6 networks. Both servers and clients can operate

in an IPv6-only infrastructure.

New device types and gateways• Fax and TTY device types were added to the AtHoc Cloud East and AtHoc Cloud West delivery gateways.• A new device and gateway were added to support the LRAD Giant Voice System integration.

Organization-specific smart card regular expression• An organization-specific regular expression for desktop smart card sign on was added.• To set up the organization-specific regular expression, go to Settings > User Authentication > Desktop

App > Regular Expression.

Phone format library and validation updateTo reduce instances where valid international numbers are not accepted as valid in the BlackBerry AtHoc system,the following updates were made:

• The Phone Format Library was updated.• The validation level was changed from 'IsValidNumber' to 'IsPossibleNumber'.

Self Service for Mojave Mac OS• A Self Service redirection issue for Mojave Mac OS was fixed.

Split two-factor authentication settings• The ability to enable two-factor authentication for only end users in Self Service or operators in the BlackBerry

AtHoc management system was added.


• The option to enable two-factor authentication was updated to display separate check boxes for operators andfor users.

• To set up two-factor authentication, go to Settings > User Authentication > Enabled Authentication Methods.

User import• When a user attempts to import restricted users, an error is displayed.

User sync client• Support was added for friendly names for pick list values.


API changes• All organizations that an operator has access to can be listed.• A dashboard that displays performance measurements of APIs in AppDynamics was created.• API authentication and access was added to the Operator Audit Trail.• A new API was added that displays the list of all organizations, including details such as organization ID and

organization code.• A new API was added that displays the organization details for a specified organization code.• The account lockout (password) policy security rule was added.• Client ID restriction based on the organization enterprise tree was added.• The ability to provision a new Mobile Dynamics app for API access was added.• The Client ID and Client Secret are restricted to being used within an organization with system or enterprise

organization inheritance.• Error message format inconsistencies in the User Sync API were fixed.

API throttlingAPI throttling was introduced to prevent malicious or accidental recurring calls to the AtHoc APIs that can slowresponsiveness of the BlackBerry AtHoc system. Throttling can help protect server resources from being overused by limiting the overall API usage by any caller, client, organization, or endpoint.

• API throttling can be configured for clients and endpoints.• Whitelisting a client or endpoint exempts them from API throttling. Whitelisting can be configured in the

BlackBerry AtHoc management system at Settings > API Throttling. • You must have System Administrator permissions and be logged in to the System Setup (3) organization to

configure API throttling settings.• For more information, see "Configure API throttling settings" in the BlackBerry AtHoc System Administrator

Configuration Guide.

| API changes | 10

Cloud and delivery servicesGETS

• GETS is now available on AtHoc Cloud.

Cloud services

The following new services were added on cloud:

• TTY• Fax

TAS

The following new locales were added for TAS:

• Deutsch (Deutschland)• English (UK)• Español (España)• Español (Mexico)• Français (France)• Italiano (Italia)• Japanese (Japan)• Nederlands (Nederland)

SMS

• Conference information in SMS and web pages was added.• An SMS concatenation fix for carriers who do not support concatenation was made.• An SMS UI issue was fixed where the height of the content was fixed and the URL was not clickable in content.• An issue where the URL was broken when there was a comma and asterisk in the URL was fixed.

Extend alert end time

• The ability to extend the end time of an alert was added.

| Cloud and delivery services | 11

Desktop clientsRelease 6.2.x.279

• New desktop client release for Windows.• This release fixes the following issue:

• The desktop client writes the authentication proxy settings password in plain text in the log.

Release 1.8

• New desktop client release for Mac.• Supports Mac OS Mojave.• This release fixes an issue where the desktop client cannot connect using LDAP authentication.

Release 6.2.x.277

• Requires BlackBerry AtHoc Release 7.5 or newer.

| Desktop clients | 12

DocumentationThe following new documents are available in release 7.7:

• AtHoc Connect User Guide• Create and Publish Alerts User Guide• Cape Aural Warning System Installation and Configuration Guide• Eaton Waves Giant Voice System Installation and Configuration Guide • Enterprise Features User Guide• LRAD Warning System Installation and Configuration Guide• Manage the Activity Log Guide• Manage Alert Templates User Guide• Manage Alert Tracking and Reporting Guide• Manage Distribution Lists Guide• Manage Incoming Alerts from the Inbox User Guide• Manage Operators and Administrators Guide• Manage the Situation Map User Guide• Manage Users Guide• Monaco Warning System Installation and Configuration Guide• Motorola ACE3600 Installation and Configuration Guide• Operator Quick Start Guide• Public Address System Installation and Configuration Guide• Roles and Permissions Matrix• Supported Integrations document• System Administrator Configuration Guide

Access BlackBerry AtHoc documentation at the following URL: https://docs.blackberry.com/en/id-comm-collab/blackberry-athoc.

| Documentation | 13



IntegrationsUEM Notifications 3.0

• UEM administrators can ensure all of their users are in the BlackBerry AtHoc system by synchronizing usersfrom within the UEM management console. Administrators can set up a user synchronization service as asystem job that updates users periodically and keeps track of the changes.

LRAD Giant Voice

• New LRAD Giant Voice integration was added.

ServiceNow

• 10,000 users can be targeted in a single alert.• The reporting user interface was improved.

Social media

• Facebook and Twitter integrations were added to the cloud virtualized IIMs.• Fixed an issue where the More Info link was not available in Facebook posts from IIM.

| Integrations | 14

Mobile app 4.3 for iOS and Android• Support for Android 5.x, iOS 9, and iOS 10 was deprecated.• Support for extending the end time of an alert was added.

| Mobile app 4.3 for iOS and Android | 15

Self Service

Manage dependents• Sponsors can manage dependents in Self Service.• When sponsors move, their dependents move with them. Sponsors and dependents are never disassociated.• Dependents can do most of the things a regular user can do (provided they have the credentials), including

responding to alerts and events.• Sponsors can update the status of their dependents for events.

Mobile responsivenessMobile responsiveness for Self Service enables end users to create and update their user profiles in Self Servicewhile using mobile devices.

• Self Service mobile responsiveness can be enabled and disabled in the feature matrix.• Error screens and disclaimers, two-factor authentication, and smart card authentication flows can be displayed

on any screen size or device.• End users can perform any of the following tasks on any screen size or device:

• Register for Self Service• Sign in to their account• Reset their forgotten password or username• Select languages• View and update their user profile, including attributes, devices, and hierarchy• Switch organizations• Add, update, or delete dependents

• The Self Service Inbox is not mobile responsive. This functionality will be added in a future release.

| Self Service | 16

Resolved issuesThe following issues have been resolved in BlackBerry AtHoc Release 7.7.

Jira ID Description Notes

IWS-13198 Draft Alert: Unable to save the overwrittendefault value of the placeholder.

—

IWS-15174 The Online attribute does not appear in theexported .csv.

—

IWS-24004 Duplicate organizations do not havethe same failover URLs as the originalorganization.

—

IWS-26984 When disabling or deleting users, theCalculate link for the DateTime attributeworks only the first time. If you change theDateTime value, the calculate link does notupdate.

—

IWS-28044 A newly provisioned organization does notrequest a password reset at first login.

—

IWS-30919 The group search filter is not displayedon the export dialog if a group searchwith child node and advanced search isperformed on the Users tab.

—

IWS-31207 Desktop client error is returned as ageneric error and is missing information.

—

IWS-34260 Failed Login details are not displayedunless you go to the My Details page onthe user's parent organization.

—

IWS-36107 An incorrect message is displayed in theEnd Alert confirmation message pop up.

—

IWS-37944 Export .csv is slower in Release 7.5. —

IWS-39420 A phone number validation error is seenfor .csv import and SDK calls.

—

IWS-40102 Errors encountered during .csv import. —

IWS-40542 Unable to save a valid Ethiopian phonenumber.

—

| Resolved issues | 17


IWS-40635 Search records are not updated and thegrid becomes blank when a pill is removedfrom the Sent Alert manager.

—

IWS-40829 When the Fill Count settings are savedon an alert template, when a new alerttemplate is created, the new template hasthe Fill Count settings of the previouslysaved template.

—

IWS-41051 SelfService CAC Auth 500 Error in reverseweb proxy environment.

—

IWS-41143 Not able to respond to alerts on desktopapp when smart card authentication isrequired on the server.

In order to use the Desktop Traffic URL,you must update the Provider Version foryour system.

1. Log in to the BlackBerry AtHocmanagement system as anadministrator.

2. Change to the System Setup(3) organization.

3. Click .4. Click to open any of the following

pages:

• Desktop App• User Authentication• General Settings

5. Click Save.

IWS-41464 Alert folder permissions for externaloperators were affected after upgrade.

—

IWS-41470 The data in the Targeting and Contentsections is lost when an event that hasmultiple text entries is forwarded.

—

IWS-41503 User Search in the External OperatorManager can not locate some users.

—

IWS-41724 Alert template Schedule section (AM/PM)issue.

—

IWS-41778 Security vulnerability with deliverytemplates.

—

IWS-42023 The digital signature breaks for allseverities.

—



IWS-42033 Desktop redirection attributes are notrecorded and saved when the client isredirected.

—

IWS-42034 Call termination (user termination) is notworking as expected.

—

IWS-42280 The User Tracking report cannot be sortedby Display Name.

—

IWS-42648 The Responded User count is sometimesincorrect in accountability events.

—

ISEC-756 JavaScript hijacking. —


Known IssuesThis section lists known issues in BlackBerry AtHoc releases.

The following table describes issues that were first noted in version 7.7. Subsequent tables in this document listall other known issues, organized based on the product version that first exhibited the issue.

7.7

Jira ID Product Package

Problem Workaround

Documentation

— — When you try to accesspages in the documentationwebsite docs.blackberry.com, youmight receive page not found errorsintermittently.

Clear your browsercache and tryagain, or usea browser inincognito mode.

User authentication settings

IWS-42920 Both When an organization is duplicatedusing the Organization Duplicator, theTwo Factor Authentication "Required forOperators" check box is not selected onthe duplicated organization.

—

User sync client

IWS-42818 Both Using non-English characters in a DisplayName or Common Name attribute valuecauses an error when using the User SyncClient.

—

7.6


Problem Workaround

Localization

IWS-42541 Both Unable to create a Twitter mass deviceuser on an en-UK localized organization.

—

SDK

IWS-41685 Both The Alert Publish SDK does not supportmore than 10,000 users.

—

| Known Issues | 20

7.5

• There are no known issues in Release 7.5.

7.4


Problem Workaround

Alerts and Alert Templates

IWS-35377 Enterprise The IPAWS out-of-the-box templatedoes not get triggered after upgrading torelease 7.4 when a custom template thatwas linked before the upgrade is made notready or gets deleted.

Make a change inthe database toselect the new out-of-the-box alerttemplate to betriggered by IPAWSalerts.

7.3


Problem Workaround


IWS-35084 Enterprise The values for Instruction or Responsetype placeholders are not rendered in anIPAWS custom alert template.

—

IWS-38378 Both On Safari, the Publish button on an alertReview and Publish page falls to thebottom of the screen.

—

7.0.0.2

• There are no known issues in release 7.0.0.2.

7.0.0.1


Problem Workaround


| Known Issues | 21


Problem Workaround

IWS-29312 Both After pressing the browser back button onthe new template page, the user lands onlast surfed page instead of on templatemanager page.

—

6.1.8 Patch 90


Problem Workaround

Reports

IWS-26353 Both When the Security Policy for sessiontimeout is changed, the Activity logand Inbox pages (SignalR) behaveinconsistently.

—

6.1.8 Patch 89


Problem Workaround

Users

IWS-21459 Both An error is displayed when a user searchis performed with the following specialcharacters: ! { } ^

—

Maps

IWS-24180 Enterprise Migration from a release 88 to a release90 template displays broken breadcrumbin Location Summary of the map.

—

Other

IWS-24294 Both In the Schedule section, date time issue onset date and time radio button.

—

IWS-24489 Both In FireFox, the Results Based Targetingpop up is not displayed when the barchart is clicked in Delivery Distribution byDevices (Chart.)

—

| Known Issues | 22

6.1.8 Patch 88


Problem Workaround


IWS-16932 Enterprise Delivery of alerts on a phone device usingthe TAS (AtHoc Cloud East) gateway trimsthe alert body.

—

IWS-17310 Enterprise Escalation using multi-select picklistshould target each user as per attributeorder.

—

IWS-19042 Enterprise Export to PDF file border extends to nextpage in case of Fill count Alert.

—

Maps

IWS-19226 Enterprise The picklist attribute created from theshape layer does not add to the count ofuser attributes.

—

Users

IWS-24620 Enterprise [UAM] The dates specified in min/maxrange for a DateTime attribute are notreflected correctly in Self Service for a VPSwhere the VPS time is different than thesystem time.

—

6.1.8 Patch 87CP1 CHF3

• There are no known issues in Release 87CP1 CHF3.

6.1.8 Patch 87 CP1


Problem Workaround


IWS-15196 Both On Firefox, the counter jumps from 54seconds to 1 minute while replaying therecorded audio.

—

| Known Issues | 23


Problem Workaround

IWS-17375 Both Scenario quick publish to all connectedorganizations: The Review and Publishpage does not show newly connectedorganizations.

The alert will stillgo to all connectedorganizations. Thisissue does notoccur when editingthe alert first.

Users

IWS-15071 Enterprise After granting an operator the SystemAdministrator role in System Setup, youcan no longer edit permissions for thatuser in their base organization.

Keep all SystemAdministratorsin System Setup,or create theuser in the homeorganization beforegranting SystemAdministratorpermissions.

IWS-17085 Both EUM Search: Search shows invalid resultswhen the searched text contains closingcurly brace (}).

—

Import/Export

IWS-14922 Both Import does not support commas (,) in adevice display name.

—

IWS-14929 Both Import does not support attribute nameswith a period (.).

—

IWS-15216 Both Importing users updates the profile withchanges for the geolocation point, butdoes not update the displayed locationname.

—

Mobile App

IWS-12923 Both The organization logo does not propogateto the Mobile App.

—

Other

IWS-14632 Enterprise Browse - Play does not work the first timethe user uploads the audio if the file is notfully uploaded.

IWS-16766 Enterprise Time Zone in PID 3 System Settings ismisleading or wrong.

—

| Known Issues | 24


Problem Workaround

IWS-17132 Enterprise Multiple active sessions for desktop clientleads to an incorrect record for "responseignored by the system."

—

IWS-17240 Enterprise Slow performance of Home Page with500,000 users - Usercounts.

There havebeen manyimprovements onthe Home Page, butperformance mightbe slow for 500,000users.

6.1.8 Patch 87


Problem Workaround

Alert Templates, Publishing, Inbox, Sent Alerts

IWS-12742 Both The Sent Alert Details view does notshow the selected details for the phone,including Options settings.

—

IWS-13063 Enterprise When targeting mass devices with keyoption and regular endpoints selection,the Review and Publish page appends acomma (,) to the endpoint display name.For example: ,ATI_Pole

—

IWS-13192 Enterprise The Review and Publishing processdoes not validate on Targeting section'sreadiness when publishing the Draft Alert.

—

IWS-13248 Both (Firefox) Alert/Scenario > Personal andMass Devices options: Should not allowapplying the custom text input with lengthvalidation error.

—

IWS-15146 Enterprise Placeholders at Org level cannot havesame name as Placeholders at Enterpriselevel.

—

User Management and Roles

| Known Issues | 25


Problem Workaround

IWS-12079 Enterprise User Attributes: When a shape layer nameis modified, the SP creates a new userattribute instead of renaming the existingattribute. Work around is manually runningthe SP:

1. Log in to AtHoc and navigateto Settings > Map and Layers > ShapeLayers.

2. Click the Add a Layer link.3. Enter a layer name. For example: Cities4. 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 execdbo.UTL_CREATE_ATTRIBUTE_FROM_LAYER< provider id>.

Where <provider id> is the 6-digitidentifier for the organization in whichthis attribute should be created. Forexample “111111”

8. Return to AtHoc and navigateto Settings > User Attributes.

9. Verify that the attribute with the layername is created (attribute should be oftype multi-select picklist).

10.Check the values for the attribute.Thevalues (and the number of values)should match the number of shapesadded in the imported shape layer file.

—

IWS-13247 Enterprise Creating attributes from a shape layerdoes not throw an error if a non multi-picklist custom attribute already exists.

Before uploadinga shape layer,administratorsshould ensure layername uniquenessto avoid this issue.

IWS-13253 Enterprise On running the SP to create an attributefrom a shape layer, the attribute's namesare incorrect when more than one shapelayer exists.

—

SDK

| Known Issues | 26


Problem Workaround

IWS-12930 Enterprise SDK: Telephony extensions (like StopCalling options or Require PIN/Validation)are not applied. Default values are used.

—

Devices

IWS-13021 Enterprise Clean MSI: Out-of-the-box devices (asidefrom MIR3) appear as enabled with anempty device metastore on VPS (3,5,6).

—

Reports and Tracking

IWS-13042 Both If you add the Organization attribute toReport Column Layout, the detailed usersview hides the attribute when you click thepie chart.

—

Import/Export

IWS-18137 Enterprise SDK import: DateTime attribute valuesafter import get converted as per the VPStimezone.

Always importDate Time valuesin the system timezone.

Other

IWS-13614 Enterprise Confusing message on login page whenthe base URL for the system is not valid.

—

6.1.8 Patch 86 R3

• There are no known issues in release 6.1.8 Patch 86 R3.

6.1.8 Patch 85 R3

• There are no known issues in release 6.1.8 Patch 85 R3.

6.1.8 Patch 85

• There are no known issues in release 6.1.8 Patch 85.

| Known Issues | 27

BlackBerry AtHoc customer portalBlackBerry AtHoc customers can obtain more information about BlackBerry AtHoc products or get answers toquestions about their BlackBerry AtHoc systems through the Customer Portal:

https://support.athoc.com/customer-support-portal.html

The BlackBerry AtHoc Customer Portal also provides support via computer-based training, Operator checklists,best practice resources, reference manuals, and users guides.

| BlackBerry AtHoc customer portal | 28

https://support.athoc.com/customer-support-portal.html

Legal noticeCopyright © 2019 BlackBerry Limited. All Rights Reserved.

This document may not be copied, disclosed, transferred, or modified without the prior written consent ofBlackBerry Limited. While all content is believed to be correct at the time of publication, it is provided as generalpurpose information. The content is subject to change without notice and is provided “as is” and with noexpressed or implied warranties whatsoever, including, but not limited to, a warranty for accuracy made byBlackBerry Limited. The software described in this document is provided under written license only, containsvaluable trade secrets and proprietary information, and is protected by the copyright laws of the United Statesand other countries. Unauthorized use of software or its documentation can result in civil damages and criminalprosecution.

This product includes software developed by Microsoft (http://www.microsoft.com).

This product includes software developed by Intel (http://www.intel.com).

This product includes software developed by BroadCom (http://www.broadcom.com).

Trademarks

Trademarks, including but not limited to BLACKBERRY, EMBLEM Design, ATHOC, ATHOC & Design and thePURPLE 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 othertrademarks are the property of their respective owners.

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

https://us.blackberry.com/legal/blackberry-solution-license-agreement

Contact Information

BlackBerry AtHoc

311 Fairchild Drive

Mountain View, CA 94043

Tel: 1-650-685-3000

Email: [email protected]

Web: http://www.athoc.com

| Legal notice | 29

https://us.blackberry.com/legal/blackberry-solution-license-agreement

Documents

BlackBerry AtHoc Release Notes 7 · 2019-07-23 · Self Service for Mojave Mac OS • A Self Service redirection issue for Mojave Mac OS was fixed. Split two-factor authentication