- Create or open the text file for
customized properties.
For
more information,
see
Editing Properties Using MQL.
-
To configure a default header table to be used in all automatically-generated PDFs for quality system documents in a specific lifecycle state, follow these steps:
-
Add or edit these lines in the file used to import properties into a page object:
enoDocumentControl.QualitySystemDocument.Draft.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.InWork.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.InApproval.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Approved.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Released.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Superseded.Default.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Obsolete.Default.PDFHeader=<Header table name>
Note:
There are no header table properties defined, so you must add all of them that you want to use.
There is no default header table defined, so must create one before you can configure these properties.
-
Set the value for the property as the name of the custom header table that you created. It will be used as the default header in PDFs automatically generated for quality system documents in that lifecycle state.
-
To configure a different header table for each implementing organization to be used in all automatically-generated PDFs for quality system documents in a specific lifecycle state, follow these steps:
-
Add or edit these lines in the file used to import properties into a page object:
enoDocumentControl.QualitySystemDocument.Draft.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.InWork.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.InApproval.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Approved.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Released.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Superseded.<organization>.PDFHeader=<Header table name>
enoDocumentControl.QualitySystemDocument.Obsolete.<organization>.PDFHeader=<Header table name>
Note:
There are no header table properties defined, so you must add all of them that you want to use.
There is no default header table defined, so must create one before you can configure these properties.
-
Set the value for this property depending on your business requirements:
- Set the value for the property as the name of the custom header table that you created. It will be used as the default header in PDFs automatically generated for quality system documents in that lifecycle state for that implementing organization.
- Replace
<organization> with the name of your implementing organizations.
-
To configure the default footer table to be used in all automatically-generated PDFs for quality system documents in a specific lifecycle state, follow these steps:
-
Add or edit these lines in the file used to import properties into a page object:
enoDocumentControl.QualitySystemDocument.Draft.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.InWork.Default.PDFFooterOverlay=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.InApproval.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Approved.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Released.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Superseded.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Obsolete.Default.PDFFooter=DOCOPreliminaryPDFFooterTable
Note:
You must create a custom footer table if you do not want to use the default footer table.
-
Set the value for this property depending on your business requirements:
-
Type the name of a custom footer table as the value to use it instead of the default footer table in PDFs automatically generated for quality system documents in that lifecycle state.
-
Delete the value if you do not want to use a footer in PDFs automatically generated for quality system documents in that lifecycle state.
-
To configure a different footer table for each implementing organization to be used in all automatically-generated PDFs for quality system documents in a specific lifecycle state, follow these steps:
-
Add or edit these lines in the file used to import properties into a page object:
enoDocumentControl.QualitySystemDocument.Draft.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.InWork.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.InApproval.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Approved.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Released.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Superseded.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
enoDocumentControl.QualitySystemDocument.Obsolete.MyCompany.PDFFooter=DOCOPreliminaryPDFFooterTable
Note:
You must create a custom footer table if you do not want to use the default footer table.
-
Set the value for this property depending on your business requirements:
-
Type the name of a custom footer table as the value to use it instead of the default footer table in PDFs automatically generated for quality system documents in that lifecycle state for that implementing organization.
-
Delete the value if you do not want to use a footer in PDFs automatically generated for quality system documents in that lifecycle state for that implementing organization.
Note:
MyCompany is the default implementing organization that you must replace with your own organization names.
-
When you are finished updating the text file with all properties that you want to modify, use the text file to modify the enoDocumentControl.properties page object. For more information, see Editing Properties Using MQL.
|