What’s new

We’ve added a dedicated Swif browser extension status field to the Device Details > Overview > Device Status section in the WebApp.

This provides at‑a‑glance visibility into whether the Swif browser extension is present on a device, alongside existing fields like Enrollment status and Agent version.

Details

• New status row:

  • A new, read‑only row labeled “Swif browser extension” now appears in the Device Status card on the Overview tab for each device.

• Status values & logic:

  • The UI checks the device’s extension data (e.g. Device.osQueryDeviceInfo.extension) for any Swif browser extension keyword.

  • If a Swif browser extension entry is found → the field displays “Installed”.

  • If no Swif browser extension entry is found → the field displays “Not installed”.

  • This logic is applied per device and is wired to the existing Device Details API payload.

• Behavior when data is missing:

  • When no relevant extension data is available for a device, the row is still rendered with a neutral “no data” style, instead of being hidden, to avoid layout shifts and ambiguity.

  • The field remains non‑interactive and follows the same read‑only behavior rules as other Device Status fields.

• Archived vs active devices:

  • Archived devices show the Swif browser extension field in the same read‑only style as other Device Status entries, consistent with the archived state spec from ST‑7404.

  • No additional actions or controls are exposed for archived devices.

• Performance:

  • The Swif browser extension status piggybacks on existing device data; no extra heavy polling or fan‑out requests were added.

  • Device Details page load performance remains in line with previous behavior.

QA coverage

QA validated the feature against the following scenarios:

• A device with Swif browser extension installed → shows “Installed”.

• A device with Swif browser extension not installed → shows “Not installed”.

• A device with no extension data available → row present with a neutral, explicit state.

• Consistent rendering and read‑only behavior on archived vs active devices.