Skip to content
← SMART iQ Embedded Experience

Give us feedback about the SMART iQ embedded experience system.

'Enhance Command Logs to Clearly Identify Active and Stopped Persistent/Scheduled Commands' has been merged into this idea

SMART iQ Embedded Experience: Remote Management

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Enhance Command Logs to Display Specific Setting Changes

When commands are pushed through SRM to change device settings, the Command Logs currently display generic statuses like "Command Sent" or "Command Executed." However, they do not specify which settings were modified or what values were applied. This makes troubleshooting and audit tracking difficult.

Proposed Feature: Update the Command Logs to include detailed information about the settings or configurations that were changed as part of the command execution. For example:

If a setting like “Device Name” or “Screen Timeout” is changed, the log should display the old value, the new value, and the specific setting modified.
Include any additional parameters or configurations applied through the command.

Benefits:

Improved Troubleshooting: Easily identify which settings were changed, helping diagnose and resolve issues faster.
Enhanced Transparency: Clearer record-keeping for audit purposes.
Increased User Confidence: Reduces the need for guesswork when analyzing command outcomes.

1 vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Report

    The current Command Logs in SRM lack clear indicators for determining which persistent or scheduled commands are currently active and which have been stopped. This makes managing active schedules or recurring commands cumbersome and can lead to confusion, especially in troubleshooting or reviewing tasks.

    Proposed Feature:
    Add visual indicators or a dedicated column in the Command Logs to clearly display the status of persistent and scheduled commands, such as:

    Active: Commands that are currently running or scheduled.
    Stopped/Inactive: Commands that were deactivated or no longer recurring.
    Include additional metadata, like the schedule frequency (e.g., daily at 7:45 AM) and the last execution time for active commands.
    Benefits:

    Better Management: Simplifies tracking of ongoing or scheduled tasks for administrators.
    Efficient Troubleshooting: Quickly determine if a command is active or inactive without manually searching through schedules.
    Improved Usability: Provides a cleaner overview of scheduled tasks and ensures no missed actions due to overlooked inactive commands.