You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commonly a filename occurs two or three times in a flow because it as used as an output, then used as an input, and then we delete it if we don't need it anymore.
Repeating the code that generates filenames is asking for trouble, so it should be possible to make a step that writes a computed value into a local variable.
An easy way to implement local variables would be to add a Map<String,Object> to the context object, so you could write something like
local['tmpfile']
to access the value.
The text was updated successfully, but these errors were encountered:
Commonly a filename occurs two or three times in a flow because it as used as an output, then used as an input, and then we delete it if we don't need it anymore.
Repeating the code that generates filenames is asking for trouble, so it should be possible to make a step that writes a computed value into a local variable.
An easy way to implement local variables would be to add a Map<String,Object> to the context object, so you could write something like
local['tmpfile']
to access the value.
The text was updated successfully, but these errors were encountered: