What is the easiest way to mimic the behaviour of the PlanetPress Suite 7 “PlanetPress Image Plugin”?
Here I could define both the folder and the filename of the generated pdf with workflow variables whose values I could set within vbs scripts.
I can’t seem to find out how I can do that in Connect. Working with output presets is not a viable solution for me, as catering for all the paths and filenames where I would need a pdf to end up, would mean that I have to create several hundreds of output presets.
And I have the same problem with whether or not the virtual stationary should be printed. As far as I can see I can only set that in an output preset too. That would mean that the number of output presets would even double. That’s close to a thousand output presets. So please tell me I’m missing something…
I am not sure I understand why one single ouput preset can’t be used as the Output Folder and the Filename can also be configured dynamically there? And yes you can also add the correct file extension automatically in the output preset.
You can pass jobinfos and Workflow variables to the Data Mapper and if you are using the ALL IN One which doesn’t need job presets, I would recommend assigning the dynamic variables OutputFolder and Filename to two job infos (Ex: %8 and % 9)
You may then use them in the Directory Options in the Print Options Pgae of the Output Creation Wizard with the @automation.jobinfoX@ syntax.
Why can I use @automation.jobinfoX@ but not @automation.variables.OutputFolder@?
Why doesn’t the interface help us assemble the mask and folder fields, much like the workflow configuration does:
Why this complex workaround (imho) workflow > global variables > jobinfo > datamapper > preprocessor > output preset? It would be far easier just to set the path and filename in the All in one plugin.
In our company most designers have no clue about the workflow. They don’t care where output file should go, that’s for the workflow manager to figure out. Still this way they do have to care as they’re the ones who have to provide the output preset. This way there is an (imho) unacceptable mixup of template design and file management.
I think you have a valid point. You can raise a feature request with your local support team by raising a support ticket here. Although it won’t be a game changer, the ability to dynamically configure the output filename and folder within the Output Creation tab of the All in One task task could be a nice addition.
I suppose the documentation is only intended to list variables that are specific to the Connect Output module whereas a job info is a property that is borrowed from the Workflow module.
In the Output preset, apart from using @automation.jobinfoX@ and a static path, I don’t think you can currently use any other variable type for the Output Folder; although I believe it will be possible in a future release.
To workaround all Design restrictions at your company, perhaps it woul dbe best to use the Send to Folder. You can still use the ALL inOne for Data Mapping and Content Creation, as these are only two tasks that are run in parallel, then followed by a Create Job, Create Output and Send to Folder where you can set your filename and output folders dynamically.
