- BlackBerry® AtHoc® set up and administration overview
- Configure BlackBerry AtHoc settings
- Basic settings
- External events
- Manage system settings
- Specify system settings options
- Add or remove a disclaimer for the BlackBerry AtHoc management system
- Security policy settings
- Define password rules
- Configure password complexity
- Enforce a system-wide password update
- Revoke operator permissions automatically
- Set session timeout and continue session values
- Limit active sessions
- Enable operator login using smart cards
- Require operator login using smart cards
- Enable SSO certificate revocation list checking
- Import a service provider certificate
- Enable CAPTCHA validation
- Monitor system health
- View the diagnostic log
- View geolocation transactions and logs
- Database archiving
- Organizations Manager
- Enable and disable features
- Manage the agents for integrated devices
- Provision applications that can call the web API
- Configure API throttling settings
- View the operator audit trail
- Manage system jobs
- Purge ended alerts
- Manage SMS Opt-In
- Configure device gateways
- Configure devices overview
- Configure devices
- Enable and disable devices
- Set device delivery priority
- Add a device to the user details contact information
- Manage mass communication devices
- Mass device types and categories
- Create a mass device endpoint
- View and edit device details
- Configure Giant Voice devices
- Configure the AtHoc Connect organization network
- Manage the Cloud Services Gateway
- Configure RSS feed information for RSS and Atom content feeds
- Configure XML feed information for mass communication devices
- Configure failover delivery gateways
- Manage a TTY/TDD phone device
- Manage a pager device
- Configure desktop app settings
- BlackBerry AtHoc Customer Support Portal
- Documentation feedback
Purge ended alerts
System Administrators, Enterprise Administrators, and Organization Administrators can enable alert purging by selecting purge criteria for an organization. The purge criteria is the number of days after an alert or event has ended.
Purged alerts and events cannot be recovered.
The purge deletes all ended alerts, events, and their related attachments from the system. Purging ended alerts and events is disabled by default and can be enabled per organization. Suborganizations do not inherit purge criteria from the enterprise organization. Sub enterprise organizations and their suborganizations do not inherit purge criteria from a super enterprise organization.
Any changes made to the purge criteria take effect at the next scheduled purge.
Only ended alerts and events are purged. Drafts alerts and events, templates, manual logs, the operator audit trail, and scheduled and recurring alerts are not purged.
For events, purge criteria are applied after the last alert for the event is published. For example, if an event is for 30 days with one recurring alert per day, and the purge criteria is set to 120 days, then all 30 alerts are purged on the 121st day after the last alert for the event is ended.
- In the navigation bar, click .
- In theSystem Setupsection, clickPurge Ended Alerts.
- Optionally, in theStatussection, click the link in the in theResultfield to view information about the last purge job, including the date of the last purge and the number of alerts that were purged.
- In theSchedulesection, select the purge criteria from thePurge Ended Alertslist. You can select to purge ended alerts and events after 90, 120, or 180 days.
- ClickSave.