Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. 7.19
  4. BlackBerry AtHoc Release Notes 7.19
  5. What's new in BlackBerry AtHoc 7.19

What's new in
BlackBerry AtHoc
 7.19

These release notes contain information about new and changed functionality for BlackBerry® AtHoc® release 7.19. For more information about
BlackBerry AtHoc
 or its related functionality, see the
BlackBerry AtHoc
 documentation here: https://docs.blackberry.com/en/id-comm-collab/blackberry-athoc.

Dynamic hierarchy attributes

A new dynamic hierarchy type of user attribute was added. Dynamic hierarchy attributes are linked attributes that are displayed as a single field in a user profile but contain multiple levels of data. Operators can create and modify dynamic hierarchy attributes and define the levels and values (nodes) in them. When an operator or end user selects a dynamic hierarchy attribute, they can step through a selection of levels within the attribute. When a user selects an attribute node, the next available selections are dependent on the selected node. For more information, see "Create a dynamic hierarchy attribute" in the
BlackBerry AtHoc
 Manage Users
 guide.

Alert templates

  • Alert rule warning
    :If an operator edits an alert template that is currently being used in an active alert rule, and the edits would cause the template to no longer be ready to publish, a message is now displayed informing the operator that their changes will deactivate the alert rule.
  • Inheritable check box
    :The "Inheritable" check box is no longer displayed on the Alert Template screen when creating a template in a suborganization.
  • Location check box
    : In the alert template settings, if the Location check box is selected on the Content tab and the operator unchecks the enable targeting By Advanced Query check box in the Target Users tab and clicks Apply, an error message is displayed and the change cannot be applied.

Management system

  • Attribute value import
    : The help text on the "Import Values" dialog that appears when importing attribute values was improved to provide additional information about reordering values in an existing attribute.
  • Desktop Popup behavior options (Windows only)
    : For Desktop Popup delivery templates, in the Popup Settings section, the option to choose "None" for the Entrance Motion was added. When this option is selected, the alert immediately appears in the selected location of the screen without motion. The Exit Motion option was removed.
  • Fallback authentication option for desktop app
    : The option to fall back to Windows Authentication for the desktop app was added. When selected, Windows Authentication is used if the authentication method for the desktop app is set to "LDAP attribute" and authentication with LDAP fails.
  • User move and organizational hierarchy
    : When a user is moved, their position in their organizational hierarchy is removed. If the user is later moved back to their original organization, their place in the hierarchy is reinstated if the node still exists. However, if the node the user was associated with no longer exists in the original organization, the user is associated with the root node.

AtHoc Account

Target Accountability Officers
: The ability to add Accountability Officers in an account template or event by distribution list, advanced query, and location was added. For more information, see "Add Accountability Officers" in the
BlackBerry AtHoc
 Account
 guide.

AtHoc Connect

Support for Call Bridge
: Call bridge numbers and their passcodes in Connect alerts are now shared across organizations.

Section 508-compliance improvements

508-compliance improvements for keyboard navigation, text-to-speech readability, color contrast, image accessibility and form elements were made in the following areas:
  • Alert Preview and Save page
  • Alert Preview and Publish page
  • Live Map
  • Operator audit trail
  • My Profile page
  • User manager page
  • Operator permissions profile page
  • Profile edit page

API

GET /orgs/{orgCode}/DeliveryTemplates/{DeliveryTemplateCommonName}
: This API was updated to include "None" for the EntranceMotion option.

Mass devices

A new CAP Feed device was added. The CAP Feed device is a collection of multiple CAP feed payloads which can be accessed through a single URL by mass devices such as digital signs.  Operators can use the CAP feed device to render alerts based on the values of CAP payload fields such as category, event, type, urgency, severity, and certainty. For more information, see "CAP Feed" in the
BlackBerry AtHoc
 System Settings and Configuration
 guide.

Desktop App 7.6 (Windows), 2.6 (Mac)

  • Desktop Popup behavior options
    : For Desktop Popup delivery templates, in the Popup Settings section, the option to choose "None" for the Entrance Motion was added. When this option is selected, the alert immediately appears in the selected location of the screen without motion. The Exit Motion option was removed.
  • Fallback authentication option for desktop app (Mac 2.6)
    : The option to fall back to Windows Authentication for the desktop app was added. When selected, Windows Authentication is used if the authentication method for the desktop app is set to "LDAP attribute" when authentication with LDAP fails.
  • macOS Sonoma support (Mac 2.6)
    : Support for macOS Version 14 Sonoma was added.
  • Patent notice (Mac 2.6)
    : The BlackBerry patent notice was added to the About Us page.

Integrations

ServiceNow 2.0.16
  • Log purging
    : Logs are now purged after 15 days.
  • Support for Vancouver
    : Support for the ServiceNow Vancouver release was added.
ServiceNow 2.1.1
Support for domain separation
: The
BlackBerry AtHoc
 ServiceNow integration supports domain separation.
  • BlackBerry AtHoc
     ServiceNow applications now support domain separation.
  • BlackBerry AtHoc
     application-related data such as alerts (incidents), settings (device pairing, AtHoc-related), and diagnostic logs are all domain-aware.
  • Tenants' data in a domain related to AtHoc follows ServiceNow domain separation business logic.

IIM

  • 6.0.0.x Migration to .NET
    : The IIM is made of the following modules: Relay input card, text-to-speech, serial port, interface to
    BlackBerry AtHoc
    , encoders, logging, UI, license manager, and watch dog. Each of these modules were translated into .NET from JAVA. During the migration from Java version to .NET version, the design and architecture of all IIM modules and interfaces were not modified. The features and functionality are unchanged in the .NET version of the IIM from the Java version. IIM was migrated from a Java to a .NET code base on Windows 2012 and 2016 for the Zetron pager integration.
  • IIM version support
    : IIM versions prior to 6.0.X are no longer supported.
  • IIM EOL/EOS
    : Java-based IIM devices are end of support and end of life as of March 31, 2024.
  • .NET code base
    : All IIM devices are now available on a .NET code base.

SMS

SMS vanity codes
: Support for SMS vanity short and long codes by account was added.