2022.2

l
Apartendsatthelastenabled*sectionoratthelastsectionbeforethestartofanewpart.
*WhenaControlScripthassettheenabledfieldofasectiontofalse,itwillnotbeout-
putted.
Ifnopartnameissetonanysection,itisassumedthatthereisonlyonepart,consistingofallPrintsec-
tions.Theattachmentwillbenamedaftertheemailsubject.
Examples
No parts defined
AssumetherearethreePrintsections:sectionsA,BandC.WhengeneratingEmailoutputwiththe
Printcontextasattachment,allthreePrintsectionswillbeputtogetherinonefileandattachedtothe
email.Iftheemail'ssubjectis'Takeaction',thenameoftheattachedfilewillbe'Takeaction.PDF'.
Splitting and renaming a Print attachment
AssumetherearethreePrintsections:sectionsA,BandC.InaControlScriptapartnameisdefined
forsectionC:
var section = merge.template.contexts.PRINT.sections['Section C'];
section.part = 'Part2';
WhengeneratingEmailoutputwiththePrintcontextasattachment,theemailwillhavetwoattach-
ments:
l
attachment1:SectionA,SectionB
l
attachment2:"Part2",whichisSectionC.Thefilenameofthisattachmentisthepartname.
Controlling multiple Email attachments
Thefollowingscriptattachesthefollowingsectionstoanemail:
l
Printsection3+4asattachmentwithcontinuedpagenumbers
l
Printsection6asseparateattachment
if (channel == Channel.EMAIL) { // only when generating Email output
if (merge.context.type == ContextType.PRINT) {
merge.context.sections['Section 1'].enabled = false;
merge.context.sections['Section 2'].enabled = false;
merge.context.sections['Section 3'].enabled = true;
merge.context.sections['Section 3'].part = "PDFAttach1";
merge.context.sections['Section 4'].enabled = true;
merge.context.sections['Section 4'].restartPageNumber = false;
merge.context.sections['Section 5'].enabled = false;
Page 403