Working in FFCore, I'm trying to setup a workflow which is pretty basic. It's a straight from FFWS to Print function. However, when I'm trying to add in the required exception pages, I seem to be hitting some odd limits - or most likely doing something wrong.
Exception pages are by 9, starting at 1 and ending at 3007. I've read this may be what is called a 'cyclical process', however as a newbie to core, this is a bit over my head. Attached is a screenshot of what I'm working with, hopefully it may shed some light on my potential error.
The image appears as a yellow trangle with a gray border. Not sure what the error is.
That said, there are two ways to define exceptions in the DFE - via the JT or as cyclical exceptoins.
The first method has a limit of 255 exception pages.
The second method does not have a limit. This second method, however, must be configured in the DFE queue as it is not available via job ticketing.
I don't know all the details around cyclical exception pages. I would suggest you reach out to your analyst.
Thanks! I'll be reaching out in the appropriate manner from here out to see if a cyclical process will help. I appreciate the feedback!
As for the Exception Pages in the JT:
My first set is as follows: 1, 10, 19, 28, 37, 46, 55, 64, 73, 82
The next set follows in suit: 91, 100, 109, 118, 127, 136, 145, 154, 163
The first set shows up at the machine without an issue. The problem comes with the next sets of exception pages not showing up. I have noticed that the sets seem to have a limit and cannot contain too many exception pages or the entire set is thrown out.
Any ideas on why the JT is failing in this manner?
Maybe it's an option on FFPS to use the attached document to create a PS ini file that can be used in a queue to enable cyclic exceptions.
This should work on FFPS 7.0 SP-2 and higher
I just heard back about the FFPS special pages limit. The combined limit for both sheet inserts and exceptions is 1,000.
You should be able to submit a job with the exceptions as you had asked (the total was approx 350 exceptions). If that's not working as expected please escalate to the hotline,