You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current work flow for creating commands in the Build tab and executing them in the Agents tab works successfully.
When series of commands are to be executed, the flow is:
Create the command in the Build tab
Wait for the command to appear in the transcoder log
Select the command in the transcoder log to display the Agents tab
Enter the agent ID(s) on the Agents tab
Select Manage Agents option
Select the Send Raw Command option, which has the new command populated
Select Manage Agents option again
Select Print Agents Report option
Repeat from 1 for the next command
This requires frequent switching between the Build and Agents tab.
Alternately, all the commands could be created at once in the Build tab. In this case, once the commands are created, the flow would start at step 3 above and be repeated from there for each command. But the same amount of switching is still needed.
The Cbor string could be copied from the Transcoder log for each command to be executed and stored somewhere. The flow in this case would be to display the Agents tab, enter the Agent(s), and proceed from step 5 above, pasting the command to be executed in the Raw Command field (step 6). Executing additional commands would proceed from step 6. This option requires less switching between the Build and Agent tabs, but it sometimes requires some effort to copy the command in the transcoder log without bringing up the Agents tab, which is the expected behavior, but is not always wanted. The user is also responsible for pasting the correct string in the correct sequence.
Developing a macro could be developed to contain all the steps wanted, but a macro may not always be wanted and it brings its own set of additional steps to be executed.
Could multiple commands be selected from the transcoder log? Perhaps with a column to enter an execution sequence number for each command? Or display the transcoder log IDs on the Agents tab and let the user select the command to execute. The user would be expected to know what commands the IDs represent. The user would like to reduce the number of switches between tabs and the re-entering of the agent IDs.
The text was updated successfully, but these errors were encountered:
The current work flow for creating commands in the Build tab and executing them in the Agents tab works successfully.
When series of commands are to be executed, the flow is:
This requires frequent switching between the Build and Agents tab.
Alternately, all the commands could be created at once in the Build tab. In this case, once the commands are created, the flow would start at step 3 above and be repeated from there for each command. But the same amount of switching is still needed.
The Cbor string could be copied from the Transcoder log for each command to be executed and stored somewhere. The flow in this case would be to display the Agents tab, enter the Agent(s), and proceed from step 5 above, pasting the command to be executed in the Raw Command field (step 6). Executing additional commands would proceed from step 6. This option requires less switching between the Build and Agent tabs, but it sometimes requires some effort to copy the command in the transcoder log without bringing up the Agents tab, which is the expected behavior, but is not always wanted. The user is also responsible for pasting the correct string in the correct sequence.
Developing a macro could be developed to contain all the steps wanted, but a macro may not always be wanted and it brings its own set of additional steps to be executed.
Could multiple commands be selected from the transcoder log? Perhaps with a column to enter an execution sequence number for each command? Or display the transcoder log IDs on the Agents tab and let the user select the command to execute. The user would be expected to know what commands the IDs represent. The user would like to reduce the number of switches between tabs and the re-entering of the agent IDs.
The text was updated successfully, but these errors were encountered: