Workday-Pro-Integrations Exam - Topic 5 Question 7 Discussion

The scenario requires configuring a Core Connector: Candidate Outbound integration with the Data Initialization Service (DIS) to include only candidates who have undergone a candidate assessment event in Workday. Core Connectors are event-driven integrations that rely on business process transactions or specific data changes to trigger data extraction. Let's analyze how to meet this requirement:

Understanding Core Connector and DIS:The Core Connector: Candidate Outbound integration extracts candidate data based on predefined services and events. The Data Initialization Service (DIS) ensures the initial dataset is populated, but ongoing updates depend on configured integration services that define which candidates to include based on specific events or conditions.

Candidate Assessment Event:In Workday, a 'candidate assessment event' typically refers to a step in the recruiting business process where a candidate completes an assessment. The requirement to filter for candidates with this event suggests limiting the dataset to those who triggered an assessment-related transaction.

Integration Services:In Core Connectors, integration services determine the scope of data extracted by subscribing to specific business events or conditions. For this scenario, you can configure the integration services to monitor the 'Candidate Assessment' event (or a related business process step) and include only candidates who have completed it. This is done by selecting or customizing the appropriate service within the Core Connector configuration to filter the candidate population.

Option Analysis:

A . Configure the integration services to only include candidates with assessments: Correct. This involves adjusting the integration services in the Core Connector to filter candidates based on the assessment event, ensuring only relevant candidates are included in the output file.

B . Set the integration transaction log to subscribe to specific transaction types: Incorrect. The integration transaction log tracks processed transactions for auditing but doesn't control which candidates are included in the output. Subscription to events is handled via integration services, not the log.

C . Make the Candidate Assessment field required in integration field attributes: Incorrect. Integration field attributes define field-level properties (e.g., formatting or mapping), not the population of candidates included. Making a field 'required' doesn't filter the dataset.

D . Create an integration map to output values for candidates with assessments: Incorrect. Integration maps transform or map field values (e.g., converting 'United States' to 'USA') but don't filter the population of candidates included in the extract. Filtering is a service-level configuration.

Implementation:

Edit the Core Connector: Candidate Outbound integration.

In the Integration Services section, select or configure a service tied to the 'Candidate Assessment' event (e.g., a business process completion event).

Ensure the service filters the candidate population to those with an assessment event recorded.

Test the integration to verify only candidates with assessments are extracted.

Reference from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on 'Configuring Integration Services' explains how services define the data scope based on events or conditions.

Integration System Fundamentals