---
title: "When to use Workday Document Transformation instead of…"
description: "Use Document Transformation when a connector’s XML needs XSLT with ETV or XTT—custom warnings, non-XML output, or multiple files—without full Studio or…"
url: https://kiweely.com/guides/workday-document-transformation-connector-when
---

# When to use Workday Document Transformation instead of Orchestrate or Studio

Document Transformation is a connector-only template: XSLT with ETV (XML out) or XTT (text out) on another connector’s document. Use it to reshape connector output or inbound XML. Prefer packaged connectors first, Orchestrate for APIs, and Studio for multi-call assemblies.

-   **Checked** against Workday on November 17
-   Applies to **Workday integrations: Document Transformation, connectors, Orchestrate, Studio**
-   3 min read
-   Published November 17
-   By Kiweely

Use **Document Transformation (DT)** when a **connector** already moves the data and you only need to reshape the document: custom warning messages, calculations in XSLT, multiple output files, or a non-XML text file. DT is not a general replacement for Orchestrate or Studio. Workday lists it as an advanced transformation tool used **only with connectors**.

## What Document Transformation is

From Workday’s connector and integrations education materials:

-   DT is a connector template that transforms data from or for another connector integration.
-   The attachment is XSLT with Workday-specific instructions.
-   **ETV** (Element Transformation and Validation) produces **XML**.
-   **XTT** (XML to Text) produces **text**.
-   The DT integration’s data source is the connector’s document; DT does not extract Workday data on its own.

A connector integration business process can fire a DT (or Studio) step so the parent connector event produces the file the transformation consumes.

## Decision table

| Need | Prefer | Why Workday frames it that way |
| --- | --- | --- |
| Vendor template, no transform | End-to-end connector | Aligns systems without coding or DT. |
| Generic extract/load with maps, change detection | Generic / Core Connector | Configurable foundation; Workday maintains the template code line. |
| Reshape connector XML; custom errors/warnings; multiple files; non-XML out |  **Connector + Document Transformation** | Inbound: modify XML input to Workday format, custom messages. Outbound: modify core connector output, multiple files, non-XML, custom messages. |
| Event-driven APIs, custom transforms without a connector document, batched scenarios | Orchestrate | No packaged solution; call Workday or third-party APIs; transform in Orchestration Builder. |
| Multiple WWS requests per object, per-object processing, complex error handling/logging, variety of scenarios | Studio | Full IDE assemblies when the connector+DT path is not enough. |

Workday’s inbound and outbound tool-order tables put **Connector with Document Transformation** after packaged/generic connectors and Orchestrate in the published sequence, and before Studio. Use that order as the default triage, not as a ban on DT when the requirement is exactly “transform this connector file.”

## When DT is the right middle path

Choose DT when most of these are true:

1.  A connector template already covers the dataset (check **Integration Template Catalog**).
2.  The gap is format, validation messages, or file shape—not a new multi-API workflow.
3.  You can express the change in XSLT with ETV/XTT.
4.  You accept that Workday does not validate XSLT syntax on upload; syntax errors appear at runtime and can hide later errors.

Skip DT (for this requirement) when:

-   There is no connector document to transform—you need RaaS/SOAP/REST orchestration or Studio.
-   You need many web service calls per object or heavy custom Java—that is Studio territory.
-   You only need a simple spreadsheet in/out—that is often an **EIB**, not DT.

## How to confirm in the tenant

1.  Run **Integration Template Catalog**. Open **View Details** on candidate connectors and Document Transformation templates.
2.  Confirm the parent connector produces the document tags your DT expects.
3.  Attach and test the XSLT in a non-production launch; read the integration event messages for transform failures.
4.  If the next requirement is “call three APIs and branch,” stop extending the XSLT and move the design to Orchestrate or Studio using Workday’s tool-order criteria.

Kiweely Vine can help you reason about which integration pattern fits a tenant question. Roots (coming next) is aimed at agent-built integrations; it is not a substitute for the connector+DT path today.

## Frequently asked questions

### Does Document Transformation extract data by itself?

No. It uses the same source as its connector because it only transforms the document. The connector (or inbound file into that pattern) produces the data; DT reshapes it.

### ETV or XTT—which do I pick?

ETV produces an XML output file. XTT produces a text output file. Both ride on XSLT with Workday-specific processing instructions on the Document Transformation template.

### Where do I find DT templates?

Run the Integration Template Catalog report in Workday. Filter by template category; the catalog includes end-to-end connectors and Document Transformations. Use View Details for services, attributes, and maps.

## Frequently asked questions

### Does Document Transformation extract data by itself?

No. It uses the same source as its connector because it only transforms the document. The connector (or inbound file into that pattern) produces the data; DT reshapes it.

### ETV or XTT—which do I pick?

ETV produces an XML output file. XTT produces a text output file. Both ride on XSLT with Workday-specific processing instructions on the Document Transformation template.

### Where do I find DT templates?

Run the Integration Template Catalog report in Workday. Filter by template category; the catalog includes end-to-end connectors and Document Transformations. Use View Details for services, attributes, and maps.

## Sources checked

-   [Workday Integrations Overview](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-integrations-overview.html)
-   [Workday Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-connectors.html)
-   [Integrations (Security for Administrators)](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/integrations.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Start with a Workday packaged connector before custom Studio Workday places packaged and generic connectors above Orchestrate and Studio. Start with Integration Template Catalog; add Document Transformation to reshape a file. Open Studio for multiple web service calls per object or complex custom assemblies.](https://kiweely.com/guides/workday-packaged-connector-before-studio)
-   [### Three cases where Workday still wants Studio Workday still routes work to Studio for multiple web service requests per object, individual object processing with complex error handling, and highly customized Java/IDE assemblies. Orchestrate is preferred for many new flows, but education materials keep Studio for that specialized subset.](https://kiweely.com/guides/workday-studio-three-cases-keep-studio)
-   [### Orchestrate is not a bulk-load replacement for Workday EIB or Studio Orchestrate can run batched scenarios and child integrations, but Workday’s Studio comparison says it is not suitable for large batch data jobs. Keep EIB for simple spreadsheet loads, connectors or Studio for heavy extracts, and design Orchestrate within published runtime limits.](https://kiweely.com/guides/workday-orchestrate-not-a-bulk-load-replacement)
-   [### What Is an EIB in Workday? How to Build, Template and Load One Workday’s guided integration tool, both ways: the exact tasks to build, template and load an inbound EIB, how to build an outbound one from a report, the template rules people trip on, Workday’s published limits and the security it needs.](https://kiweely.com/guides/what-is-an-eib-in-workday)

### More guides on Orchestrate

[All 86 guides](https://kiweely.com/guides#orchestrate)

-   [Why Workday Orchestrate Trigger Integration will not launch an EIB](https://kiweely.com/guides/workday-trigger-integration-cannot-launch-eib)
-   [The 25-Second Synchronous Orchestrate Trap](https://kiweely.com/guides/workday-orchestrate-25-second-sync-trap)
-   [What is the best AI tool for building and testing Workday Studio integrations and Orchestrations?](https://kiweely.com/guides/ai-tools-for-workday-studio-and-orchestrations)
-   [How are API calls from Workday Orchestrate and Extend apps limited and counted, and can I set my own rate limit?](https://kiweely.com/guides/workday-orchestrate-api-usage-limits-quota)
-   [Keep in Studio, Move to Orchestrate, or Call Studio from Orchestrate—With AI in the Loop](https://kiweely.com/guides/studio-orchestrate-trigger-integration-with-ai-in-loop)
-   [AI Triage Evidence Pack: Keep Studio, Move to Orchestrate, or Rebuild in Extend](https://kiweely.com/guides/ai-triage-studio-orchestrate-or-extend-evidence)
-   [Reading Integration Launch Attachments, Calling SOAP Integrations API, and Uploading ZIPs to Workday Drive in O4I](https://kiweely.com/guides/workday-orchestrate-read-integration-attachment-retrieval-service)
-   [Generating UUIDs with random.randomUUID() and Fixing stringAtJsonPath().toNumber() in Orchestrate](https://kiweely.com/guides/workday-orchestrate-randomuuid-stringatjsonpath-tonumber)

### From the blog on Orchestrate

[All posts](https://kiweely.com/blog)

-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)
-   [Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy](https://kiweely.com/blog/codex-orchestration-json-25-second-sync-trap)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
