Skip to main content
  • EN

Hi,

 

I have an automation workflow that is executed by dropping a file in a target directory. If the file is a ZIP archive (filter action), a hosted FME workbench should be triggered.

 

The workbench expects a path specification (path of the ZIP file) as user parameter. However, in the configuration interface of the automation action I don't have a dropdown to access an output key of the trigger ({file.path}).

 

Is there any configuration to be done in the workbench to handle output keys?

20221209_14-43-0520221209_14-43-1520221209_14-43-2220221209_14-43-40 

Edit: Using FME Server 2022.1.1 - Build 22623-win64

Hello @mowo​, this is very unusual! It appears to be a bug with parameter groups in 2022.1.1. If you move the file parameter out of the group and republish the workspace, you should see the drop down arrow and be able to select the key.

fileparameterIn FME Server 2022.2+, this problem is not present.

Hi @mattmatsafe​, thanks for your feedback.

 

I have since tried further and found out that a custom transformer used as an entry point to the UAV Unzipper workspace was responsible for the problem. I have added a generic reader as a dummy to the workspace - now output keys are also displayed.

Reply


Community Stats

30,162
Posts
114,480
Replies
37,807
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.