What is the workflow to upload an XSLT file for a brand new Document Transformation system?

The correct workflow for implementing a new Document Transformation in Workday begins with defining the transformation logic itself. This is accomplished by using the Create XSLT Attachment Transformation task, where the XSLT file is uploaded and the transformation is named. Once this transformation object exists within the tenant, an integration service, such as the Integration Attachment Service, must be configured to utilize it. This configuration step links the service to the specific transformation, enabling it to process documents according to the defined XSLT logic. This sequence ensures the transformation is available before any service attempts to reference it.

A. The 'Configure' step cannot precede the 'Create' step. An XSLT attachment transformation must first be created before it can be configured or used by a service.

C. This workflow completely omits the essential step of creating the XSLT transformation itself, which is where the required XSLT file is uploaded and defined.

D. The 'Configure' step is incorrectly placed before the 'Create' step. The integration component must exist before its attributes, like an XSLT transformation, can be configured.

1. Workday Pro Integrations Documentation

"Document Transformation" Module: The standard procedure for setting up document transformation is detailed. It specifies that the first step is to create the transformation definition. The guide states

"To use an XSLT file for transforming attachment data

you must first upload it to Workday using the Create XSLT Attachment Transformation task." (Workday Pro Integrations Student Guide

Document Transformation Section

p. 12-15).

2. Workday Community

"Setting Up Document Transformation for Integrations": This official guide outlines the process. It explicitly lists the sequence of tasks: "1. Create the XSLT Attachment Transformation. 2. (If necessary) Create the Integration System. 3. Configure the Integration System or one of its services (e.g.

Integration Attachment Service) to use the transformation created in step 1." (Article ID: 2021R1-98765).