Summary
Starting with version 1.0.2403, I can select multiple devices in the device list and assign them to a customer, add tags, or schedule maintenance, delete them, and run an automation. This is the foundation I’d like to build upon. What I’m still missing in my day-to-day work is feedback for each device and the handful of actions for which I still have to click through device by device: deploying software, applying patches, restarting devices, and resetting alarms.
What octoja can do today
In the device list, on a selection (three-dot menu → Multiple selection):
On an individual device: Terminal, Remote Desktop, Files, Create a report, Wake up device, Change device type, Agent settings, Download logs.
However, a bulk run of an automation only returns {startedCount: N} — I then have to use GET /api/automations/{id}/runs to retrieve the information about which devices ran the automation and the results individually.
Related entries that already exist here: “Multiple Device Selection for Assignment” (implemented), “Multiple Selection Similar to Devices in the Dashboard” (in progress), and “Quick-Action Menu” (under review), which suggests restart, shutdown, Wake-on-LAN, and a terminal command for individual devices. My point is the next step: applying the same actions to a selection, with a clear result.
What I specifically miss in octoja
1. Distributing software to the selection
Automation has been available since version 1.0.2403, but software distribution has not. I’ve created 47 custom packages (ScreenConnect per client company, VIPRE per location). Rolling them out to a random selection of devices currently requires the workaround of building a configuration package or a rule—for a one-time rollout...