johnnyq
c76882f3d2
Add RMM alerts opening tickets: a provider's Edit picks which alerts open tickets (errors, errors and warnings, or every alert) and their ticket category, and the new RMM Alerts cron job looks every minute - a new alert on a device of a linked client opens a ticket on its client and asset with priority by severity, the same alert again goes on its open ticket and reopens it if resolved, and a cleared alert notes and resolves its ticket unless someone has written on it, it was moved to another status or another of its alerts is still open; the first look after turning alerts on, or the provider back on, takes open alerts as known, as does an alert raised before its device came into ITFlow; Tactical alerts read from PATCH /alerts/ and GET /alerts/id/ with no setup in Tactical; open alerts and their tickets on the asset's RMM card, an Alerts column on the providers list, the RMM ticket source on the ticket page and list, and the new-ticket address email; database 3.6.8 adds the alert columns to rmm_providers and the rmm_alerts table; 26.11.9 changelog entries
2026-11-13 18:33:38 -05:00
..
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
Add RMM alerts opening tickets: a provider's Edit picks which alerts open tickets (errors, errors and warnings, or every alert) and their ticket category, and the new RMM Alerts cron job looks every minute - a new alert on a device of a linked client opens a ticket on its client and asset with priority by severity, the same alert again goes on its open ticket and reopens it if resolved, and a cleared alert notes and resolves its ticket unless someone has written on it, it was moved to another status or another of its alerts is still open; the first look after turning alerts on, or the provider back on, takes open alerts as known, as does an alert raised before its device came into ITFlow; Tactical alerts read from PATCH /alerts/ and GET /alerts/id/ with no setup in Tactical; open alerts and their tickets on the asset's RMM card, an Alerts column on the providers list, the RMM ticket source on the ticket page and list, and the new-ticket address email; database 3.6.8 adds the alert columns to rmm_providers and the rmm_alerts table; 26.11.9 changelog entries
2026-11-13 18:33:38 -05:00