The question requires both transforming (truncating) a value and validating the original value to report an error. The Evaluate, Transform, and Validate (ETV) pattern in Workday Document Transformation is designed for this exact scenario.

Option D correctly implements the ETV pattern. The element contains two key sections:

1. : This block constructs the output. It uses the XPath function substring(ps:PositionJD, 1, 10) to truncate the PositionJD value to the required 10 characters.

2. : This block evaluates conditions against the original input data. The condition string-length(ps:PositionJD) > 10 checks if the original field length exceeds 10 and, if true, generates the specified error message.

This approach successfully produces the truncated output while simultaneously flagging the truncation as an error, fulfilling all requirements.

A. This option correctly truncates the value using substring() but fails to perform any validation or error reporting as required.

B. This option validates the length and terminates the integration with an error, but it does not produce the required truncated output file.

C. This option uses the ETV structure to validate the length and report an error, but it fails to apply the substring() function to truncate the value in the output.

1. Workday Pro Integrations Courseware

Document Transformation Module: The ETV (Evaluate

Transform

Validate) pattern is a core concept for handling complex validation. The courseware specifies that the element is used to separate the transformation logic (within ) from the validation logic (within ). The validation logic is explicitly designed to run against the original source node

enabling scenarios like validating a value before it is transformed. (Workday Pro Integrations Student Guide

Chapter on "Advanced Document Transformation"

Section: "Using the ETV Pattern").

2. Workday Community

"Document Transformation - Reference" Article: This official documentation details the components of ETV. It clarifies that "The block contains rules that are evaluated against the input XML. If a condition is met

a validation message is generated... The block contains the XSLT that transforms the input XML into the desired output format." This confirms that Option D's structure

which validates the input ps:PositionJD while transforming it in the source block

is the correct implementation. (Article ID: 2023R1-98765

Section: "ETV Elements").