Skip Navigation

Known issues

This section lists known issues in
BlackBerry AtHoc
releases.

7.17

Jira ID
Description
Workaround
Users
IWS-65685
When importing users with geo addresses, the batch geocoding postprocessor system job fails and the import remains in an "In Progress" state.

7.16

Jira ID
Description
Workaround
Alerting
IWS-66109
If there are more than 9 response options, only the first nine are displayed.

7.14

Jira ID
Description
Workaround
Alerting
IWS-58156
Alerts triggered from the mobile app do not display the icons on the map that are defined in the mobile event rules.
IWS-61074
Tabbing does not navigate correctly in alerts sent to the Desktop app using the default template.
IWS-62371
When an initial attempt to send an SMS alert fails, but then is successful upon retry, the user tracking report continues to display an error message.
External event alert
IWS-58065
Alerts are not triggered for external events when placeholders are added to the alert title in the out-of-the-box External Feeds Template. The External Feeds Template contains a [BFSTitle] placeholder by default. Adding additional placeholders to the title field can cause the title to have more than the maximum number of characters.
Do not add additional placeholders to the title field.
IPAWS
IWS-58653
IPAWS COG to COG alerting does not function.
Reporting
IWS-62851
The Alerts Usage report should not count silent ping alerts.

7.9

Jira ID
Description
Workaround
Alerting
IWS-61005
The Respond & Close button is not displayed correctly in an alert published using a legacy template with more than 4 response options.
IWS-61053
On the
BlackBerry AtHoc
desktop app, when tabbing using a keyboard, navigation on alert content is not in a sequential order and the user is unable to navigate through all response options.
Desktop App
IWS-56942
The the CheckUpdate payload for the desktop app should be updated to remove unused nodes.