I believe there is the possibility to configure user parameters in a way that they take a local path for in/output and when they are going to be published the provided alternative for the FME Flow resources path is used.
I cannot find my bookmark on how to do this and did not come to anything useful when searching the net.
Does somebody have a tutorial on how to configure the user parameter that it uses the local resources when run in FME Form and the FME Flow resources when run in Flow?
Page 1 / 1
You can create a parameter that uses a python script that test if you have engine names. FME can only find engine names if the workbench is run on FME Flow. Here is the most simple python way:
VarLocal = "ANiceLocalPath"
VarFlow = "ANiceFlowPath"
if FME_MacroValues.get('FME_ENGINE', '') == '':
return VarLocal
else:
return VarFlowedit: if you even have different engine names between your test FME Flow and Prod FME FLow you can use those names to also change the path between Flow Test and Flow Prod. We use this all the time.
Are you looking for Deployment Parameters? https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Transformers/!Transformer_Parameters/Deployment-Parameters.htm
To use a different value for the parameter when the workspace runs from FME Workbench than when it runs from FME Flow, select Use Local Value in the Create FME Flow Deployment Parameter dialog, and enter the value to use in FME Workbench. To set a local value after a deployment parameter is created, right-click on it in the Navigator and select Set Local Value.
Local values are saved with workspaces, but do not deploy to FME Flow. Local values are indicated in the Navigator with [local value] appended:
Yes,
But I will keep the Python
If a parameter is pointing to a resource folder on FME Flow you can also just set the FME Flow Parameter - FME_SHAREDRESOURCE_DATA to point to a local folder when running on FME Form
