Workday-Pro-Integrations Exam Dumps : Workday Pro Integrations Certification Exam

In XSLT, the processor applies transformation rules by matching nodes using XPath expressions inside statements.

“Templates define the rule, and XPath expressions determine which nodes they apply to.”

This is the foundational mechanism by which XSLT processes XML data.

Why the others are incorrect:

B. The element defines scope, not node matching.

C. invokes a named template but does not itself match nodes.

D. Namespace prefixes are used within XPath, but node matching is based on XPath.

The XML fragment shown follows the Report‑as‑a‑Service (RaaS) structure typical for Workday custom report output:

Megan McNeil

25

7507df6a99664ce7bc0cb902cf370543

Child

Inside each , the target value Relationship_ID resides under:

wd:Dependents_Group

→ wd:Relationship

→ wd:ID (wd:type="Relationship_ID")

When writing the template:

XSLT uses a relative XPath (starting with ./) to navigate from the matched node.

Therefore, the correct XPath should be:

/wd:Dependents_Group/wd:Relationship/wd:ID

That expression selects the wd:ID element so you can then test/extract where wd:type="Relationship_ID".

Why the other options are incorrect:

Option

Why Incorrect

A & B

These use an equality test incorrectly inside the XPath expression — they would not return the node value and are syntactically invalid for value extraction.

C

Missing ./ — would still work in many cases, but Workday XSLT best practice is to use relative paths when inside a match.

Workday Pro Integration guidance for RaaS/XSLT stresses:

Always scope node selection relative to the current context tree using prefix‑qualified XPath expressions.

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.