Flow app 'OK' button greyed-out after you attempt to run and have a parameter error
Hi all, I am running FME Flow 2023.1 and have a flow app with a handful of mandatory parameters which the user enters and clicks 'OK'.
If the user does not enter all parameters and attempts to run the app, they get a 'Please supply a list for parameter' error.
If the user re-enters all the parameters and attempts to run the app, the 'OK' button is now greyed-out. The user must refresh the page and start again.
is there a reason for this behaviour?
It's pretty annoying to have the user re-enter all parameters again if they have forgotten to enter a mandatory field.
I tried to reproduce this issue with FME Flow 2023.1 b23619 and was unable to. Would you mind sharing your workspace or and fsproject file for us to investigate further? You could also create a case if you don't want to share your files on the Community.
I tried to reproduce this issue with FME Flow 2023.1 b23619 and was unable to. Would you mind sharing your workspace or and fsproject file for us to investigate further? You could also create a case if you don't want to share your files on the Community.
Thanks!
thankyou! I have created a case and sent the workspace.
Case number C694066
Hi There, I might have run into related trouble. I created an Automation, and added a new workspace to run to the setup. When configuring the new action, everything goes smoothly. However, saving the Automation results in the same error and the automation seems to be blocked forever. Selecting another menuitem like Run Workspace, clears the blocking but results in loosing all changes to the Automation.
As an alternative, one can try start the Automation, which also will release the block.
Still not having any clue on what it means, to supply a list. I just want to specify one file and no more.
Aha, now I see. It helps to tell FME it needs only one file for a parameter. As in:
However this prevents the error from popping up, yet does not change the undesirable blocking behavior.
Hello @helmoetz ! I’m sorry to hear you’re running into a similar problem. What version and build of FME Workbench and FME Flow are you using? Many of the issues related to the previous post were resolved in 2023.2 and 2024.x releases. Upgrading may solve your issue, too. Thank you!
Hi @sanaeatsafe we are using FME Flow 2022.2.3 (through a Citrix configuration). Thanks for asking. It's not that the issue is blocking me any more….
Hello @helmoetz ! I’m sorry to hear you’re running into a similar problem. What version and build of FME Workbench and FME Flow are you using? Many of the issues related to the previous post were resolved in 2023.2 and 2024.x releases. Upgrading may solve your issue, too. Thank you!
The bug is also present in FME Flow 2023.2.3. Changing the published parameter helped but the bug is not resolved in that version.
