I have two Job Creation presets, one that filters out multi paged statements and another for the singles. In Workflow my main process branch branches out and uses the multi page job preset to extract and create a file containing all the multi paged statements. The branch then moves down and using the single page preset creates a PDF containing all the records that are single paged statements.
However some data does not have multi paged records, so when branching out the Workflow process creates a PDF that is corrupt. How do I stop this from happening? I cannot filter the data out by name because what if those databases suddenly contain multi paged data in the future.
What do you mean by “a PDF that is corrupt”? Have you opened up the resulting file to examine it?
From what you’re saying, it appears the multi-page preset works fine but not the single-page one. Have you tried running them separately to see if one impacts the other?
In your process, is each preset being called in its own branch from the Trunk and if so, have you made sure in each branch to set the option to “backup the job file”?
You did not get what I was trying to say. Say I have two databases. One has multi paged data in it and the other does not. When the branch goes down and branches out to extract the multi’s from the second database, there are no multi paged data in it, so it causes an exception (no content items to produce) which then goes to the send to folder and generates a PDF that is broken.
I could set the Create Job plugin (which extracts the multi paged statements) On Error to Stop Branch when the error occurs but that would mean I would have to sacrifice all error reporting on that plugin for this specific job. (to avoid getting unwanted email notifications for this error)
The On Error approach is the correct one. But you don’t have to cancel processing, though.
In the On Error tab, keep the Action setting to Default and tick the Log message option. Then you can write whatever message you want (which will appear in the log), but most importantly, you can set a specific value in one of the JobInfo variables. Something like this:
Now immediately after the task, insert a condition that checks whether %9 = 888. This will allow you to perform (or avoid performing) tasks specifically when no multi-page content is available.
However isn’t setting the on error like this going to report the exact same error even though the plugin might error out due to another reason?
Also, I have a on error process, so I wanted to set it in the send to process. Looks like I will have to live with that error been emailed to me each time?
Right! Forgot about jobinfo transfer between processes. I just need to make some ‘rules’ in the on error process to exclude reporting for my custom error codes.
