PDF templates is a flexible mechanism for setting up printing forms for different vTiger modules. 

A list of PDF templates is available from the vTiger CRM Menu -> Tools -> PDF Templates

On the PDF Template List page, you can view, edit a template, create a new one, or add a new template by duplicating an existing one, for subsequent modification.

Create a PDF Template

Go to vTiger CRM Menu -> Tools -> PDF Templates

Click on the Add template button.

The PDF template edit page contains a property area and an editing area.

In the properties area, you need specify the following required template parameters:

Template name - is an arbitrary string that will indicate the created template.

Module - select from the drop-down list of the module to which the template belongs.

Header size - The height in pixels of the template title. The template header is set by the header block.

Footer size - The height in pixels of the footer of the template. The template footer is set by the footer block.

Page orientation - select an orientation type from the drop-down list (portrait or landscape).

Company - a choice from the drop-down list of that legal entity. Persons whose data will be inserted into the template (for the addition of other legal entities, see. Organization Data).

In the editing area, the body of the template is entered. The body of the template is HTML markup divided into blocks. Each block is limited by two special tags - opening and closing:

A typical template for Invoice, Quotes, Sales Order or Purchase Order modules consists of the header, table_head, table_row, summary, ending, footer blocks:

header block

This is an optional block, which is located at the top of the first page of a printed document and, as a rule, is used to issue a standard document header.

table_head block

This is a required block, which is displayed once before the table of goods (services) of a printed document. Used to set table headers.

table_row block

This is a mandatory block that is displayed for each product (service) of a printed document.

summary block

This is a required block, which is displayed once immediately after the table of goods (services). Used to display the total cost and taxes.

ending block

This is a mandatory block, which is placed once at the end of a printed document and is usually used to issue signatures and other final elements.

footer block

This is an optional block that appears at the bottom of each page of a document.

A typical HelpDesk or Potential template consists of header and content blocks:

Header block

This is an optional block, which is located at the top of the first page of a printed document and, as a rule, is used to issue a standard document header.

Content block

This is a required block that contains the main body of the generated PDF document.

Variables

PDF templates allow you to insert variables into printed documents, which are replaced by data from the corresponding CRM record. Variables have the form:

Each module has its own set of common variables, which include all fields of the printed CRM record, as well as all fields of related records (for example, Organizations and Contacts). In addition, special variables are available in the table_row and summary blocks, which are calculated based on the list of goods (services).

Own organization data available in all modules

Responsibles data available in all module

Invoice Module Variables

Quotes Module Variables

Orders module variables

Purchase Order Module Variables

Accounts module variables

Contacts module Variables

Vendors module variables

Potentials module Variables

Helpdesk module variables

Products Module Variables

Special variables of table_row block

Special variables of the summary block

Date format and translations

The standard date output format is long, for example, on 15 August 2011. However, adding the suffix_short to the name of any date variable, we get the date in a short format (for example, 15.08.11).

Text values of some variables are displayed in English by default (for example, standard lists). You can get a translation of these values by adding the suffix_translated to the variable name.