A signature page template is used by Publisher to generate signature pages that are attached to document renditions. A template defines the layout of the signature page, the electronic signature property values, and standard text to include on signature pages. A signature page template can be created with any program that can produce an HTML file, for example, Microsoft Word. During signature page generation, Publisher loads this file into a session of Microsoft Word and prints the file with the Adobe PDF printer, replacing placeholders in the text with values from the specified document properties.
As of the 2022 release, you are not required to have Microsoft Office installed on the rendering node to add signature pages to the end of a document. Instead, the signature page is applied by the Aspose library.
This feature is designed for use with electronic signature information generated by the Meridian FDA Module, but it will work equally well with information generated by another electronic signature application and stored in a document property.
To create a signature page template:
-
In any program that can produce an HTML file, create a new file.
-
Type any standard text that you want to appear on every signature page.
Type placeholders to represent document property values using the syntax $(<PropertySet.PropertyName>). For example, to show the Meridian FDA Module electronic signature data on the page, type: $(BCRenditionPropertySet._ESIGNATURES).
Note:The Meridian Enterprise _ESIGNATURES property contains the electronic signature information from all signers of the current revision of the document (the most recent workflow). The same syntax may be used for other source system properties.
-
Design the layout of the template using any features (for example, tables and logos) supported by the editing program and the HTML format.
-
Upload the template as described in Manage Custom Resources.
-
Specify the template in the configuration of signature pages as described in Configure Signature Pages.
