IF you have access to the External Component (with Adv. Automation Option). A script can be used to create subdirectories. The call to the External Component would be executed early in the workflow, then used by Save.
Example would be a script (Make Directories) that takes a list of directories to create.
Then execute the script call to make directores based upon job name at submission: <<MIS Order ID>> <<Customer name>>.
Then the Make Directories script would get parameters like:
C:\Customer Repository\$FFwfJob.jobName$\Original Files
C:\Customer Repository\$FFwfJob.jobName$\Preflight Results
C:\Customer Repository\$FFwfJob.jobName$\Print Ready Files.
The problem with the Save node no being able to use a FFCore variable in the save name is fixed in 6.0.3. The folder needs to exist before the save node is invoked. The creation of the folder can be done with the external node. Below are screensnaps of the WF and Hotfolder. Attached is the script for creating the folder.
I created a very simple MAX workflow. The input CSV file uses 4 columns, 2 of which are standard fields:
...and two custom fields:
The workflow merely takes each given file, uses "VERT_OFFSET" and "HORIZ_OFFSET" in a Resize node, then saves the altered PDF.
I configured the Save node's file location to be "$FFFolder Name$\FFCore_Output", with the assumption that the subdirectory "FFCore_Output" wouldn't exist at the time of submission. My expectation was that FreeFlow Core would create this directory.
I tried this workflow, and get the error "The save device location is invalid." if the subdirectory "FFCore_Output" doesn't exist at time of submission. If I manually create that subdirectory before submission, the jobs process without issue.
Is this a limitation of the FreeFlow Core application, or am I running into a permissions issue?
Any relation to this line of the release notes (v6.0.3): "Fixed issue that was allowing the Save node to be configured with a process variable location"?
Solved! Go to Solution.