Preflight Error Report

[JavierM-Xerox]

The preflight reports are generated by the Preflight component so place that component before the external component in the workflow.

After preflight you can use the external component to invoke blat (or any other CLI email client) to email the preflight report.

You can see an example here:

http://forum.support.xerox.com/t5/FreeFlow-Core/Sending-emails-with-the-external-component-and-Blat/...

[Erick]

I am having similar issues. We just got Freeflow Core and I am trying to get our Preflight workflow under way.

Question 1. Do we need to set-up Notifications in the Administration tab in order to generate preflight reports via email?

Question 2. Could you give me an example of what the script and parameters would look like in Blat in order to generate a preflilght report?

Would appreciate any info you could give.

[Stevieraysuihkonen]

Thousand thanks AnwarG! And great news - it worked! Meaning I used the script and the parameter You sent and works smoothly...

Happy as can be :-) Very happy...

Sami from Finland!

[AnwarG · Accepted solution]

Have you checked the error log? That usually gives some more information about what is wrong with the script.

C:\Xerox\FreeFlow\Core\Data\00000000-0000-0000-0000-000000000000\Data\Scripts\External Process Status\stderr.log

We have a similar script running that works, should work for you aswell.

Parameters: "$FFwfjob.preflightReport$"

Script:

cd\
cd C:\Xerox\FreeFlow\Core\Data\00000000-0000-0000-0000-000000000000\Platform\Spool\%1\

copy *.* D:\HOT_OUT\KUOPIO

[Stevieraysuihkonen]

Thanks Anwar! 

Tried this, but sorry to say didn´t work :-(

The script was: copy %2 D:\HOT_OUT\KUOPIO, parameters $FFin$ $FFwfJob.preflightReportUri$, but no luck, still gives exit code 1...

But thanks anyway. Any ideas what to do now?

Sami

[AnwarG]

Try the following settings:

Parameters: $FFin$ $FFwfJob.preflightReportUri$

Script: copy %2 D:\HOT_OUT\KUOPIO

%1 refers to the first parameter, %2 refers to the second parameter, etc etc.

[Stevieraysuihkonen]

One problem solved, but here comes the nest one...

I´m trying another way to handle these reports, copying them from the default Core location to D:. If I try the specific folder for one or another folder from CLI, everything works just fine, report copies to D:\HOT_OUT\ ok. Now I´m trying to do this onlien from Core using batch script, but all I get is an error. Above You´ll find the script itself and the parameters from Core, plus the error code from Core. I´m probably missing a thing or two, can´t just figure out, what...

The script: copy "$FFwfJob.preflightReportUri$" D:\HOT_OUT\KUOPIO

[Stevieraysuihkonen]

LOL, thats´s a pretty simple solution :-) 

Thousand thanks Javier! Very much appreciated!

Sami

[JavierM-Xerox]

Try -attach "C:\..."

If there's a space in a path you typically have to put quote marks around the path.

[Stevieraysuihkonen]

Hi again!

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