# Generating a PDF from a DITA Map — WKFS 2026

This document explains how to set up your DITA map metadata and run the **DITA Map PDF (XSLFO) - WKFS 2026** transformation scenario in Oxygen XML Editor to produce a properly branded PDF.

---

## 1. Configure the DITA Map Metadata (`<othermeta>` elements)

The PDF transformation reads document metadata from `<othermeta>` elements inside the `<topicmeta>` block at the top of your `.ditamap` file. These values populate the cover page, footer, and back cover of the rendered PDF.

Open your `.ditamap` file in Oxygen and locate (or add) the `<topicmeta>` block immediately after the `<title>` tag. Set the following `<othermeta>` elements:

```xml
<map title="Your Document Title">
  <title>My User Guide</title>

  <topicmeta>
    <!-- Business division shown on the cover and back cover -->
    <othermeta name="division"         content="Financial &amp; Corporate Compliance"/>

    <!-- Document type label shown in the footer (e.g., "User Guide", "Tagging Guide") -->
    <othermeta name="doctype"          content="Tagging Guide"/>

    <!-- Product family name shown on the cover and in the footer -->
    <othermeta name="product-family"   content="SmartSign Plus"/>

    <!-- Support phone number shown on the back cover -->
    <othermeta name="phone-number"     content="800-274-2711"/>

    <!-- Support phone extension shown on the back cover -->
    <othermeta name="phone-extension"  content="1123666"/>

    <!-- Support email address shown on the back cover -->
    <othermeta name="email"            content="emailaddress@wolterskluwer.com"/>

    <!-- Copyright year shown in the footer and back cover -->
    <othermeta name="year"             content="2026"/>

    <!-- Publication month (two digits, e.g., "03" for March) -->
    <othermeta name="month"            content="03"/>
  </topicmeta>

  <!-- topicrefs follow ... -->
</map>
```

Replace the `content` values with the correct information for your project. **All eight elements are required** — if any are missing, the corresponding section of the PDF will be blank or may trigger an error.

---

## 2. Duplicate the Global Scenario as a Project-Level Scenario

The scenario **DITA Map PDF (XSLFO) - WKFS 2026** is stored as a *global* Oxygen scenario. You should duplicate it as a *project-level* scenario so that your settings are version-controlled with your project and do not affect other DITA projects on your machine. In this way, the scenario is also available to anyone that opens the project.

**Steps:**

1. In Oxygen, open the **DITA Maps Manager** and load your `.ditamap` file.
2. Click the **Configure Transformation Scenarios** button (the wrench/play icon in the DITA Maps Manager toolbar), or go to **DITA Maps > Configure Transformation Scenarios**.
3. In the **Configure Transformation Scenarios** dialog, find **DITA Map PDF (XSLFO) - WKFS 2026** in the list (it will be marked as *Global*).
4. Select it and click **Duplicate**.
5. In the **Edit Scenario** dialog that opens:
   - Change the **Name** if desired (e.g., append your project name).
   - At the top of the dialog, change the **Storage** dropdown from **Global Options** to **Project Options**. This saves the scenario inside your Oxygen project file (`.xpr`) so it travels with the project.
   - IMPORTANT: Verify or update the **Output** directory field to a path appropriate for your project. The output PDF **MUST** be in a "PDF" folder inside your document's root structure.
   Example:
      - Your document folder is: \\zusscgrcprodwebhelp.file.core.windows.net\webhelp\dev\CompliEditor\UserGuide
      - Your PDF folder must be located as follows: \\zusscgrcprodwebhelp.file.core.windows.net\webhelp\dev\CompliEditor\UserGuide\PDF
6. Click **OK** to save the duplicated scenario.
7. Back in the **Configure Transformation Scenarios** dialog, ensure only your new project-level scenario is checked.
8. Click **Apply Associated**.

> **Why project-level?** Global scenarios are shared across all projects on your machine. Saving as a project-level scenario means changes you make (output paths, parameters, etc.) are isolated to your project and can be committed to source control alongside your DITA content.

---

## 3. Run the Transformation

1. With your `.ditamap` open and active in the **DITA Maps Manager**, click the **Apply Transformation Scenarios** button (the play ▶ icon).
2. Oxygen will run the `pdf2` transtype using Apache FOP and write the rendered PDF to the output directory configured in the scenario (default: `C:\DITA\transforms\out\<mapname>\`).
3. When the transformation completes, the **Results** panel at the bottom will show **BUILD SUCCESSFUL**. The PDF will open automatically if **Open in Browser/System Application** is enabled in the scenario output settings.

---

## 4. Key Scenario Settings (Reference)

| Setting | Value |
|---|---|
| Scenario name | `DITA Map PDF (XSLFO) - WKFS 2026` |
| Transtype | `pdf2` |
| FO Processor | |
| Processor | Apache FOP (built into DITA-OT) |
| Parameters | |
| Customization files | `C:\DITA\WKFS_oXygen_Files\PDF-files\Customization\` |
| Output | |
| Base directory | `${cfd}` (folder containing the active ditamap) |
| Default temp directory | `C:\DITA\transforms\temp` |
| Default output directory | `C:\DITA\transforms\out\${cfne}` |

---

## 5. Troubleshooting

| Symptom | Check |
|---|---|
| Cover page fields are blank | Verify all `<othermeta>` elements are present in `<topicmeta>` with the exact `name` values listed above. |
| TOC is missing | Ensure the map has at least one `<topicref>` that resolves to a valid topic. |
| Build fails with font errors | Fira Sans fonts must be available to FOP. Confirm the font configuration in the customization's `fop.xconf`. |
| Scenario not listed | Import the scenario: **Options > Import Global Options** and point to `WKFS_oXygen_Files\scenarios\DITA Map PDF (XSL-FO) - WKFS 2026.scenarios`. |
