Workday Updated Workday-Pro-Integrations Exam Questions and Answers by reina

In Workday integrations, Document Transformation (DT) using XSLT with Workday Transformation Toolkit (XTT) attributes is used to transform XML data, such as the output from a Core Connector or EIB, into a specific format for third-party systems. In this scenario, you need to transform the ps:Position_ID field within the ps:Position element to a fixed length of 10 characters, truncate the value if it exceeds 10 characters, and align the output to the left. The template must match the ps:Position element and apply these formatting rules using XTT attributes.

Here’s why option A is correct:

Template Matching: The correctly targets the ps:Position element in the XML, as shown in the provided snippet, ensuring the transformation applies to the appropriate node.

XTT Attributes:

xtt:fixedLength="10" specifies that the Pos_ID field should be formatted to a fixed length of 10 characters. If the ps:Position_ID value exceeds 10 characters, it will be truncated (by default, XTT truncates without raising an error unless explicitly configured otherwise), meeting the requirement to truncate if the value exceeds.

xtt:align="left" ensures that the output is left-aligned within the 10-character field, aligning with the requirement to align everything to the left.

XPath Selection: The correctly extracts the ps:Position_ID value (e.g., "P-00030") from the ps:Position_Data child element, as shown in the XML structure.

Output Structure: The ... structure ensures the transformed data is wrapped in meaningful tags for the target system, maintaining consistency with Workday integration practices.

Why not the other options?

B.

xml

WrapCopy

This applies xtt:align="left" to the xsl:template element instead of the Pos_ID element. XTT attributes like fixedLength and align must be applied directly to the element being formatted (Pos_ID), not the template itself, making this incorrect.

C.

xml

WrapCopy

This applies xtt:fixedLength="10" to the Position element and xtt:align="left" to Pos_ID. However, XTT attributes like fixedLength and align should be applied to the specific field being formatted (Pos_ID), not the parent element (Position). This misplacement makes it incorrect.

D.

xml

WrapCopy

This applies xtt:fixedLength="10" to the xsl:template element and xtt:align="left" to Pos_ID. Similar to option B, XTT attributes must be applied to the specific element (Pos_ID) being formatted, not the template itself, making this incorrect.

To implement this in XSLT for a Workday integration:

Use the template from option A to match ps:Position, apply xtt:fixedLength="10" and xtt:align="left" to the Pos_ID element, and extract the ps:Position_ID value using the correct XPath. This ensures the ps:Position_ID (e.g., "P-00030") is formatted to 10 characters, truncated if necessary, and left-aligned, meeting the integration file requirements.

Workday Pro Integrations Study Guide: Section on "Document Transformation (DT) and XTT" – Details the use of XTT attributes like fixedLength and align for formatting data in XSLT transformations, including truncation behavior.

Workday Core Connector and EIB Guide: Chapter on "XML Transformations" – Explains how to use XSLT templates with XTT attributes to transform position data, including fixed-length formatting and alignment.

Workday Integration System Fundamentals: Section on "XTT in Integrations" – Covers the application of XTT attributes to specific fields in XML for integration outputs, ensuring compliance with formatting requirements like length and alignment.

This question pertains to a Core Connector: Worker integration configured with Data Initialization Service (DIS) enabled and scheduled to run once daily. The integration is set to extract only those worker records where changes have occurred in compensation, home address, or business title since the last execution — leveraging Workday’s change detection to avoid full file extracts.

In testing, when a home address update occurs, the integration fails to capture this change in its output. However, all other components — such as worker eligibility, integration field attributes, and Full-Diff parameters — are confirmed to be correctly configured.

The critical element missing here is the event subscription. In Workday, for a Core Connector to recognize changes via Full-Diff or delta mode, it must be properly subscribed to the specific change events that should trigger inclusion in the output. This is done using the Edit Subscriptions configuration.

From the Workday Pro: Integrations documentation:

“The Edit Subscriptions task defines the set of data changes (e.g., job changes, address changes, compensation updates) that the integration system listens for. If an event type is not included in the subscription, changes related to that event will not be picked up in either delta or Full-Diff mode, regardless of other configuration.”

In this scenario, although the integration is configured for Full-Diff, failure to include "Home Address Change" in the subscription list prevents the system from recognizing the update, thereby omitting it from the output file.

Incorrect Options Explained:

A. Configure Integration Field OverridesThis option is used to override or map integration field values but has no impact on whether a change is detected or included in the output.

B. Maintain Integration AttributesWhile this configuration manages connector behavior and filtering rules, it does not control the detection of specific event changes.

D. Configure Integration Transaction LogThis is used for tracking and audit purposes but does not affect change detection or output inclusion.

The scenario involves a Core Connector: Candidate Outbound integration with the Data Initialization Service (DIS), where the vendor requires the "Country" field to be formatted differently (e.g., "United States of America" to "USA"). This is a data transformation requirement, and Core Connectors provide specific tools to handle such formatting. Let’s evaluate the solution:

Requirement:The vendor needs a shortened country code (e.g., "USA" instead of "United States of America") in the output file. This involves transforming the delivered "Country" field value from the Candidate business object into a vendor-specific format.

Integration Maps:In Workday Core Connectors, integration maps are used to transform or map field values from Workday’s format to a vendor’s required format. For example, you can create a map that replaces "United States of America" with "USA," "Canada" with "CAN," etc. This is configured via the "Configure Integration Maps" related action on the integration system, allowing you to define a lookup table or rule-based transformation for the Country field.

Option Analysis:

A. Use an Evaluated Expression calculation and add it to the integration’s report data source: Incorrect. While an Evaluate Expression calculated field could transform the value (e.g., if-then logic), Core Connectors don’t directly use report data sources for output formatting. Calculated fields are better suited for custom reports or EIBs, not Core Connector field mapping.

B. Use the integration related action Configure Integration Population Eligibility: Incorrect. This action filters the population of candidates included (e.g., based on eligibility criteria), not the formatting of individual fields like Country.

C. Use the integration services to only output shortened country codes: Incorrect. Integration services define the dataset or events triggering the integration, not field-level formatting or transformations.

D. Use the integration related action Configure Integration Maps: Correct. Integration maps are the standard Core Connector tool for transforming field values (e.g., mapping "United States of America" to "USA") to meet vendor requirements.

Implementation:

Navigate to the Core Connector: Candidate Outbound integration system.

Use the related action Configure Integration Maps.

Create a new map for the "Country" field (e.g., Source Value: "United States of America," Target Value: "USA").

Apply the map to the Country field in the integration output.

Test the output file to ensure the transformed value (e.g., "USA") appears correctly.

References from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on "Configuring Integration Maps" details how to transform field values for vendor-specific formatting.

Integration System Fundamentals: Explains how Core Connectors handle data transformation through maps rather than calculated fields or services for field-level changes.

In an XSLT stylesheet, the purpose of declaring the XSLT namespace is to differentiate XSLT instructions (like , , etc.) from the elements in the source XML.

“XSLT uses XML syntax, so to avoid confusion with the actual data, all XSLT elements must be associated with the XSL namespace xmlns:xsl="http://www.w3.org/1999/XSL/Transform ".”

This ensures the processor interprets tags as transformation logic, not content.

Why others are incorrect:

A. XML version is declared separately ()

C. Encoding is set in the XML declaration, not in namespaces.

D. Namespaces are not used to retrieve external transformation rules.