Set FilePath for FME_SHAREDRESOURCES_TEMP

Yep, FME does it all automatically :)

As an example, this is how I tend to do something similar:
 

1. Test for the existence of an FME Flow parameter
2. If it exists, we’re on Flow, so set the output attribute to the value of the temp resource folder
3. If it doesn’t exist, we’re on Form, so either manually specify the temp path (AttributeCreator) or use the TempPathnameCreator. Note the latter location will be deleted one FME finishes running

Sometimes overriding the Flow parameter value is a cleaner approach. I do find its a bit hidden and people will often miss that its set there when running on Form (of course you can mitigate this by publishing it or through documentation).

In other words, a few ways you can achieve a similar outcome

Just reading this posting because I have some issues writing to FME_SHAREDRESOURCE_TEMP, where I am getting 

Undefined macro `FME_SHAREDRESOURCE_TEMP' dereferenced in file `C:\Windows\TEMP\fmeengines\localhost_Engine1\FME_1743423682605_780'

but concerning the usage of either Form or Flow, does that not simply require to define the parameter within the workbench?