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

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.

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

The scenario involves a Core Connector: Candidate Outbound integration requiring a calculated field for the average number of jobs a candidate applied to, which isn’t a delivered Workday field. The task is to output this calculated field in the integration file. Core Connectors in Workday use predefined templates but allow customization through various configuration options. Let’s evaluate the steps:

Context:

Core Connector: Candidate Outbound uses the Data Initialization Service (DIS) to extract candidate data.

A calculated field must be created (e.g., averaging the " Number of Job Applications " field across a candidate’s records).

This value needs to be included in the output file sent to the vendor.

Integration Field Overrides:In Core Connectors, calculated fields are typically incorporated into the output by defining integration field overrides. This feature allows you to map a calculated field to a specific field in the connector’s output structure, overriding the default delivered value (or adding a new field). The calculated field is built separately (e.g., in Report Writer or Calculated Fields) and then referenced in the integration configuration.

Option Analysis:

A. Configure a custom field override service to output the calculation: Incorrect. There’s no " custom field override service " in Workday Core Connectors. This might confuse with integration field overrides, but it’s not a distinct service.

B. Configure integration attributes to output the calculation: Incorrect. Integration attributes define metadata or settings for the integration (e.g., file name, delivery method), not specific field mappings for output data.

C. Configure integration field attributes to output the calculation: Incorrect. " Integration field attributes " isn’t a precise Workday term for this purpose; it may confuse with field-level settings, but field overrides are the correct mechanism.

D. Configure integration field overrides to output the calculation: Correct. This is the standard method in Core Connectors to include calculated fields in the output file by overriding or adding to the delivered field structure.

Implementation:

Create a calculated field (e.g., " Average Job Applications " ) using functions like Arithmetic Calculation to average job application counts.

In the Core Connector configuration, navigate to the Integration Field Overrides section.

Define a new field or override an existing one, mapping it to the calculated field.

Test the integration to ensure the calculated value appears in the output file.

References from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on " Configuring Integration Field Overrides " explains mapping calculated fields to output files.

Integration System Fundamentals: Details how Core Connectors extend delivered functionality with custom calculations.

An Outbound EIB (Enterprise Interface Builder) requires a data source to extract information from Workday. The two valid data source types are:

Custom Report (Advanced or Simple)

Workday Web Service (WWS)

From Workday documentation:

“Outbound EIBs support either a Custom Report marked as Web Service Enabled, or a Workday Public Web Service (WWS) operation, as the data source.”

Custom Reports allow user-defined data with filtering.

Web Services allow access to standard operations like Get_Workers.

Why the other options are incorrect:

A. Business Process is not a data source type.

B. XpressO Reports are not supported for integrations.

C. Business Processes cannot feed EIBs directly as data sources.