About Headers, Footers, and Watermarks in Automatically-generated PDFs

In Quality-based Document Control, there are two methods to configure the headers and footers used on the pages of automatically-generated PDFs: forms and tables. Use form-based headers and footers if you need multi-line text. Use table-based headers and footers if you do not need multi-line text. You must define both headers and footers using one method or the other; they cannot be combined. You can specify a custom header and footer for each quality system document lifecycle state with either method. You can use the quality system document's current lifecycle state as a page watermark with either method.

Note: The following properties that define static header and footer text are no longer supported:

enoDocumentControl.PDFRendition.StaticHeaderText=
enoDocumentControl.PDFRendition.StaticFooterText=

Using Forms to Define PDF Page Headers and Footers

Forms are the default method for defining headers and footers for automatically-generated PDFs in Quality-based Document Control. Forms define the groupings and alignment of fields printed in the page headers and footers of automatically-generated PDFs. The headers and footers can contain up to three columns of up to three rows of fields each. Each form field must have a Group Name setting that has a value of Left, Right, or Center to specify the column where the field is used.

Header Form

There are properties that specify the default header form used in each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.Default.PDFHeaderOverlay = DOCOPDFHeaderForm

There are properties that you can use to specify different header forms for different implementing organizations for each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.<organization>.PDFHeaderOverlay = DOCOPDFHeaderForm

Note: MyCompany is the default implementing organization that you must replace with you own organization names.

The default header form specified in all of these properties, DOCOPDFHeaderForm, includes these fields in this layout:


`<Type>`		`<Name> \| <Revision>`
`<State>`		`Effective Date: <Effective Date>`
`<Title>`		`<Organization>`

You can define a custom header form to use for one or more quality system document lifecycle states and implementing organizations.

Footer Form

There are properties that specify the default footer form used in each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.Default.PDFFooterOverlay = DOCOPDFFooterForm

There are properties that you can use to specify different footer forms for different implementing organizations for each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.<organization>.PDFFooterOverlay = DOCOPDFFooterForm

Note: MyCompany is the default implementing organization that you must replace with you own organization names.

The default footer form specified in all of these properties, DOCOPDFFooterForm, includes these fields in this layout:


`<UnControlledCopy label>`	`<Confidential label>`	`<Page Number>`

You can define a custom footer form to use for one or more quality system document lifecycle states and implementing organizations.

Using Tables to Define PDF Page Headers and Footers

Tables define the groupings and alignment of fields printed in the headers and footers of automatically-generated PDF files. By default, the properties that specify the watermarks and the tables used for footers in automatically-generated PDFs are defined but commented out using a #. You must copy and rename these properties to use them to define the footers and watermark for automatically-generated PDFs.

Header Table

There is no default header table defined. There are also no default header properties defined. You can create a custom header table then use it as the default header by adding the needed properties and specifying the header table name value. Define the properties using the following format: enoDocumentControl.QualitySystemDocument.<state>.Default.PDFHeader = <Header table name>

There are no properties that specify different header tables for different implementing organizations for each quality system document lifecycle state. You can create a custom header table then use it by adding the needed properties and specifying the implementing organization and header table name values. Define the properties using the following format: enoDocumentControl.QualitySystemDocument.<state>.<organization>.PDFHeader = <Header table name>

Footer Table

Important: By default, all of the footer table properties' names are preceded by #. You must remove the # from these properties' names to use them to define footer tables for automatically-generated PDFs.

There are properties that specify the default footer table used in each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.Default.PDFFooter = DOCOPreliminaryPDFFooterTable

The default footer table specified in all of these properties, DOCOPreliminaryPDFFooterTable, includes these fields in this format:


`<UnControlledCopy label>`	`<Type>\|<Name>\|Revision>`	`<Page Number>`

You can define a custom footer table to use for one or more quality system document lifecycle states and implementing organizations.

Defining Watermarks for PDF Pages

There are properties that specify the default watermark used in each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.Default.Watermark = current

There are properties that you can use to specify different watermark use for different implementing organizations for each quality system document lifecycle state. They are defined using the following format: enoDocumentControl.QualitySystemDocument.<state>.<organization>.Watermark = current

The watermark defined for each quality system document lifecycle state, except for Released, is the current lifecycle state of the quality system document. Documents in the Released state have no watermark by default. To specify that no watermark be used for one or more quality system document lifecycle states, remove the value for the affected states.