i'm having trouble Imposing a job when template has pages set to unused

[msteinberger]

I have triggers set up that turn a page on or off depending on the data, but when I try to impose the job, the pages that are set to unused will not impose.

 

I have the pages set to unused in the page manager and am using "set body page usage" in the OnRecordStart rule to turn them on or off depending on the data.

 

Under normal composition, the jobs compose exactly as they should. When I try to compose and use an imposition definition, the unused pages will not impose even when the data is saying they should be used.

 

I'm using FusionPro VDP Designer 9.3.9

 

Thanks,

[Alex Marshall]

Are you chunking the output? Did you possibly enable the "Infinite Stack" option in the FP Imposer definition file?

[msteinberger]

Hi Alex,

My POD department has asked that we give them batches of 5,000 records so I have infinite stack turned off and stack set to 2500 in my Imposer definition file.

[tou]

onJobStart should have the following:

 

FusionPro.Composition.chunksBreakStacks = true

 

infinite stacks in fpi checked as well as you already have it.

 

output file, split on 5000 record chunks.

[Alex Marshall]

Reinstall Fusionpro using the 9.3.36 build from the support page:

http://marcom.com/resources/support-training/fusionpro-downloads/

[Dan Korn]

Under normal composition, the jobs compose exactly as they should. When I try to compose and use an imposition definition, the unused pages will not impose even when the data is saying they should be used.

Are you sure about that? I suspect that the output pages are not in the order you expect when imposed. I would try adding a text frame with variables such as $pagenum, $inputrecordnumber, $outputrecordnumber, $processedrecordnumber, and $outputrecordnumberbysheet to each of the pages, in order to track exactly which pages you're seeing in the output. You might also want to add some Print calls to your OnRecordStart rule to report which pages have been activated for each record in the composition log (.msg) file. Of course, you should be looking at the log file for any warning messages already.