Webinterface

[knk]

Hey @emcodem!
I understand your challenges completely. It's not easy to "please" everyone and fit every use case.
The "refresh" was a bad call, obviously it would only fit my scenario and probably no one else's.

My point was/is, for those who are technically "less inclined", and if they are many for some reason, the Start button not providing feedback can be a pain, because if you do make a double click in a heavy WF (with dozens or even hundreds of files listed), it's easy to create a mess. Even very light WF's can create a mess if they don't give us enough time to cancel a double or triple submission.

So my honest suggestion is, for consideration, to have the Start button change its state after clicked, like to an unclickable "Job Started" and offering something like a "<<back" link to reset it to a clickable state again.
Even better (and now just dreaming ) to have a custom pop-up message per WF, that could appear as a window/form/mask and called by a variable or something after user clicking Start Just shooting things out there!

All the best to you guys! Have a wonderful weekend

[emcodem]

Got to mention that i am always happy when i get some inputs from you @knk, thanks a bunch!

My point was/is, for those who are technically "less inclined", and if they are many for some reason, the Start button not providing feedback can be a pain, because if you do make a double click in a heavy WF

In theory it currently should not be possible to unintentionally double submit but the mechanics around that are far away from being perfect so i believe you have issues with it without a doubt - and yes of course we also want to be compatible with "less inclined" users interactions

to have the Start button change its state after clicked, like to an unclickable "Job Started" and offering something like a "<<back" link to reset it to a clickable state again.

Thats one of my thoughts, i do that at work in a similar but much simpler tool and the users do use it very much actually, its a button saying "reactivate" and the submit btn goes greyed out. Of course it also depends or better is caused by the way i designed the corresponding workflow form - this can or can not drive the users into the wish to re-use the current form inputs and instead clean the file list for a new job submission.
Of course we want to support both cases, complete restart and re-use current form

Even better (and now just dreaming ) to have a custom pop-up message per WF, that could appear as a window/form/mask and called by a variable or something after user clicking Start

Such things are absolutely thinkable when i finished what i said before - the possibility to store job submit form settings along with the ffastrans workflow json.
Question: what would you let the user know in such a "post-submit" window?