When you add a "file" manual key to an automation which get run by an automation app, the option is to choose a file already in the resources of FME Flow. It would be nice to have an option for a user to upload a file like what's already available in workspace apps. For a User Parameter "File" the user is able to upload a file which gets used by the workspace the workspace app runs. The same would be ideal for automation apps.
+3- Contributor
- 2 replies
I'm surprised this hasn't been implemented already. It seems like it would be straight forward. Is there any workaround that allows us to upload a .shp file into a user parameter within a custom attribute in the fme automations?
+23- Supporter
- 30 replies
I also stumbled just over this very weird limitation. After i added a manual Trigger to the automation, you can add a manual parameter of type “Choose File”.
This even already provides a UI for file selection in a Flow Automation App. But after struggeling with assigning Access rights to the app token to the File Upload Service and some Resource folders, i noticed that this manual file selection is only able to select a already existing file (and this is also stated in the doc).
I do not see any reason, why at this point the temporary file upload like with a Workspace App with file input should not be possible.
+21- Enthusiast
- 185 replies
This would be a great help to enable the running of automations triggered by a user upload, where more than one workspace needs to run and we do not need or want to store the file; this includes where there are data sovereignty concerns i.e. data cannot be permanently stored (or stored outside of runtime) in the Flow server’s location. In our case for Flow Hosted these things are mostly or all pertinent.
This is currently requiring a look back at the old notifications workflow.
As we have automation parameters already, it would seem logical to expose these to the app where desired.