I want to raise the topic of user feed back. Whilst this can be a number of different forms, one particular that comes up is when clicking a custom button.
Use Case : User clicks a custom button, some automate runs, but the result can be passed back to the users browser.
Example : Select a VM, click custom button, automate generates the RDP details for the VM and generates the file for download, posting the link back to the user.
Example : Select a VM, click custom button, automate generates the required URL for a bespoke remote control software, that is posted back to the user in a new window.
I think this request is slightly different to those that request constant feed back to the user, this request is a lot simpler in that user clicks button, automate runs, and returns html back through the web server to the users browser, presumably targeting a frame, or window etc…I would expect the browser to wait for the result to be returned from automate, support normal browser timeout defaults.
thoughts? @dclarizio and others… any other use cases to help?