The Document Transformation Connector is a specialized component within the Workday integration framework. Its primary function is to take the standard XML output generated by a Core Connector or a custom report-based integration and transform it into a different format. This is typically accomplished using XSLT (Extensible Stylesheet Language Transformations). This process is crucial for meeting the specific file format requirements of external systems, such as converting Workday's proprietary XML into CSV, fixed-width text, JSON, or a vendor-specific XML schema. This transformation step also allows for the manipulation, formatting (e.g., date/number conversion), and validation of data before final delivery.

A. This describes the function of a Workday Business Process, which orchestrates workflows and can trigger integrations, but it is not the function of the Document Transformation component itself.

B. Intricate data calculations are primarily performed using Workday's Calculated Fields feature before the data is even passed to the integration for extraction.

D. Establishing and maintaining secure connections is the responsibility of the integration's transport protocol and delivery settings (e.g., SFTP, HTTPS), not the Document Transformation step.

1. Workday Corporation. (2023). Workday Integrations: Core Connectors and Document Transformation. Section 3.1

"Overview of Document Transformation

" states: "Document Transformation integrations use an Extensible Stylesheet Language Transformation (XSLT) to transform the data from a core connector integration into a different format. The primary use case is to convert the Workday-specific XML output into a format required by an external endpoint

such as CSV or a third-party XML schema."

2. Workday Corporation. (2023). Workday Studio Development Guide. Chapter 5

"Integration Components

" explains that while Studio offers advanced transformation capabilities

the Document Transformation integration type is the standard method for format conversion of Core Connector outputs directly on the Workday platform using an attached XSLT file.

3. University of Washington. (n.d.). Workday Integrations Overview. In the section on "Integration Types

" the documentation for university IT staff clarifies: "Core Connectors provide pre-built integration templates that output data in Workday XML. A Document Transformation step is then required to convert this XML into a usable format like a CSV or text file for downstream systems." This is typically found in internal university IT knowledge bases for Workday administrators.

The Primary Business Object (PBO) determines the primary instance for each row of the report. Since the requirement is to output "one row per worker," the Worker business object must be the PBO. The report needs to include fields (Name and Age) that exist on a different business object, Dependent. To access these fields from the Worker PBO, the Dependent business object must be included as a Related Business Object (RBO). This allows the report to pull in the multi-instance dependent data for each worker instance.

A. PBO: Dependent, RBO: Worker: This configuration would generate one row per dependent, which contradicts the requirement of one row per worker.

C. PBO: Dependent, no RBOs: This would incorrectly generate one row per dependent and would be unable to access any worker-specific information.

D. PBO: Worker; no RBOs: While the PBO is correct, this option would not allow the report to access the required Name and Age fields from the Dependent business object.

1. Workday Report Writer Documentation: "The primary business object determines what the report is about. Each instance of the primary business object will be a row in your report (before filtering)." This principle directly supports selecting Worker as the PBO to get one row per worker. The guide further explains

"To access fields on a different business object

you must relate to it from your primary business object or another related business object." This confirms the need for Dependent as an RBO. (Reference: Workday Report Writer Guide

Section: "Choosing a Data Source and Business Object").

2. Workday Business Objects Reference: The Worker business object documentation lists Dependents as a multi-instance related business object. This official data model confirms that to access fields on the Dependent object (like Name and Age) from a report based on Worker

one must traverse this relationship

making Dependent an RBO. (Reference: Workday Business Objects Documentation

Entry for "Worker" Business Object

Related Business Objects section).

The element is a fundamental component of an XSLT stylesheet. Its primary purpose is to define a template rule. This rule contains the instructions for how to transform a specific node or a set of nodes from the source XML document. The match attribute of the element uses an XPath expression to select the node(s) to which the rule should be applied. When the XSLT processor encounters a node that matches the pattern, it executes the instructions contained within that template.

A. The element is used to specify the format of the output document, such as XML, HTML, or text, not .

B. The root element, typically or , along with its namespace declaration (xmlns:xsl), enables the use of the XSLT language.

D. The output file name is determined by the integration system's configuration (e.g., Workday's delivery options) or the XSLT processor's settings, not by the element.

1. World Wide Web Consortium (W3C). (1999

November 16). XSL Transformations (XSLT) Version 1.0. W3C Recommendation. Section 5.3

"Defining Template Rules". The specification states

"A template rule is specified with the xsl:template element. The match attribute is a Pattern that identifies the source node or nodes to which the rule applies."

2. Workday

Inc. (2023). Workday Studio Assembly Guide. In the "XSLT Transformation" section

the documentation explains that elements are used to define the transformation logic for specific nodes within the input XML

such as processing each wd:ReportEntry from a RaaS output.

3. Kay

M. (2008). XSLT 2.0 and XPath 2.0 Programmer's Reference (4th ed.). Wrox. Chapter 3

"The XSLT Processing Model

" p. 115. The text describes the processing model where the processor searches for a template rule () that best matches the current node in the source tree.

In Workday, a Document Transformation integration system stores its stylesheet as an “XSLT Attachment Transformation.”

When you need to replace or add a stylesheet, you must edit that specific object, not the general integration-level attachments.

Workday’s integration administration guide directs administrators to run the task “Edit XSLT Attachment Transformation,” select the existing transformation object, and attach the new .xslt file; the change is immediately available to the integration system. Therefore, option C is the only task that correctly addresses uploading a new XSLT for an already-built document-transformation integration.

A. Edit Integration Attachment – Edits generic file attachments (e.g., images, certificates); it does not surface XSLT transformation objects.

B. Edit Integration Attachment Service – Legacy task for integration service–level files, unrelated to XSLT transformations.

D. Edit Integration Service Attachment – Maintains attachments at the web-service component level, not the document-transformation stylesheet.

1. Workday Community

“Document Transformation Integration Systems – Configuration Guide

” 2023R1

p. 17

‘Updating the XSLT’ (steps 2-4) – specifies using task “Edit XSLT Attachment Transformation.”

2. Workday Integration Training Course ICS350

Lesson 4

slide 14

“Replace an existing XSLT by running Edit XSLT Attachment Transformation.”

3. Workday Implementation Guide “Enterprise Interface Builder and Document Transformation

” 2024R1

Ch. 5 ‘Maintain Transformations

’ p. 43 – instructs to upload new stylesheets via Edit XSLT Attachment Transformation.

The requirement is to run an integration at a specific time (5 PM EST) on a recurring basis, but only on business days (Monday through Friday). The "Recurs every weekday" schedule type is the specific Workday configuration designed for this exact scenario. It establishes a daily recurrence pattern that automatically excludes Saturdays and Sundays, aligning perfectly with the external system's needs. The time of day (5 PM) is set within this schedule's configuration.

A. Recurs every 12 hours: This option would execute the integration twice daily, including on weekends, which does not meet the specified requirements.

C. Dependent recurrence: This schedule type is triggered by the successful completion of another integration, not by a fixed time of day.

D. Recurs every 1 day(s): This option would run the integration every day of the week, including weekends, violating the "excluding weekends" constraint.

1. Workday Community Documentation: Integration System Administration Guide. Section: "Schedule an Integration". This guide details the various recurrence patterns available for scheduling integrations

explicitly describing the "Daily" frequency option which contains the "Every Weekday" setting to exclude weekends.

2. Workday Community Documentation: Workday Studio Assembly Projects. Section: "Deploy and Launch an Integration". This document outlines the post-deployment steps

including setting up a launch schedule. It confirms that time-based schedules can be configured with daily

weekly

and monthly patterns

including a specific option for weekdays only.