Professor6 minutes ago, Mosh said:
Yep exactly. But I'm think more a button that can be bound to a Data Source or a Config Source that uses embedded scripting for discovery/collection. So, for example, today there is on a Data Source definition a button for Test Script. Now imagine if there was a checkbox option on the Data/Config Source to make that button available on a resource where an Applies To expression evaluates to true. And, an option to choose the label for the button. Basically it's the same structure as a data source, but is only invoked by a user via the data source's button on the resource.
Not sure if that all made sense, so here's a mockup ?
Button could appear next to the existing cluster of Refresh, Poll Now and Debug buttons:
