WORKDAY-PRO-INTEGRATIONS practice question 2 of 15

Refer to the following scenario to answer the question below. You have configured a Core Connector: Worker integration, which utilizes the following…

Full set: 108 questions
Refer to the following scenario to answer the question below. You have configured a Core Connector: Worker integration, which utilizes the following basic configuration: • Integration field attributes are configured to output the Position Title and Business Title fields from the Position Data section. • Integration Population Eligibility uses the field Is Manager which returns true if the worker holds a manager role. • Transaction Log service has been configured to Subscribe to specific Transaction Types: Position Edit Event. You launch your integration with the following date launch parameters (Date format of MM/DD/YYYY): • As of Entry Moment: 05/25/2024 12:00:00 AM • Effective Date: 05/25/2024 • Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM • Last Successful Effective Date: 05/23/2024 To test your integration, you made a change to a worker named Jeff Gordon who is not assigned to the manager role. You perform an Edit Position on Jeff Gordon and update their business title to a new value. Jeff Gordon's worker history shows the Edit Position Event as being successfully completed with an effective date of 05/24/2024 and an Entry Moment of 05/24/2024 07:58:53 AM however Jeff Gordon does not show up in your output. What configuration element would have to be modified for the integration to include Jeff Gordon in the output?
Answer options
A: Transaction log subscription
B: Integration Population Eligibility Correct answer
C: Date launch parameters
D: Integration Field Attributes
Correct Answer:
B. Integration Population Eligibility
Explanation

The integration is configured to only process workers who satisfy the Integration Population Eligibility rule, which requires the Is Manager field to be true. The scenario explicitly states that Jeff Gordon is not a manager. Although the transaction log correctly identified the Position Edit Event for Jeff Gordon within the specified date parameters, he was subsequently filtered out because he did not meet the eligibility criteria. To include Jeff Gordon in the output, the population eligibility rule must be modified or removed to allow non-managers.

Why Incorrect

A. Transaction log subscription: This is incorrect. The integration is correctly subscribed to the Position Edit Event, which is the exact change that occurred for the worker.
C. Date launch parameters: This is incorrect. The worker's change event, with an effective date of 05/24/2024, falls within the processing window defined by the launch parameters.
D. Integration Field Attributes: This is incorrect. These attributes define what data to output, not which workers to include. The worker was filtered out before this step was reached.

References

1. Workday Documentation, "Core Connectors" Guide. Section: Set Up Integration Population Eligibility. This section details that the rule configured in the Integration Population Eligibility field acts as a primary filter, and only records that satisfy this condition will be processed and included in the integration output.

2. Workday Documentation, "Core Connectors" Guide. Section: Change Detection for Core Connector: Worker. This documentation explains that the transaction log identifies all workers with relevant business process events. However, these workers are then subject to further filtering, such as population eligibility, before being included in the final output file.

3. Workday Documentation, "Integration System Fundamentals". Chapter: Building and Configuring Integrations. This guide outlines the logical processing flow of integrations, establishing that eligibility and filtering steps are applied to the initial data set before data transformation and output generation occur.

Scroll to Top