I found that FFASTRANS 8.2.2 interprets the absence of source file as the error.
But in my case it's not an error, but normal state. My workflow moves at the last step the source to one or another folder. It depends on workflow conditions. I use Command node with command like that:
Thank you both for your feedback. Some nodes require an input source file to work, others don't. Currently, FFAStrans does not distinguish between the two and requires all nodes to have access to a valid source file. Obviously it breaks some workflows when the source is moved without updating the %s_source% variable. Now, the only way that that's gonna happen is if you use the "Command executor" to move the source file. This is exactly the reason why you can update the %s_source% variable from within that node; in order to not break your workflow. But, maybe requiring a source file was a bad idea after all. You think it should be removed again?
Yes, I think source file input in all nodes not needed. Some nodes can manipulate data without source files. For generate texts, execute commands, populate variables, check values or something else.
In my workflow I watch for file and change filename in some situations in command executor. After that I check if original file exists. And if not - dismiss job. Changed filename may be watch in next iteration. So, in some situations original source file not exists and it's normal.
Hi sebird, thank you for using FFAStrans and welcome to the forum!
%s_source% refers to the input file(s) for the node. It gets updated every time a node change the it. There are three ways for the user to update this variable manually; either by using the "Populate variables", "Command executor" or "Generate text file" nodes. In the two first nodes you simply set the FULL path of the new source variable in the input field. In the "Generate text file" node you just check the "Set text file as source" option.
