Section Templates and Sig IDs

[johnny_jay]

I am having trouble with Sig IDs in a template with 2 sections. Section one mark comes out fine but section 2 does not. I am restricting the mark to each section but both still say the lower Sig number. For example  Section 1 is Sig 2 and Section 2 is Sig 7 both say Sig 2.

I also have a collation mark set the same way it is comes out perfect.

Thank you,

John

[Joe]

I think you have to have your template setup as a multi-section for that to work like the one shown in the screen shot. There are two separate signatures in one template as indicated by the red numbers. I have 2 ID's on the template, one for each section so the press knows which sections they are running.

[johnny_jay]

I think you have to have your template setup as a multi-section for that to work like the one shown in the screen shot. There are two separate signatures in one template as indicated by the red numbers. I have 2 ID's on the template, one for each section so the press knows which sections they are running.

This is how I have it set up. Everything seems fine except for the Sig ID. I pulled out my Preps/Prinergy training guide and tried some other marks but had no luck.

[Joe]

Oh, that's weird then. Mine work perfectly and it looks like yours are setup the same way.

I'm on 5.3.3. Is that the version you are using?

[johnny_jay]

yes - 5.3.3

and no Kodak support contract - yippee - maybe I'll post to the GUA - Kodak techs sometimes do chime in

[Farabomb]

Having that Kodak support contract isn't all it's cracked up to be. On average this forum has solved far more issues I've had better and far faster than any call to Kodak.

[Joe]

yes - 5.3.3

and no Kodak support contract - yippee - maybe I'll post to the GUA - Kodak techs sometimes do chime in

The only difference I see between yours and mine is that I am using:

Sig: $sig

and you are using:

Sig: $[SIG]

Which should work but it's worth a try to change it.

[Joe]

I just tested this. $[SIG] does not work on my template but $sig does work.

[johnny_jay]

Thanks so much Joe, I'll try that tomorrow. The Prinergy training had me so programed to do $[SIG] I never thought of trying $sig. :embarrassed:

[johnny_jay]

Having that Kodak support contract isn't all it's cracked up to be. On average this forum has solved far more issues I've had better and far faster than any call to Kodak.

Good point! When we first switched to Prinergy I was on the phone a good bit with Kodak, mostly for stupid stuff. Many calls then could have been avoided if there had been better documentation.

Our SUA was great, but things never go wrong in the trenches when help is on site.

Now to master RBA.  :rolleyes:

[Joe]

It's kind of weird because in my template, I'm using Prinergy variables like $[ImpPlanName] and $[Color_Offset] and they work but for some reason $[SIG] doesn't work.

[johnny_jay]

It's kind of weird because in my template, I'm using Prinergy variables like $[ImpPlanName] and $[Color_Offset] and they work but for some reason $[SIG] doesn't work.

Same here as well.

[DigiCorn]

Too bad you're on Prinergy. I love the Rampage marks. They make it so easy...

[johnny_jay]

Too bad you're on Prinergy. I love the Rampage marks. They make it so easy...

We actually switched from Rampage last year. Prinergy is not perfect but much better than Rampage for us. We needed the automation and the Insite Portal is top notch. The marks are pretty close to the same. This has been the first kink we had with marks.