What option for an outbound EIB uses a Workday-delivered transformation to output a format other than Workday XML?

The "Alternate Output Format" option, configured in the "Get Data" step of an outbound EIB, leverages a Workday-delivered transformation. This feature allows the integration to directly convert the XML output from a Workday RaaS (Report-as-a-Service) or web service call into a different, pre-defined format such as CSV, Text, or Simple XML. This is achieved by selecting the desired format from a dropdown list, which applies a pre-built, maintained-by-Workday transformation without requiring any custom XSLT or report development.

B. XSLT Attachment Transformation: This option applies a transformation specifically to file attachments within the integration data, not to the primary data output itself.
C. Custom Transformation: This option requires the developer to provide their own transformation logic, typically using custom XSLT, and is therefore not a Workday-delivered transformation.
D. Custom Report Transformation: This method uses a custom report as the data source, where the output format is defined within the report's own configuration, making the transformation part of the custom report design, not a separate, Workday-delivered EIB step.

1. Workday Community Documentation, "Enterprise Interface Builder" Guide: The guide details the configuration of an outbound EIB. In the section covering the "Get Data" step, it explicitly describes the "Alternate Output Format" field. It states, "Workday can transform the output of the report into another format. Select the format you want from the prompt list. For example, you can select CSV to transform the XML output into a comma-separated value file." This confirms it is a Workday-provided transformation feature. (Reference: Enterprise Interface Builder Guide, Section: "Create EIB - Get Data Step").

2. Workday Community Documentation, "Workday Studio vs. EIBs" Article: This resource often contrasts the capabilities of different integration tools. It highlights that EIBs are ideal for simple integrations that can use "built-in transformations," referring to features like the "Alternate Output Format," as opposed to Workday Studio, which is required for complex, custom transformations. (Reference: Workday Integration Tools Overview, Section: "When to Use EIBs").