---
title: "Configuring Generate PDF from Print Template (XSLT)"
slug: "configuring-generate-pdf-from-print-template-xslt"
updated: 2026-04-27T16:26:40Z
published: 2026-04-30T10:00:01Z
canonical: "documentation.encodify.com/configuring-generate-pdf-from-print-template-xslt"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Generate PDF from Print Template (XSLT)

### Overview

---

A **Generate PDF from Print Template (XSLT) Rule** automates the creation of PDFs based on pre-configured print templates. When the rule’s conditions are met, the selected template(s) are processed, and the resulting PDF is automatically saved to a specified file field.

## How to Create a Generate PDF from Print Template (XSLT) Rule

---

### **Rule Configuration**

To configure a Generate PDF from Print Template (XSLT) rule, follow these steps:

1. Navigate****to **Automation Rules** (see [Automation Rules Overview](/v1/docs/automation-rules-overview) for more details).
2. Click the **Add Rule** button.
3. Complete the **Basic Info** section:
  - Enter a **Name** and, optionally, a **Description**.
  - From the **Type** dropdown, select **Generate PDF from Print Template (XSLT)**.
4. In the **Conditions**section, select a **Module.** If needed, specify **Filter Criteria**to configure the conditions that will trigger the rule.
5. Configure **Actions**
  1. Select the**Print Templates**that will be generated. The template source depends on the Site Configuration → Module → Print Template Settings.
  2. Select the **File Field**where the generated PDF will be stored (Only **Universal File Fields (UFF)** with a limit of 1 are supported).
6. Click **Save** to confirm your settings and create a rule.

![Automation rules for generating PDFs with conditions and actions outlined in the interface.](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/Screenshot 2026-02-19 143711.png)

### **Configuration of Workflow**

1. Go to **Site Configuration → {Module} → Workflow**
2. Locate the workflow transition that should trigger the rule and click **Edit**
3. In the **Run Automation Rules** section, select the rule you previously configured
4. Click **OK** to save your changes

![Editing workflow transition from approved to rejected with automation rules and actions listed.](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/Screenshot 2026-02-19 144416.png)

## Executing the Automation Rule

---

The rule can be triggered by status transitions across various contexts, including item view, bulk status updates, and transitions within the proofing view. Upon execution, the selected print template(s) will be automatically generated, and the resulting PDF will be uploaded against the chosen file field. A background job notification titled ‘Generate Print Template’ is generated and tracked for the user who initiated the status change. The notification includes an ‘Open Item’ button to access the specific item, or an ‘Open Module’ button in the case of a bulk status transition.

![List of processed PDF generation background jobs with completion status and download options.](https://cdn.document360.io/3a63e0a8-1221-4570-aaa1-d43f9b95a612/Images/Documentation/Screenshot 2026-02-19 153553.png)

### Key Considerations

- **Bypassing Restrictions:** To ensure consistent automation, rules run under **System Admin** privileges. This means:
  - The rule ignores User Access Rights (e.g., "Export PDF" rights).
  - The rule ignores individual field-level access or module permissions.
  - Version Control is not mandatory for the target file field.
- **Note on Versioning:** The **"Increment Version"** action is **not** triggered if a file is uploaded or updated via this Automation Rule.
- **Error Handling:** There is no configuration-level validation for deleted templates or disabled "Download" permissions. If a configuration is invalid, the **background job will fail** with a detailed error log explaining the cause.
- **File Name Overwrite Logic:** If an **External Module** is enabled, the Output File Name defined in the **Module Settings** will overwrite any name defined at the **Print Template** level. Please configure names at the Module level when using external exports.