BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look...

30
BlackBerry AtHoc Release Notes 7.6 (OnPrem) Last Published: September 2018

Transcript of BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look...

Page 1: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

BlackBerry AtHocRelease Notes 7.6 (OnPrem)

Last Published: September 2018

Page 2: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

2019-07-23Z

 |  | 2

Page 3: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Contents

Introduction.......................................................................................................4

New in release 7.6............................................................................................ 5

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

Known Issues..................................................................................................21

BlackBerry AtHoc customer portal.................................................................. 29

Legal notices...................................................................................................30

 |  | iii

Page 4: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

IntroductionThese release notes contain information about new and changed functionality for BlackBerry AtHoc NetworkedCrisis Communication Release 7.6. 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 | 4

Page 5: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

New in release 7.6The 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.• The Infocasting, Get Scenario, and ALERT-LIST SDKs have been updated to include Type and Severity

attributes.

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.

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 theaccountability event Users tab. The Change Status dialog has been updated to display the history of statusupdates for the selected user.

• When an accountability event has ended, an operator can view the status history of impacted users.

Account Event Manager updates

The following changes were made to the Account Event Manager page:

 | New in release 7.6 | 5

Page 6: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

• The delete function was removed for accountability events.• The More Actions list was replaced with an End button.• The Accountability Event Deleted action was removed from the Accountability Event entity in the operator audit

trail.

Accountability Officer availability

Operators who send accountability events can now see if their designated Accountability Officers are available toupdate their users' statuses. Out of the box and custom accountability event templates now include the followingresponse options for Accountability Officer messages:

• I am available to update user status• I am not available to update user status

The new response options are part of the Accountability Officer initial message and are viewable in the sent alertreport. Operators with publisher permissions can see these response options in accountability event reports andin a new Accountability Officer section on the event page summary tab.

CAP messages

Community Warning System (CWS) CAP messages now include a <uri> element so that when a "More Infolink" is included in the publisher, it is passed to IIM.

Cloud and delivery services

• Automatic reply emails (Out of Office) are ignored.• 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 emails through PSS was added.• UK organizations were migrated to the UK mobile/connect.

Cross browser support

BlackBerry AtHoc no longer requires Internet Explorer to access Settings pages.All pages are available on thefollowing 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 mapimage.

Desktop delivery templates

For new installations of BlackBerry AtHoc release 7.6, the following desktop delivery templates were removed:

• Amber Desktop Popup

 | New in release 7.6 | 6

Page 7: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

• Weather Template• 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 thatcontains 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.• Concurrent active sessions limit.• Added Severity, Urgency and Certainty to IPAWS device options.• Revoke operator permissions when user was disabled/deleted.• Allow creation of User attribute named 'Title.'• The IPAWS device is using the unquoted service path.

Distribution list map layers

The live map was upgraded to show users on a map with distribution list layers. The live map provides thefollowing features:

• The last location of users from up to 10 distribution lists is displayed.• Each distribution can have up to 500 users.• Distribution lists are displayed on the map using customizable colors.• Users who appear in the same area are clustered together.• The map refreshes automatically once a minute.• The map is configurable in the BlackBerry AtHoc management system in the Map Settings page.

Note: Distribution list map layers must be enabled on a per-organization level by a System Administrator.

Note: Availability of this feature is determined by your license. For more information, contact your BlackBerryAtHoc account manager.

Integrated Weather Alerts

• All feeds collected by the system during the last 15 days can be exported.• A new out of the box weather alert template is now available.• Updated walk-throughs for Integrated Weather Alerts were created.

 | New in release 7.6 | 7

Page 8: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Integration manager changes

• Improved user interface; each agent opens in a new window.• "Metastore" was renamed to "Configuration" and a bigger text box was added to improve the ability to edit.• Agent's name is now read-only.• The Generic agent was removed. 

Integrations

• Eaton WAVES giant voice device integration was introduced.• The RMG Digital Signage device page was updated to the latest UI.• A new gateway and device were added for BBM Enterprise Alerts.

IPv6

• The AtHoc Crisis Communication suite is compatible with IPv6 networks. Both servers and clients can operatein an IPv6-only infrastructure.

LDAP sync module version 2.0

The BlackBerry AtHoc LDAP sync module has been updated from version 1.2.7 to 2.0.0 and supports thefollowing features and functions:

• Enterprise user management and user move

• You can create a single configuration to support your enterprise.• You can specify the Organization attribute for the sub organization for new users to be created in. If a user

already exists, they are moved to the specified organization.• Expected performance improvement of more than 5 times.• Use of the Username as the primary key instead of the mapping ID (mid).

In LDAP module version 1.2.7, the LDAPSync client used the SDK payload to synchronize users and distributionlist memberships. The LDAPSync client used the mid to look up the user. Instead of using the mid, theBlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changesto XSL Mappings that were done to map the attribute from the LDAPSync Server to the BlackBerry AtHocattribute. 

• Use of OAuth2 for authentication, which requires client provisioning per customer. For more information,including instructions for migrating from LDAP module 1.2.7 to 2.0.0, see the BlackBerry AtHoc LDAP DataIntegration Module Guide.

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

• A warning is now displayed when an operator attempts to publish to all users.• The Quick Publish and Review and Publish pages were updated to allow quick editing of the Title and Body of

an alert. 

 | New in release 7.6 | 8

Page 9: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Alert templates

• An option was added to Desktop Popup and Email device options in an alert template to include a map imagein an alert.

• An option was added to explicitly choose to make an alert template available for publishing to the Mobile App.

Audit trail for mass device endpoints

Actions performed from the More Actions list in the Mass Device Endpoints settings page (create, delete, export,and update) are now captured in the operator audit trail.

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 auto-populated in theaddress field.

BBM Enterprise Alerts gateway and device

The BlackBerry Messenger gateway and device were added to the management system to support theBBM Enterprise Alerts integration. For more information, see the BBM Enterprise Alerts Installation andAdministration Guide.

CAWS device zone targeting

When targeting a Cape Aural Warning System (CAWS) device with pre-recorded audio or text-to-speech, you cannow target individual zones or combinations of zones.

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 whichsupports adding styles and images. Previously, theses editors were XML-based.

Email addresses on User Details dialogs

Email addresses on User Details dialogs are now clickable and will open the local email 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 orExcel file.

External operator permissions

The Advanced Operator Manager settings page was updated and renamed to External Operator Permissions. TheExternal 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 thecurrent 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 theBlackBerry AtHoc management system. You must have system administrator permissions to enable or disablefeatures. Feature enablement is inherited from parent organizations by default.

Feature enablement on an enterprise organization is inherited by its sub organizations. You can override theseinheritance rules by explicitly enabling or disabling a feature on an enterprise or individual organization.

 | New in release 7.6 | 9

Page 10: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Features can be enabled or disabled from Settings > System Settings > Feature Enablement.

IIM

An out of the box IIM monitor was added.

IPAWS device options

New Severity, Certainty, and Urgency values were added to the IPAWS CAP Exchange, IPAWS NWEM, EAS, andIPAWS WEA device options.

The following Severity selections were added:

• Extreme• Severe (default)• Moderate• Minor• Unknown

The following Certainty selections were added:

• Observed (default)• Likely• Possible• Unlikely• Unknown 

The following Urgency selections were added:

• Immediate (default)• Expected• Future• Past• Unknown

IPAWS gateway

A new IPAWS gateway named IPAWS (East) was added. The existing IPAWS gateway was renamed toIPAWS (West). The IPAWS (East) gateway can be configured as a failover gateway.

You must enable both IPAWS gateways using the Device Configurator tool after a fresh installation or an upgradeto release 7.5 or later release.

IPAWS template

A new out of the box IPAWS alert template was added.

Layouts settings

The following sections in the Layouts section of the General Settings page have been updated to display as adialog 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

Limit active concurrent sessions

You can configure your BlackBerry AtHoc system to limit the number of active sessions an operator can haveopen at the same time with the same operator account. Session information is maintained by an operator'sbrowser. Multiple tabs on the same browser use the same session. When the active session limit is reached,

 | New in release 7.6 | 10

Page 11: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

the operator is prompted to close an existing session. The session that has been inactive for the longest time isterminated and the operator is redirected to the login page.

Map image in alerts

If an alert template includes a map, an image of the map is included in desktop and email alerts. The map isincluded in the delivered alert if the following conditions are met:

• The map is present in the alert template or alert.• Desktop or email is targeted.• An out of the box delivery template or a new custom delivery template is used.• The cloud delivery services gateway is used for email.

The map that is included in an email or desktop alert is not interactive. The alert recipient cannot zoom in or outon the map. Clicking on the map image opens the interactive map in the alert in Self Service Inbox. Any mapobjects defined in the publisher map are included in the map image in a zoom-to-fit fashion.

This feature is supported on both Windows and Mac desktop apps.

Map image attachment improvements

• Direct access to the details of an alert, including maps, in Self Service from email and desktop alerts wasadded.

• 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.

Mass device manager export format

The format of the exported information from the Mass Device Endpoint manager was updated with the followingimprovements:

• There is one row for each endpoint.• Columns that are not relevant for the selected devices are empty.• The export produces a flat CSV file where no formatting is needed.

The exported CSV file contains the following columns by default:

• ID• Endpoint name• Display name• Device• Device Category• GV Type• GV Key• Address• Feed title• Feed description• Created on• Updated on

Mobile App settings page

 | New in release 7.6 | 11

Page 12: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

The Mobile App settings page was updated so that each mobile feature in the Advanced Features sectionincludes its own menu to select a distribution list. This enables administrators to select a different distribution listfor each advanced mobile feature (Emergencies, Check In, Reports, and Tracking).

Monaco Warning System publisher warning

When publishing an alert with the Monaco Warning System as a targeted device in the BlackBerry AtHocmanagement system, a warning is displayed about targeting limitations.

When targeting a Monaco Warning System device, you can target a single giant voice (GV) tower (pole), multipleGV towers (poles), or a single GV group (zone). Targeting multiple GV groups or a combination of groups andtowers is not valid. If these limitations are not followed, publishing to the Monaco Warning System device mayfail.

New authentication flow for desktop

A new section was added to the User Authentication settings page that enables administrators to select "Defer toSelf Service" as an authentication method. When this method is selected, a pop-up sign in window appears on theend user's desktop. When the user clicks the Sign In button, they are presented with the Self Service login page.

This update is available for desktop client release 6.2.x.277 or later.

Organization Settings page removal

The Organization Settings page has been removed. Content previously found on the Organization Settings pagecan now be found on these pages in the BlackBerry AtHoc management console:

• The Desktop Software tab is now available in the Desktop App settings page.• The Targeting and Delivery tab is now available in the General settings page.• The User Authentication & SDK is now available in the User Authentication settings page.

Removal of IE warning

A warning about some settings not being available on browsers other than Internet Explorer was removed fromthe Settings page. All settings pages are now available on all supported browsers.

Revoke operator permissions when you disable or delete a user account

When a user's account is disabled or deleted from the End User Manager, Edit User Details screen, or from theAdvanced Operator Manager in the BlackBerry AtHoc management system, their operator permissions arerevoked.

When a user's account is disabled or deleted using any of the following methods, their operator permissions arerevoked:

• Auto disable/delete user job• User import CSV• User Sync web API• User Sync SDK

If a user is logged in to the BlackBerry AtHoc management system when their operator permissions are revoked,they are logged out and redirected to an error screen with the following message: "You do not have the requiredOperator Permissions to access this page. Contact your administrator."

RMG Digital Signage settings

The RMG Digitial Signage device settings page was updated to display information about zones instead ofendpoints. The RMG Digital Signage device options page was updated to replace the Alert Delivery type with anAlert Severity selection. The following severity colors are supported:

• Informational—Purple• High—Red

 | New in release 7.6 | 12

Page 13: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

• Low—Green• Moderate—Orange• Unknown—Grey

Note: You must update NDS with the Digital Signage NDS 2.0 patch to enable these updates. For moreinformation, see the BlackBerry AtHoc Digital Signage Installation Guide.

Single sign-on

Only one single sign on login page is required for Enterprise even when there are multiple sub organizations.

System default delivery template

System default delivery templates can no longer be changed from the System Setup (3) organization. If you needto change a delivery template, duplicate the default delivery template or create a new custom delivery template.

Title attribute

You can now create a user attribute named "Title."

Two-factor authentication

• Two-factor authentication is supported in Self Services and the BlackBerry AtHoc management system.• The setting to enable two-factor authentication is 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 email, text, or phone based on the delivery methods configured for your

organization.

User import enhancements

• Importing users from a CSV file or through the User Import API was updated so that the import continues evenif 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 isdisplayed for the duplicate users.

• Importing users from the user manager with a CSV file or with the User Sync API was updated to allowimport of users with partial or invalid data. If data is missing or invalid for a user entry, the rest of the user'sinformation is still imported.

Quoted service path requirement

The AtHocDeliveryService.exe file requires a quoted service path.

Web API provisioning from the Settings page

A new API Applications settings page was added to allow organization administrators to provision a new clientIDand client secret. These values are required when calling the web API preview or configuring LDAP sync version2.0.0. Provisioned applications can then be enabled by a system administrator.

Mass Device Manager changes

The following changes were made to the Mass Device Manager:

• Mass device users are now Mass Device Endpoints.• A new user interface for mass device endpoints manager was added.• Endpoints can be created for specific enabled devices.• Only relevant fields are displayed based on the selected device.• Mass devices are organized into the following categories:

• Giant Voice

 | New in release 7.6 | 13

Page 14: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

• Feed (RSS and XML)• Social (Twitter)• Common

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:

• 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 email address ([email protected]) was removed from sending Admin logs flow. The following

Mobile App versions will be deprecated after November 15, 2018:

• 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

Mobile app release 4.1 for iOS and Android

• Support was added for 3D Touch and App Shortcuts to view and access live alerts or to log in and publish analert.

• The user interface was optimized for iPhone X.• User interface improvements were made when using a hotspot, on the phone, or when using any capability that

includes a banner at the top of the mobile device screen.• A prompt was added to enable location services during the Report flow.• Support for mass devices was added in the alert publisher.

Mobile app release 4.1 for BB10 devices

• The user interface was updated to align with the BlackBerry suite look and feel.• Support was added for regional PSS (UK and CA availability.)

Mobile app release 3.4.1

• Support for Android O and iOS11 was added.• Registration performance improvements. Once a user verifies their email, moving to the Org Code screen is

about three times as fast.

Mobile app release 4.0

• Complete overhaul of the user interface to align with the BlackBerry enterprise suite of apps and to incorporateplatform-native user interface components.

• New Alert Publisher summary screen.

 | New in release 7.6 | 14

Page 15: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

• Operators can edit targeted personal devices from the Alert Publisher.• Android permissions are now requested when a user taps on a feature that requires that permission instead of

the user being asked for all permissions when they first install the mobile app.

Mobile app release 3.5

• Silent alert delivery. A new option was added which enables alerts to be sent silently to the mobile app,regardless of the severity of the alert.

• The user registration user interface was updated. The "Use another email address" option was removed. Now,when you tap "Send another confirmation" the user is taken to the initial Registration screen.

• Mobile alert publishing now supports up to 4000 characters in the alert body.• The minimum supported OS versions are iOS 9 and Android OS 5.

Dynamics Mobile App release 3.5

• The dynamics mobile app was updated to provide the same features and functionality as the non-managedmobile app.

• The dynamics mobile app provides additional security.• Administrators can remotely push the dynamics mobile app, clear data, determine allowed integrations and

usage policies, and control access to the app.• Operators can publish alerts without VPN software.• Available as the BlackBerry AtHoc Dynamics app in the Apple App store and in the Google Play store.

New documentation

The following new documents are available on the help.blackberry.com portal:

• BlackBerry AtHoc API Quick Start Guide• BlackBerry AtHoc BlackBerry 10 User Guide• BlackBerry AtHoc Desktop App Installation and Administration Guide (for Microsoft Windows)• BlackBerry AtHoc Mobile User Guide• BlackBerry AtHoc Smart Card Authentication• BlackBerry AtHoc Whelen Giant Voice System Installation Guide• 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 email or desktop pop-up takes the user directly to thealert details page in Self Service. If the alert includes a map, the user can click the map to go to an interactive mapin the alert in Self Service.

Self Service smart card login

Self Service can now use Subject Alternative Name (SAN) for logins with a smart card.

Self Service two-factor authentication

You can require all users in your organization to use two-factor authentication when logging in to Self Service.

When two-factor authentication is enabled for your organization, when a user logs in to Self Service, they firstenter their username and password. They are then presented with a screen to select a verification code deliverymethod (email, text, or phone). The user then receives a verification code on their selected device which they enterin Self Service to continue the login process.

 | New in release 7.6 | 15

Page 16: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

The verification code expires if not used after five minutes. If the verification code expires, or the user does notenter the verification code correctly, they can request a new verification code. If the user attempts to log in with asecond verification code, they will need to fill in a captcha field. Users can request up to three verification codes.If a user requests more than three verification codes, they are returned to the login page, and an unsuccessfullogin attempt is logged. This may result in the user account becoming locked if they exceed the number of loginattempts defined in the organization's security policy settings.

Self Service user-initiated move

The Self Service user-initiated move feature enables an administrator to configure their enterprise organization toallow their users to move themselves between sub organizations from the My Profile page in Self Service.

When a user moves to a different organization, their view of Self Service may change, depending on thesettings of the organization they are moving to. If the user is an operator, any operator permissions they hadin their original organization are revoked. If the user had enterprise administrator permissions in the enterpriseorganization, they are retained. If the user had permissions in other organizations within the enterprise ororganizations outside of the enterprise organization, they are retained.

Before user-initiated move can be enabled, require user uniqueness must be enabled in the enterprise settings.

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 theLDAP Sync Module and contains all functionality that existed within the CSV Importer Tool, including the ability toconnect through a proxy, the ability to parse multiple CSV files, and the ability to send out an email when the syncis complete.

 | New in release 7.6 | 16

Page 17: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Resolved issuesThe following issues were listed in past release notes as known issues and have been resolved in BlackBerryAtHoc Release 7.6.

Description Notes

In Security Policy, deselecting Allow Multiple Concurrent Sessions doesnot work.

Allow Multiple ConcurrentSessions has been removed from

the Sessions Settings section.

SDK: MetaStore parameter not reported by SDK. —

Disclaimer text on login screen should not expose the JavaScript codewhen the disclaimer text contains combination of ' and " quotes.

SDK: Targeting severity based default delivery template is not supported. —

Users exported from German Organization still have Username inEnglish.

Export Mass Device web page dialog is in English on GermanOrganization.

Changes to the settings for user messages and accountability officersin an accountability event template are retained after selecting to cancelthe changes.

Placeholder dropdown selection is available even when "Show as read-only and prevent publisher from editing" is selected.

Custom text preview for SMS does not work in accountability events. —

When responding on behalf of others for an accountability event, if thecomment exceed the 500 character limit, no error is displayed.

On the Users tab on the event dashboard for an accountability event, ifyou click to change the status of a user, the pop-up contains a status andcomments from a previously updated user.

The target organization count does not get updated when the locationcheck box is checked and then unchecked.

Remove the unique key constraint on device name in DLV_DEVICE_TAB. —

he association between an endpoint and a mass device user in an alerttemplate is lost when the organization is duplicated.

The date format displays incorrectly in the operator audit trailexport CSV file.

 | Resolved issues | 17

Page 18: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Description Notes

TTS does not correctly read phone numbers in the format (xxx)-xxx-xxxx. Operators should use one ofthe following supported phoneformats when inserting phone

numbers into alert content:

• xxx xxx xxxx• xxx.xxx.xxxx• xxx-xxx-xxxx

On the Sent Alerts page, the user interface gets distorted after sortingthe page by the Publisher column header.

When a System Setup (3) alert folder which is associated with anEnterprise or sub organization alert template is deleted, the dependencypop-up is not displayed.

The focus shifts to the top in the Create Blank Alert page when anorganizational hierarchy is selected by advanced query in the Targetingsection.

If an alert is not ready, it is not loaded in edit mode after clicking on theEdit option from the Review and Publish page.

Alert publishing to a non-restricted distribution list from an operator withrestricted 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.

Unable to send alerts to mass devices due to syndication errors. —

When a phone number extension is represented by an X, the extensiondoes not get imported when importing phone numbers using a CSV file.

On the Add/Block user dialog, the scroll bar moves to the top of the pageif users are blocked and then unblocked after scrolling down.

Accountability event update is not captured in the operator audit trail. —

A disabled accountability officer does not get displayed in the Details tabon the event dashboard.

On the New Alert page, after selecting an item from the search bar drop-down list, there is a hidden pop-up on the Edit button that prevents iffrom functioning.

The Alert List SDK response displays an incorrect start and end time fora draft alert.

The default severity is not changed for Emergency, Check-In and Reporton the Mobile Alert Settings page.

 | Resolved issues | 18

Page 19: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Description Notes

No line spacing between the body and response options in Sent Alerts. —

Unable to save changes to system-level delivery templates. —

The "Update status on behalf of user" button stays enabled even if arestricted logged -in user can view 0 targeted users.

A SQL and diagnostic log error is seen when viewing a user-level"Delivery distribution by devices" report.

Unable to target Connected organizations on an organization with a UKlocale.

The Import User page shows a spinning wheel if the previous importcontained 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 evenwhen the rule is not enabled.

The pie chart on an event Summary tab does not show the percentage ofusers who responded for disabled and deleted users.

The Distribution List Report displays deleted dynamic lists that were notpart 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 "Show Welcome message"option was removed from theDesktop App settings page.

The Display Name in the head of user details window is not displayedwhen opened from the Add/Block user dialog.

The SDK Alert Tracking report is not doing pagination correctly. —

After deselecting and then selecting a mass device from alert templatesettings, the alert template page does not load.

When toggling between the Bulk Change Status and the single userupdate status, an incorrect count of users is shown in the Bulk Changeuser status dialog.

An advanced search in Sent Alerts with a date range specified does notprovide the correct results.

Status updated once through email for an accountability event isupdated twice in the ARCHIVE_USR_ATTRIBUTE_VALUE_TAB.

 | Resolved issues | 19

Page 20: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Description Notes

The ALERT-TRACKING-DETAILS SDK Response and the "User TrackingReport with Events" contain duplicate records.

The Sent Alerts page is slow on Alerts4. —

Unquoted service path vulnerability. —

 | Resolved issues | 20

Page 21: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Known IssuesThis section 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 listall other known issues, organized based on the product version that first exhibited the issue.

7.6

• There are no known issues in release 7.6.

7.5

Product Package

 

Problem Workaround

Alerts and Alert Templates

Both When using Internet Explorer, if you select to blockand then unblock a user on the New Alert screen, theinterface flickers.

7.4

Product Package

 

Problem Workaround

Alerts and Alert Templates

Enterprise The IPAWS out of the box template does not gettriggered after upgrading to release 7.4 when acustom template that was linked before the upgradeis made not ready or gets deleted.

Make a change in thedatabase to select thenew out of the box alerttemplate to be triggeredby IPAWS alerts.

Integrated Weather Alerts

Enterprise A Connect organization does not get targeted byweather alerts when the Override Geo Informationcheck box is selected.

 | Known Issues | 21

Page 22: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

7.3

Product Package

 

Problem Workaround

Account

Enterprise When creating an accountability event, if youadd custom text to the device options for SMS,accountability officers receive an alert on theirSMS device with the SMS custom device text

instead of the accountability officer event message.

Alerts and Alert Templates

Enterprise The values for Instruction or Response typeplaceholders are not rendered in an IPAWS customalert template.

Both On Safari, the Publish button on an alert Reviewand Publish page falls to the bottom of the screen.

Connect

Enterprise When a response option includes a special character,the desktop app removes any text after the specialcharacter and the response is incorrectly added to the"RE: Others" category in tracking.

7.0.0.2

• There are no known issues in release 7.0.0.2.

7.0.0.1

Product Package

 

Problem Workaround

Alerts and Alert Templates

Both After pressing the browser back button on the newtemplate page, the user lands on last surfed pageinstead of on template manager page.

 | Known Issues | 22

Page 23: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

6.1.8 Patch 90

Product Package

 

Problem Workaround

Reports

Both When the Security Policy for session timeout ischanged, the Activity log and Inbox pages (SignalR)behave inconsistently.

6.1.8 Patch 89

Product Package

 

Problem Workaround

Users

Both An error is displayed when a user search is performedwith the following special characters: ! { } ^

Maps

Enterprise Migration from a release 88 to a release 90 templatedisplays broken breadcrumb in Location Summary ofthe map.

Other

Both Duplicate organizations do not have the same failoverURLs as the original.

Both In the Schedule section, date time issue on set dateand time radio button.

Enterprise Regression > User Attribute > 'Clear for all Users'button is not enabled under 'Bulk Update Values'section in edit mode for Multi-select picklist, Single-select picklist, Check box, Text, Number, Memo, Date,Date-Time, and Geo–location.

Both In FireFox, the Results Based Targeting pop-up is notdisplayed when the bar chart is clicked in DeliveryDistribution by Devices (Chart.)

 | Known Issues | 23

Page 24: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

6.1.8 Patch 88

Product Package

 

Problem Workaround

Alerts and Alert Templates

Enterprise Delivery of alerts on a phone device using the TAS(AtHoc Cloud East) gateway trims the alert body. 

Enterprise Escalation using multi-select picklist should targeteach user as per attribute order.

Enterprise Export to PDF file border extends to next page in caseof Fill count Alert.

Import/Export

Enterprise SDK: Targeting severity based default deliverytemplate is not supported.

Maps

Enterprise The picklist attribute created from the shape layerdoes not add to the count of user attributes.

Users

Enterprise [UAM] The dates specified in min/max range for adatetime attribute are not reflected correctly in SelfService for a VPS where the VPS time is different thanthe system time.

6.1.8 Patch 87CP1 CHF3

Product Package

 

Problem Workaround

Both Operator Password Change page: Clicking on Updatewhen session is timed out, does not show sessiontimeout message on the login page.

 | Known Issues | 24

Page 25: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

6.1.8 Patch 87 CP1

Product Package

 

Problem Workaround

Alerts and Alert Templates

Both Firefox - The counter jumps from 54 seconds to 1 minwhile replaying the recorded audio.

Both Scenario quick publish to all connected organizations:The Review and Publish page does not show newlyconnected organizations.

The alert will still go to allconnected Organizations.This issue does notoccur when editing thealert first. 

Users

Enterprise After granting an operator the System Administratorrole in System Setup, you can no longer editpermissions for that user in their base organization.

Keep all SystemAdministrators in SystemSetup, or create the userin the home organizationbefore grantingSystem Administratorpermissions.

Both EUM Search: Search shows invalid results when thesearched text contains closing curly brace.

Import/Export

Both Import does not support commas (,) in a devicedisplay name.

Both Import does not support attribute names with theperiod (.).

Both Importing users updates the profile with changesfor the geo location point, but does not update thedisplayed location name.

Mobile App

Both The organization logo does not propogate to theMobile App.

Other

Enterprise Browse - Play does not work the first time the useruploads the audio if the file is not fully uploaded.

 | Known Issues | 25

Page 26: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Product Package

 

Problem Workaround

Enterprise Time Zone in PID 3 System Settings is misleading orwrong.

Enterprise GET-DISTRIBUTION-LISTS does not work forEnterprise Administrator.

Enterprise Multiple active sessions for desktop client leads to anincorrect record for "response ignored by the system."

Enterprise Slow performance of Home Page with 500,000 users -Usercounts.

There have been manyimprovements onthe Home Page, butperformance might beslow for 500,000 users.

6.1.8 Patch 87

Product Package

 

Problem Workaround

Alert Templates, Publishing, Inbox, Sent Alerts

Both The Sent Alert Details view does not show theselected details for the phone, including Optionssettings.

Both After an upgrade, an alert template with Emergency/Secure set up for phone does not have the "Selectif the alert has no response options" check boxselected.

Enterprise When targeting mass devices with key option andregular end points selection, the Review and Publishpage appends a comma (,) to the end point displayname. For example: ,ATI_Pole

Enterprise The Review and Publishing process does not validateon Targeting section's readiness when publishing theDraft Alert. 

Enterprise Draft Alert: Unable to save the overwritten defaultvalue of the placeholder. 

Both (Firefox) Alert/Scenario > Personal and MassDevices options: Should not allow applying thecustom text input with length validation error. 

 | Known Issues | 26

Page 27: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Product Package

 

Problem Workaround

Enterprise Placeholders at Org level cannot have same name asPlaceholders at Enterprise level.

User Management and Roles

Enterprise User Attributes: When a shape layer name is modified,the SP creates a new user attribute instead ofrenaming the existing attribute. Work around ismanually running the SP:

1. Log in to AtHoc and navigate to Settings > Mapand Layers > Shape Layers.

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-digit identifier forthe organization in which this attribute should becreated. For example “111111” 

8. Return to AtHoc and navigate to Settings > UserAttributes.

9. Verify that the attribute with the layer name iscreated (attribute should be of type multi-selectpicklist).

10.Check the values for the attribute.The values (andthe number of values) should match the number ofshapes added in the imported shape layer file.

Enterprise Advanced Operator Manager role: an Operator withjust the System Admin role cannot view the details ofexisting operators; throws no authorization error.

Grant Organizationadmin roles to theSystem Admin onSystem Setup (3).

Enterprise Creating attributes from shape layer does not throwerror if a custom attribute already exists of type nonmufti picklist. 

Before uploading shapelayer administratorsshould ensure layername uniqueness toavoid this issue.

Enterprise On running the SP to create an attribute from a shapelayer, the attribute's names are incorrect when morethan one shape layer exists.

 | Known Issues | 27

Page 28: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Product Package

 

Problem Workaround

SDK

Enterprise SDK: Telephony extensions (like Stop Calling optionsor Require PIN/Validation) are not applied. Defaultvalues are used.

Devices

Enterprise Clean MSI: Out-of-the-box devices (aside from MIR3)appear as enabled with an empty device metastore onVPS (3,5,6).

Reports and Tracking

Both If you add the Organization attribute to Report ColumnLayout, the detailed users view hides the attributewhen you click the pie chart.

Import/Export

Both Import/Export: Import fails when the file has only aUsername column or when only the Username columnis selected to import.

Enterprise SDK import: Date time attribute values after importget converted as per the VPS timezone.

 Always import Date-Time values in thesystem time zone.

Other

Enterprise Confusing message on login page when the base URLfor 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 | 28

Page 29: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

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 | 29

Page 30: BlackBerry AtHoc Release Notes 7.6 (OnPrem) · BlackBerry AtHoc APIs now use the login_id to look up users. In version 2.0.0, you must make changes to XSL Mappings that were done

Legal noticesCopyright © 2018 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.

Trademarks

Trademarks, including but not limited to ATHOC, EMBLEM Design, ATHOC & Design and the PURPLE GLOBEDesign are the trademarks or registered trademarks of BlackBerry Limited, its subsidiaries and/or affiliates, usedunder license, and the exclusive rights to such trademarks are expressly reserved. All other trademarks are theproperty of their respective owners. Users are not permitted to use these marks without the prior written consentof AtHoc or such third party which may own the mark. 

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). 

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 notices | 30