Some time ago for demonstration purposes I have done not exactly this but something similar. In that case the task of creation max file on the fly and than using it have been acomplished by creating two workflows. One of this workflows at step one generates the preflight report in xml format, at step two create the max file by xslt conversion of this xml report and sent the max file for other actions to the next workflow hotfolder.
I am struggling with exactly the same issue - we need to create manifest on-the-fly using script activated for hotfolder. An answer to this would be highly appreciated. Many thanks.
Regarding to this matter Jyri Salmi from level 2 contacted Solution and Workflow Analyst Marko Liukkonen who then phoned me. Now the situation is, that Marko is no longer working with Xerox: Who could I ask for help in this matter now?
Sunny greetings from Finland,
Thanks Javier and sorry for the not so informative description ;-)
We´ve done max workflows using csv-files, so that´s ok. What I would like to do, is to create a csv from a pdf-file when dropped to HF and use MAX with this csv. In csv I´d like to have columns for the file name and then generate a few static data columns. I´m a real novice in scripting (but eager to learn!), and don´t have a clue how to do this...
Not sure the right level of detail for an answer. I would suggest that you engage the professional services group if you are looking for more in depth information.
In any case, here's a bit of a high level answer.
FFCore hot folders support use of manifests (csv files) to drive production. When a manifest is received, FFCore will parse the data columns in the csv file per the hot folder configuration and submit the job to the selected workflow (or use the routing rules to automatically select a workflow for the job in each manifest row)
The manifest fields are configured in the Hot Folder Setup tab.
We have a few "Standard fields" which are used to control job submission from the manifest.
You can also add custom fields so set additional variables with information from the manifest
After a manifest is parsed, FFCore will use the configuration in the Workflow Destinations to automatically select a workflow
If you enable hot folder scripting then FFCore will execute the confired script before any other processing is done by the hot folder.
The configuration itself is pretty straight forward
Under the hood FFCore will concatenate the path to the script along with the parameters and execute the script as if it was executed from the CLI. There are no requirements on the script itself. If you can get it working from the CLI then you can configure it to execute when a file is dropped into the hot folder. The only requirement that the script output a valid job file and place it at the location defined in the $$out$ variable. The file does not have to be a manifest but that is what most customers implement.