Ideas
Create Agents for Connector within Connector interface
I think IdB would be easier to use if when a configuration object was required but did not exist the user could easily create one without loosing their current object entries.
A good example is how the new Azure Portal works... if you need to create an object that requires another object to be created first; when the option appears to choose the second object you always have the option to make a new object (which if significant configuration is needed brings you to a new sub-screen and back to the original when completed).
The general idea is that users usually start off with a goal in mind and start down that track ("I need a connector!") and along the way they discover detail ("Oh, I also need an Agent, dam it!"); and ensuring the product permits that kind of thinking makes the product far more natural (and so easier) to use.
Unfortunately I don't know enough about web gui's to know how this can be easily accomplished. :/
Answer
Thanks for the feedback, Michael.
In the particular case of case of creating a connector with no available agents, the UI does direct you to create an agent, however it doesn't direct you back to the connector afterwards.
This would be quite difficult to implement currently, but we are planning an overhaul to the UI in an upcoming release, so I will add this to the list of desirable workflows that it should support.
Thanks for your message Curtis.
You are correct, it does present a link for you to go do it; but alas as you mentioned, no way to return.
Please keep me updated as you guys work on the new GUI... I am genuinely interested to see what frameworks there are and what we end up using in this new world of things like single page applications and such like.
Customer support service by UserEcho
Thanks for the feedback, Michael.
In the particular case of case of creating a connector with no available agents, the UI does direct you to create an agent, however it doesn't direct you back to the connector afterwards.
This would be quite difficult to implement currently, but we are planning an overhaul to the UI in an upcoming release, so I will add this to the list of desirable workflows that it should support.