Connected Commands should be visually identifiable as connected commands in the Resource Commands pane #1191
Quali-Community
started this conversation in
Idea Box
Replies: 1 comment
-
|
Hi, Thanks for submitting this idea. I believe that for most sandbox users, the distinction between resource and connected commands is not important, and there is an advantage in seeing it all without distinction. I believe the solution should be in the API- either have a new API that returns both resource and connected commands, or add type information to the existing GetResourceCommands API Ariel Ariel Benary (Ariel.B) - 01/02/2019 02:56 AM
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, when looking at the commands pane of a resource, there is no way to know if a command is a resource command, or a connected resource command.
This is a problem because when a Blueprint Designer wants to customize the orchestration of a blueprint, it is very likely that he will try to execute the command via "ExecuteCommand" API (instead of the correct ExecuteResourceConnectedCommand) and will run into errors.
Suggested change: Make some visual indicator available in the portal that will identify the command as a Connected Command, with a tooltip that would indicate which resource the command belongs to.
Mock up of how it would look (maybe different icon?)
Attachments:
Leeor Vardi (Leeor.V) - 01/02/2019 12:43 PM
· 4268 ·
Beta Was this translation helpful? Give feedback.
All reactions