Workday Workday-Pro-Integrations Exam With Confidence Using Practice Dumps

To use a custom report as an integration data source, especially through Report-as-a-Service or an EIB-style extract, the report must be configured so Workday can expose its output in a structured service format. Enabling the report as a Web Service allows the report to be called externally or used by integration tools. The Namespace is required so the XML output has a defined structure and can be referenced properly. XML Aliases for fields, group column headings, and prompts are also required because they control the XML element names used in the integration output. Web service aliases and “linking fields” are not the correct required set. Without these report settings, the integration cannot reliably consume the report as a service-based data source.

================

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.

The requirement is population filtering, not output formatting. In a Core Connector: Worker integration, Integration Population Eligibility determines which workers qualify for extraction before the connector produces the output file. To include only active workers in the Clinical Staff job family, the eligibility rule must evaluate worker status and job family together. Integration Field Overrides are used when replacing or adding output values, such as a calculated License ID. Integration Attributes control connector-level configuration and do not restrict the worker population. Transaction Log configuration controls which transaction types are detected for change processing, not whether a worker belongs to the desired eligible population. Therefore, the correct configuration step is Integration Population Eligibility.

================