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

Alerting

• Alert response comments: Users can now add comments (up to 300 characters) when responding to alerts by email, SMS, desktop, mobile app, or Self Service. Operators can enable or disable this feature at the template and individual response level, with customizable prompts up to 100 characters. The alert summary displays a Comments column showing the number of comments per response option. The Users tab includes an expandable Comments column for viewing full comments. Advanced reports feature new User Comments columns for easy tracking across all alert reports, with export capability to CSV. Template inheritance and bilingual support with automatic prompt translation are included.

  To use this feature on the desktop app, you must have desktop app release 7.9 (Windows) or 2.8 (Mac) or later desktop release. To use this feature on the mobile app, you must have mobile app release 4.18.1 or later mobile release.

• Automatic inclusion of location map in alerts and events: When a map is used in the Content section of an alert or accountability event or template, the location map is now automatically included by default. Previously, operators had to manually select the "Map Image in Alert" option in the Personal Devices Options screen to ensure the map was included. For email devices, the operator had to verify that the "Include Map" option was selected in the "Email Preview" section of the Preview and Publish screen. Now, when a location map is added in the Content section of an alert or event, the map is automatically included in the alert or event message, simplifying the publishing process for operators. If an operator does not want to include the map, they can uncheck the map option in the Personal Devices Options or Preview and Publish screens.
• Call bridge field validation update: The validation rules for the Call Bridge and Passcode fields when creating alerts was updated. The Call Bridge and Passcode fields are now restricted to accept only numbers (digits), dashes, periods, parentheses, and commas. This is the same validation used for phone number fields, as the Call Bridge field is intended to be used for providing phone numbers and conference codes to allow users to connect to a conference call.

  An alert is not publishable until the call bridge number and passcode are successfully filled out with the correct characters or removed from the response option. If invalid characters are input into the Call Bridge or Passcode fields, an error message appears in red, stating "Invalid Phone Number" for the number portion and "Invalid Number" for the passcode field.

  This change is intended to prevent operators from attempting to input webinar links, URLs, or anything other than a phone number and passcode for a telephone conference as the Call Bridge and Passcode fields are designed to work only with phone numbers.

• Custom placeholder enhancements: Operators can now edit custom placeholder values for scheduled alerts up until the time of publishing. The Content section of a scheduled alert now displays the selected placeholder values, allowing operators to view and edit them. Scheduled alerts that have not been published can be duplicated, and custom placeholder values are editable. Before an alert or event can be scheduled, values must be selected for any custom placeholders. If a custom placeholder does not have a value, the alert is not ready and cannot be scheduled.
• Five new delivery locales added: BlackBerry AtHoc now supports five additional languages for alert delivery: Haitian Creole, Tagalog, Farsi, Bengali, and Thai. Access the new locales in Settings > General Settings >Locale Settings. The new locales can be selected when creating alert and accountability templates. Users can set their preferred language in their user profiles via the BlackBerry AtHoc management system or Self Service. Email and desktop delivery templates are available for all severity levels (High, Moderate, Low, Informational, and Unknown) for the new locales. These new locales are not available for phone or SMS alerts.
• Location pin improvements and clustering on the publisher map: The BlackBerry AtHoc publisher map now displays enhanced location pins with advanced clustering functionality across all map interfaces. A unified common cluster layer intelligently groups multiple data points including distribution list users, ping locations from alerts and events, and alert and event location data. The new clustering system has been integrated across the alert publisher, event publisher, and map settings maps, and all associated layers including alerts, suborganization alerts, account events, suborganization events, incoming alert mobile reports, and distribution lists. FlareCluster library updates provide improved pin labels and descriptive information for location pins. A critical bug in the Plan module has been fixed where location pins previously dropped at incorrect positions when adding locations, applying changes, and saving plans. Location pins now maintain precise placement at user-selected coordinates throughout the entire workflow. Map rendering performance has been optimized with the advanced clustering implementation, delivering consistent clustering behavior across all publisher map components.
• Manual creation of custom map layers: Operators can now easily create custom shape layers on the map. Operators can now create new shape layers directly in the Map Settings without the need to import a pre-configured shape file. This provides a more seamless experience for adding custom map layers to the BlackBerry AtHoc system.

  In the Map Settings, a new "Custom" option was added to the "Add Shape Layer" dialog. Operators can enter a name for the new layer, then click "Create a shape" to open the map and manually draw the desired shapes. Each shape can be named individually. The new custom layer is then saved and becomes available for selection when creating alerts and accountability events or configuring alert and event templates.

  Operators can also edit or remove the custom shape layers after they have been created. The custom layers are displayed in the "Shape Layers" section on the live map and in the Show Layers menu on the publisher map.

  For more information, see "Add a custom shape layer" in the BlackBerry AtHoc Create and Publish Alerts guide.

• Mobile app alert templates honor personal device option settings: When an alert template is published from the mobile app, personal device option settings configured in the alert template are now applied to the alert. Previously, personal device options configured for an alert template were not applied when the alert was published from the mobile app, and default settings were used instead. Operators can now configure personal device options such as delivery templates and device-specific settings in the alert template, and these settings are honored when the template is published from the BlackBerry AtHoc mobile app.
• Private ArcGIS layer support: Organizations can now securely integrate private ArcGIS layers through OAuth 2.0 authentication. A new Layer Authentication Settings section on the Map Settings screen lets you add and manage private layers, while a new Layer Source column identifies them as private. Private layers are also marked with a lock icon on the live map. This enhancement enables organizations to leverage their private ArcGIS data within BlackBerry AtHoc while maintaining security and access controls.
• Resend alerts to users with multiple responses: Alert operators can now resend an alert from the Sent Alerts screen to users with multiple alert responses. Additional users can be added to the resent alert. Users can be added individually, by group, or through advanced query selection. This capability applies to alerts published from alert templates and supports all response types, including custom responses, status attributes, and single-select and checkbox attributes configured as response options. Operators can now efficiently manage alert distribution and target combined groups without creating separate alerts.
• WhatsApp as a personal alert device: The BlackBerry AtHoc integration of WhatsApp as a personal device enables operators to send alerts to WhatsApp users. End users must add a WhatsApp number in Self Service and acknowledge the information-sharing consent disclaimer to receive AtHoc alerts on WhatsApp. After administrators enable and configure WhatsApp for the organization, operators publish alerts through the same workflow as other personal devices and can include responses, locations, and supported attachments. Sent, delivered, and read statuses (where available) appear in BlackBerry AtHoc reporting and CSV exports.

Alert templates

• Improved desktop template styling capabilities: BlackBerry AtHoc has introduced several enhancements to provide operators with a clearer understanding of the Standard and Advanced (XSLT) style format options when working with desktop alert templates:
  • Warning pop-up: When switching between Standard and Advanced (XSLT) style formats, a warning message now appears to inform operators that these are separate styling systems and changes in one format will not affect the other.
  • Help text: Descriptive help text has been added beneath the "Style Format Method" option, explaining the differences between the two formats and their independent nature.
  • Last style format tracking: A new field "Style Format Last Saved As" has been added, displaying which format type (Standard or Advanced XSLT) was most recently saved, helping operators understand which format is currently active.
• Updated system email template themes: The visual appearance of all system-generated email templates have been refreshed to align with BlackBerry's updated corporate branding and color scheme. This enhancement ensures a consistent, modern visual experience across all automated communications. Email templates updated include:
  • Forgot Username notifications
  • Forgot Password notifications
  • Batch Geocoding Notification emails
  • Two-Factor Authentication (2FA) System Verification Code notifications
  • System Delivery template emails

API

• Enhanced organization subscription management with bulk operations: The Organization Subscription API now includes new bulk operations to add or update multiple organization subscriptions in a single API call. A new AddUpdateOrganizationSubscriptions endpoint enables batch processing with array-based payload structure and standardized UTC date formatting. The DeleteUserOrgSubscriptionsByStartDate endpoint enables flexible deletion with optional start date filtering for precise subscription management. Enhanced validation logic prevents conflicting subscription date ranges and ensures proper handling of subscriptions without end dates. Improved diagnostic logging provides better visibility into processing issues and system monitoring. Batch processing scales linearly with recommended batch sizes under 50 subscriptions per organization for optimal performance.
• Web API - OpenAPI documentation enhancement: The Web API was enhanced to integrate OpenAPI documentation generation, providing an improved Swagger documentation experience. The Swagger documentation endpoint was updated to {server-address}/api/v2/docs/OpenAPI/services/openAPIpages/index.html. Entering the previous Swagger URL redirects to the new URL. When switching between services, organization codes are now persistent, enhancing the authorization experience. Improved lock icon states for selected services were added.

AtHoc Account

Event summary Hierarchy tab updateThe Hierarchy tab on the accountability event summary screen was updated to include information about dynamic hierarchy attributes. The Hierarchy tab provides a granular view of accountability event responses based on organizational or custom dynamic hierarchy attributes. Use the drop-down list to select the organizational hierarchy or an available dynamic hierarchy attribute.

Rows on the Hierarchy tab represent the hierarchical levels of the selected organizational or dynamic hierarchy attribute. Columns display response options from the accountability event. Rows are collapsed by default and can be expanded to show deeper levels. The user count for each option is displayed. Hierarchy levels with no responses are displayed with a 0 count.

Click a number in the table to view details about a specific user or users.

When exporting an accountability event summary, the full path of a hierarchy attribute is displayed. For example, /California/San Francisco/Office A.

For more information, see "View accountability event status by organizational or dynamic hierarchy attribute" in the BlackBerry AtHoc Account guide.

AtHoc Geofencing

• New Geofence Viewer Role: A new operator role for users who need limited access to the BlackBerry AtHoc Geofence application was added. Operators with the geofence viewer role can:
  • View geofences and geofence folders within the Geofence Manager and on the map
  • Toggle shape layer visibility on and off
  • View, filter, and export dwelling activity reports Geofence Viewers do not have access to any other BlackBerry AtHoc functionalities or features and cannot perform these tasks in the Geofence app:
    • Create geofences
    • Edit geofences
    • Access the Geofence Audit Log

Browser support

BlackBerry AtHoc release 7.22supports the latest versions of the following browsers: Edge, Safari (Mac), Chrome, and Firefox.

Management system

• BlackBerry AtHoc updated with new BlackBerry corporate colors: BlackBerry AtHoc was updated with a refreshed visual identity that aligns with BlackBerry's updated corporate branding.
• Custom shape layer and individual shape deletion management: Operators can now delete individual shapes or entire custom shape layers from Settings > Map Settings > Shape Layers. If you created an attribute when creating a custom or imported shape layer, the attribute and its values must also be deleted if you want to remove them from the BlackBerry AtHoc system.

  For more information see "Delete a shape or custom shape layer" in the BlackBerry AtHoc Create and Publish Alerts guide.

• Desktop template pop-up settings section improvements: The Popup Settings section on the Desktop Popup delivery template screen was enhanced to improve clarity and visibility. The Popup Behavior section is now visible in both Standard and Advanced XSLT views. This ensures operators understand that popup behavior settings such display size, location, entrance motion and exit motion can be manually configured regardless of style format selection, eliminating confusion about settings retention between Standard and Advanced style formats.
• Shared device identification in device settings: A new "Users Sharing" column in the Settings > Devices > Personal Devices section enables administrators to identify devices used by multiple users. Clicking the user count in the Users Sharing column displays a detailed list of users sharing each device, with options to search by username or name and export the data to a CSV file. This enhancement ensures emergency alerts reach all intended recipients.

Mass devices

The Alert Repetition option is not available for other mass devices or personal devices. The alert repetition interval and duration cannot exceed the alert duration. To view the number of times the alert was repeated, go to Sent Alerts > Advanced Reports to view the publishing lifecycle of the alert.

Mobile app

• Mobile app data privacy disclaimer message: Organizations can now display custom disclaimer messages to mobile app users to support data privacy compliance. A new Show Disclaimer setting in Settings > General Settings > Customization > Mobile App enables you to create a custom message of up to 300 characters. When enabled, users will see a disclaimer dialog during registration that informs them about your organization's privacy policy and data management practices.

  The mobile app disclaimer setting is not inherited from super enterprise organizations to suborganizations.

• Organization logo setting: A new Organization Logo setting in the BlackBerry AtHoc management system lets operators add their organization's logo to the mobile app home screen, alerts, and settings screens. You can upload up to four logo variations:
  • Full logo (light and dark themes): Displayed on the Home screen to represent the connected primary organization.
  • Logo mark (light and dark themes): A simplified logo used in alerts and on the Settings screen.

  For best results, upload both light and dark theme versions of each variation.

  Supported file formats and size requirements:

  • Accepted formats: SVG, PNG, or JPEG
  • Minimum dimensions: 600 × 200 px
  • Maximum file size: 1 M

  Note: For security reasons, uploading an SVG file displays a generic SVG icon in the preview instead of your actual logo. This is expected behavior and does not indicate a problem with the file. Your logo will display correctly in the mobile app.
• Mobile app home screen customization: Organizations can customize branding and information displayed on the mobile app home screen with the new customized content settings available at Settings > Mobile App Settings. These settings enable you to display a greeting on the mobile app home screen that appears below your organization's logo. The Title field supports up to 100 characters, while the Message field supports up to 300 characters. The Message field can be stylized with the formatting controls. Email addresses, phone numbers, and URLs in the Message field are automatically formatted as clickable links. Both suborganizations and standalone organizations can use the Customized Content settings to provide a personalized welcome message and contact information to mobile app users.
• Single sign-on authentication for the BlackBerry AtHoc mobile app: The BlackBerry AtHoc mobile app now supports single sign-on (SSO) authentication. Operators can choose from three authentication methods: SSO, username and password, or smart card. SSO redirects operators to their organization's identity provider for authentication.

  SSO and smart card authentication cannot be used together. Username and password is no longer the default fallback method but can be configured as one.

Roles and Permissions

• Granular geofence folder-level permissions: Administrators can now assign geofence permissions at the folder level for operators with the Geofence Manager, Geofence Viewer, or Organization Administrator role, replacing the previous model where access was applied globally to all geofence folders.

  Geofence Managers and Organization Administrators can have their access to view and manage access to individual geofence folders from the Operator Permissions screen on the operator's user profile page. Operators with the Geofence Viewer role can be granted view-only access to individual folders. If a Geofence Manager role is removed from an operator who also has the Geofence Viewer role, their view access to previously managed folders is automatically preserved.

Section 508-compliance improvements

Self Service

User consent for profile data collection: A user consent mechanism was added to the My Profile page in Self Service to ensure compliance with data protection regulations. This option can be enabled in Settings > General Settings > Customization > Self Service. When this option is enabled, a consent banner appears on the profile page explaining that personal contact information is collected for BlackBerry AtHoc organizational alert communications. Users must explicitly agree to data usage terms by clicking the "Save" button. Users are also informed of their right to opt-out of data collection.

Users

• Customizable operator export columns: Administrators can now customize operator exports by selecting additional columns beyond the 15 mandatory fields, including attributes, organization hierarchy, and device associations. The enhanced export interface enables compilation of comprehensive operator data in a single export, eliminating the need for separate exports. Selected columns are appended after "Last Login date" in the order arranged, while the 15 mandatory operator columns remain unchanged to maintain data integrity.
• Microsoft Entra ID integration: The Microsoft Entra ID (formerly Azure Active Directory) integration provides a solution for automatically synchronizing your organization's user data directly with BlackBerry AtHoc. This integration eliminates the need for manual user management through the User Sync Client and streamlines the process of keeping your BlackBerry AtHoc user data current and accurate. The Microsoft Entra ID integration offers several key benefits:
  • Direct integration with your Microsoft Entra ID environment
  • Automated user data synchronization
  • Simplified user management
  • Reduced manual intervention
  • Enhanced data accuracy
  • Streamlined user provisioning and deprovisioning
  • Support for both attribute and distribution list synchronization

  For more information, see "Manage user synchronization with Microsoft Entra ID" in the BlackBerry AtHoc Manage Users guide.

• Dynamic hierarchy attribute improvements: : Dynamic hierarchy attributes now support up to 13 levels, with up to 2,500 nodes per level and 15,000 nodes total across all levels. Performance improvements for importing, saving, and loading large hierarchies provide greater stability when managing deeper, larger structures.