Devices¶

The Devices module has the widest surface area in the current portal capture. This section groups the validated device pages into operational tasks for summary review, registration, configuration, command execution, monitoring, custody management, and device administration.

1. Review the Device Summary Dashboard¶

Purpose: Start from a high-level view of the device estate.

Route / context: /device/device-summary

Steps:

1. Open Devices from the top navigation.
2. Select Device Summary.
3. Review the summary counts or high-level indicators.

Expected result: The dashboard loads and provides a baseline view of the device estate.

2. Review the Device List¶

Purpose: Browse registered devices in a detailed list view.

Route / context: /device/device-list

Steps:

1. Open Device List.
2. Search for the device identifier or browse the table.
3. Use the list as the main entry point for device investigation.

Expected result: The device list loads with device-level operational detail.

3. Open Device Row Actions¶

Purpose: Inspect the per-device actions available from the main device list.

Route / context: /device/device-list

Steps:

1. Open Device List.
2. Locate the device row you want to manage.
3. Click the row action button.
4. Review the menu before choosing the next workflow.

Expected result: The row-action menu opens for the selected device.

Observed live actions: View, Edit, Delete, Request Repair, Prepare Arming..., Mark Returned, Mark for Maintenance, and Open Lock.

4. View Device Detail¶

Purpose: Open the detailed device workspace for a selected device.

Route / context: /device/device-list -> /device/device-detail/:id

Steps:

1. Open the device row action menu.
2. Select View.
3. Wait for the detail page to load.
4. Review the device tabs and the action controls shown on the detail page.

Expected result: The portal opens the device detail page for the selected record.

Observed live tabs: Device Location, Commands, and Custody History.

5. Edit a Device¶

Purpose: Update the registration metadata for an existing device.

Route / context: /device/device-list -> /device/edit-device/:id

Steps:

1. Open the device row action menu.
2. Select Edit.
3. Review the editable device fields.
4. Update the required values.
5. Use Update when ready.

Expected result: The device edit form opens for the selected record.

Observed live fields include: Model, Configuration, and Device Group.

6. Start Device Arming Preparation¶

Purpose: Begin the device arming-preparation workflow without committing the action.

Route / context: /device/device-list -> row actions -> Prepare Arming...

Steps:

1. Open the row action menu for the target device.
2. Select Prepare Arming....
3. Review the confirmation dialog.
4. Use Confirm to proceed or Cancel to stop.

Expected result: The portal opens a confirmation dialog for arming preparation before any state change is applied.

7. Review Device Groups¶

Purpose: Confirm the current device grouping model.

Route / context: /device/device-group

Steps:

1. Open Device Group.
2. Review existing groups.
3. Confirm grouping entries are visible and manageable according to role.

Expected result: Device groups are listed and usable for administrative organization.

8. Add a Device¶

Purpose: Register a new device in the system.

Route / context: /device/add-device

Steps:

1. Open Add Device.
2. Complete the required registration fields.
3. Save the record.
4. Confirm the device is available in the device inventory afterward.

Expected result: A new device is created successfully.

9. Configure Devices¶

Purpose: Apply configuration logic to devices or groups.

Route / context: /device/configure-devices

Steps:

1. Open Configure Devices.
2. Select the target device or device group.
3. Apply the required configuration profile or values.
4. Save the configuration change.

Expected result: The device configuration screen loads correctly and supports configuration assignment.

10. Review Device Configuration Actions¶

Purpose: Inspect the reusable actions available for saved device configurations.

Route / context: /device/device-configurations

Steps:

1. Open Device Configuration from the left navigation.
2. Locate the saved configuration you want to manage.
3. Open the row action menu.
4. Review the available configuration actions.

Expected result: The configuration row menu opens for the selected record.

Observed live actions: Configure, Clone, and Delete.

11. Manage Device Models¶

Purpose: Maintain the model definitions used for device registration and classification.

Routes / context:

• /device/add-device-model
• /device/device-models
• /device/edit-device-model/:id

Steps:

1. Open Add Device Model to create a new model definition.
2. Open Device Models to review existing entries.
3. Use the row action menu to manage an existing model.
4. Select Edit when a model definition needs to be updated.

Expected result: Model creation, model-list review, and model editing are all accessible.

Observed live row actions: Edit and Delete.

12. Manage Device Groups and Configuration Inventory¶

Purpose: Maintain reusable group and configuration structures.

Routes / context:

• /device/add-device-group
• /device/device-configurations

Steps:

1. Open Add Device Group to create a new grouping record.
2. Open Device Configurations to review reusable device configuration entries.
3. Confirm both screens load without runtime errors.

Expected result: Group and configuration administration pages are available for operations and setup work.

13. Import Devices¶

Purpose: Load multiple devices through a bulk import flow.

Route / context: /device/import-devices

Steps:

1. Open Import Devices.
2. Review the import template or file-upload controls.
3. Prepare the input file according to the expected format before upload.

Expected result: The import screen loads and is ready for controlled bulk onboarding.

14. Send a Device Command¶

Purpose: Trigger an operational command against a target device.

Route / context: /device/send-command

Steps:

1. Open Send Command.
2. Select the target device or device group.
3. Choose the command type.
4. Complete the command input.
5. Submit the command when ready.

Expected result: The command form loads and supports a controlled command-submission flow.

Observed live command types in the selector: Set Trusted Number, Stop Sending Positions, and Open Lock.

15. Review Command History¶

Purpose: Check previously issued device commands and their outcomes.

Route / context: /device/commands

Steps:

1. Open Commands.
2. Review command entries and their states.
3. Use this page when confirming whether a command was already issued or completed.

Expected result: Historical command activity is visible and traceable.

16. Review the Device Map¶

Purpose: Observe device location information spatially.

Route / context: /device/device-map

Steps:

1. Open Device Map.
2. Confirm the map canvas loads.
3. Review device markers or other map overlays.

Expected result: The map view renders successfully and exposes location-oriented device context.

17. Review Device Monitor¶

Purpose: Inspect device telemetry or state from a dedicated monitoring view.

Route / context: /device/device-monitor

Steps:

1. Open Device Monitor.
2. Confirm monitoring information is visible.
3. Use the page to assess current device state and recent activity.

Expected result: The monitoring workspace loads and provides live or near-live device information.

18. Review Transfer Custody¶

Purpose: Track or manage device custody movement between operational owners.

Routes / context:

• /device/transfer-custody
• /device/add-transfer-custody

Steps:

1. Open Transfer Custody to review current custody-transfer records.
2. Open Add Transfer Custody to initiate a new transfer.
3. Confirm the list and creation screens both load correctly.

Expected result: Custody-transfer administration is available for controlled device handover workflows.

19. Remaining Validated Gaps¶

The following device workflows still need dedicated capture before they should be documented as full completion procedures:

• delete device to completion
• request repair to completion
• mark returned to completion
• mark for maintenance to completion
• delete device configuration to completion
• delete device model to completion
• distinct disarm or switch-off flows, if they are enabled for this environment