I'm new to the Xerox FreeFlow system and I'm having trouble figuring out if the Preflight reports are saved any place other than the job details? In my current workflow I have a few different preflights that are setup. I have a basic preflight and then based on the results have it routed to a different path that runs some additional preflights. I know on one of the preflights I’m generating errors but it looks like it saves the last preflight report in the process on the job notes. I’m looking to determine if I can view all preflight reports that are run on a specific job, I assume that the reports are saved in a folder on the server someplace but I have not been able to track them down. Any help would be appreciated.
Solved! Go to Solution.
FreeFlow Core saves only the last preflight report.
If you want the information from the previous preflight reports I would suggest that you add checks from the previous preflight profiles to the last prefilght profile in the workflow.
Ok that makes sense, can you access them anyplace other than the job details? We would like our CSR's to be able to access the report so they can email the client but they will not have access to FreeFlow only to some of hte folders.
You can add an external node after preflight and then call a script (can be as simple as a batch file) to copy the current report somewhere else.
The URI for the preflight report is in the following variable: $FFwfdoc.preflightReport$
You can also fully automate this by passing the customer's email to FFCore and then using the external node to invoke a CLI email client.
You can see more details in the following threads:
I´m having trouble sending the prefilght report using blat. Without report it works jsut fine, but I can´t make the script send the actual report. What´s wrong with my syntax here?
I found it is easier to debug the syntax of external commands by opening a command line on the PC, and typing the command in full there like: C:\blat\full\blat.exe -to firstname.lastname@example.org etc.
Blat will tell you what it finds wrong with the command. You can fix it, then copy/paste the parameters back into FreeFlowCore.
You will need to replace the $FFwfdoc-preflightReport$ with a real file name and path like c:\test.txt
I would also do two things:
The variable you are using ended up in the documentation because of a misunderstanding (it's an internal variable). We corrected that misunderstanding by creating a documented variable with the expected information.
About debugging scripts. I would endorse the approach mentioned by JJakubowski. Get the script working on the CLI and then copy it into the FFCore preset. Once there you can see the CLI feedback in two XML files FFCore will create when the script executes. There should be a status folder in the script folder in the sandbox (you will need to access the location in the server filesystem). These files contain the output from stdout and stderr (aka the feedback you will see when you invoke the script from the CLI).
Thanks Javier and JJakubowski!
I´ll try what Javier suggested and thanks JJ for the great tip using the command line as debugging tool!
Sami from Finland
Finally had the chance to test this...
I can´t manage to get it to work even in Core CLI. Seems that the problem lies in the report file name. Debugger says that blat do not understand the space in the report filename (screenshot). I also tried this from the Core web client itself, returns code -1. If I put a file named A4.pdf to the same folder where the report is and send it with blat, everything works fine.
Any suggestions what to do now?
Sami from Finland