@ParthS007 Thanks for the PR. Can you add a CHANGELOG entry, and maybe a GIF showing the changes before/after?

Sorry - accidentally hit the close button...

How long is the re-run disabled for? So if it's a long running workflow for instance, when does the button get re-enabled?

Note. We are currently in code review, so we will need to save merging this until after 3.7 is released. I would like to see some tests with some long-running actions, as couldn't really tell from video when the button is getting re-enabled.
I will try and do some testing with it, unless someone can expand on the detail of how the disable is working.

Hello @amanda11, thanks for your comments.

How long is the re-run disabled for? So if it's a long running workflow for instance, when does the button get re-enabled?

I am starting to go through the code, I am not familiar with functionalities yet. Please let me know what should be the ideal time for the button being disabled.

For now, The Submit button gets disabled on onClick event on button and it goes back to rerun page. To be more clear, the rerun button is not getting disabled, its the submit button inside the rerun details form.

I can add tests for testing the disabled.

@amanda11 From my understanding, the login button is disabled till a response is received (if success, it redirects anyway, if failed, it re-enables the button). For the action re-run form, I guess the button is disabled after the execution is launched, and since that component disappears, it should be okay (any new instance of re-run action should start with button not disabled).

The idea is to prevent sending multiple requests by double clicking on the button.

The buttons that lead to a redirection response, should be disabled on click (and need not be enabled manually?)
The buttons that wait for an async response should be disabled till the response is received in general.

@ParthS007 This looks great, I had a play with it, and it all looks great. Thanks for the contribution. I went through our manual regression, and all looked good as well.

Could you do an update so that it picks up the master branch changes, this should build it as a 3.8 artifiact, and I can give it another quick spin, and then I'll be happy to merge.

@amanda11 Thanks for your time for reviewing. I rebased the PR, please let me know if I need to add anything else. 👍

All committers have signed the CLA.

@ParthS007 If you get a chance, could you sign the contributor agreement and then I can merge. Thanks so much for the change.

@amanda11 Signed. Thanks 👍

@ParthS007 Many thanks for the PRs, that's all merged and will be available in StackStorm 3.8.