When you elect to preflight using a preflight profile you will have the option to upload a preflight profile.
Click on the yellow folder icon.
A dialog will come up listing the preflight profiles. You can use the Upload button to add more profiles.
thanks for the info. we have the license now for the advanced prepress components. I can create the pre-flight profiles but cant seem to find out how to get them into the core preferences folder. is there an easy way to do this.
The components that you see in workflow builder are controlled by licensing. The base license includes preflight, impose, enhance images, print, save and finish. Additional components and functionality require one of the 4 other licenses: advanced prepress, advanced prepress and automation, output management and variable data.
Optimize and the external component are part of the advanced prepress license.
Note: The external component will let you automate printing via FFPM-APP per this post: http://forum.support.xerox.com/t5/FreeFlow-Core/Using-the-External-component-to-print-via-FFPrintMan...
The preflight component in the base version of FFCore provides access to all preflight available in Adobe Acrobat or in pdfToolbox. There's no need to purchase and additional license to access the advanced preflight capabilities.
In order to enable advanced preflight, you will need to create the preflight profile and upload it to FFCore. FFCore will execute the profile and perform all defined checks / fixups. There's no need to install any additional software in the FFCore server.
I am trying to just create some basic workflows and wish to import more components such as optimze, preflight (not just basic) and so on. Do I need to have acrobat loaded onto this server to import more components? At this point I am trying to use the print manager to send directly to a printer. No lpr needed at this time.
To use 3rd party software with FFCore you would typically use the External component.
That component has two modes of operation.
We save a PDF and optionally the print ticket to a defined location (local or a shared network drive) and then we pick the files up at another location. This is typically done with off the shelf software that supports hot folders.
In this case we make a CLI call to invoke a program of script. You can pass parameters to this script and also use it to update the job's print ticket. The parameters may also be any variables that FFCore supports (see Appendix in Help).
I typically suggest that people get their script workfing from the CLI first and then do the external node configuration.
Lastly, when FFCore executes a script we capture stdout and srderr to XML files within a Status folder in the Scripts folder within the FreeFlow Core sandbox. You can open these files to see what you would otherwise see if you invoked the script from the CLI.
Once you define a preset for either hot folders of a script you can reuse that in many workflows.
I moved a tutorial from the internal FFCore forum to the public FFC forum as it uses the external node: