I started protecting my workspaces with passwords because they sometimes contain sensitive informations (like embedded connections) and I noticed a weird issue when I uploaded them on FME Flow 2024.2.5.
I use the parameter FME_MF_NAME in different places, for naming different outputs. As soon I added the password, the workspaces started to fail.
Notably I have one workflow which requires launching multiple workspaces sequentially, the main one launching the others with FMEFlowJobSubmitter.
All the protected workspaces have their FME_MF_NAME overwrited by the FME Flow.
All the logs show the same message upstream, something like this:
FME Configuration: FME_MF_NAME is 'wb-tmpXXXX'
Which is weird because the parameter of the workspace is correctly set with a message like this:
`--FME_MF_NAME' `myworkspacename.fmw'
Using the parameter FME_MF_NAME during the job gives 'wb-tmpXXXX' instead of ‘myworkspacename.fmw'.
I can find workarounds but it is annoying and I am wondering if it is a bug or a normal behavior due to password protection.
Kind regards,
Alexandre