We use the review module to sent out emails to clients.
The original input was an XML that picks up the supplied file and wraps the XML round it as normal. The problem is that when the customer reviews the file and approves it the output from that process is the report file with the XML file. My additional preflights further down the process fail because it tries to create a report that is already a report file.
Am I missing a trick or is there a way round this?
Review Module - Original PDF input file
Re: Review Module - Original PDF input file
You could use a Inject Job that picks up the PDF file again after the Review
Re: Review Module - Original PDF input file
Unfortunately that's not really a starter as the PDF had already been through preflights and actions before being submitted for review so I don't want to do all that again.
Any other thoughts?
Any other thoughts?
Re: Review Module - Original PDF input file
If the customer see the PDF report in PDf Review instead of the original PDF then you have either to change your flow so that it is the original that the customer see.
Or let them see the report it there is warnings or errors and in PDF review they make decisions on what and how the PDF should be treated. Then if they decide that the PDF should be printed anyway they say OK to the job and Switch will pick up the original PDF from a repository. If they decide anything else, like tell you to fix problems or they send you a new file the original in the repository gets deleted.
Here is a flow that does just that. Customer sees the PDF Report with all errors and warnings as annotations. They also get a report in the email with the link, that email also has a preview of the PDF's first page.
Email me if you have any questions on this flow.
Or let them see the report it there is warnings or errors and in PDF review they make decisions on what and how the PDF should be treated. Then if they decide that the PDF should be printed anyway they say OK to the job and Switch will pick up the original PDF from a repository. If they decide anything else, like tell you to fix problems or they send you a new file the original in the repository gets deleted.
Here is a flow that does just that. Customer sees the PDF Report with all errors and warnings as annotations. They also get a report in the email with the link, that email also has a preview of the PDF's first page.
Email me if you have any questions on this flow.
Re: Review Module - Original PDF input file
I do not quite understand the original question. It suggests that the output of the review process is a report, but it is not: the output of the review process is the input file, possibly enriched with comments that have been added.
And why would you preflight a file after it has been approved and not before?
And why would you preflight a file after it has been approved and not before?