The Configure Integration Population Eligibility step is the designated phase within the Core Connector framework for defining the overall population of workers the integration will process. To resolve the issue of terminated workers appearing in the output, you must apply a condition rule in this step to filter the population. By creating and applying a rule that evaluates if a worker's status is "Active," the integration will only select active employees for processing before the Data Initialization Service (DIS) performs its change detection comparison. This ensures that terminated workers are excluded from the initial data set, directly addressing the requirement.

A. Configure Integration Attributes for Integration System step to enable Include Inactive Workers in Full File.

This action would have the opposite effect, explicitly instructing the integration to include inactive workers, which contradicts the requirement to exclude them.

B. Configure Integration Transaction Log step to subscribe to everything except termination transactions.

The scenario specifies the integration uses the Data Initialization Service (DIS) for change detection, not the Integration Transaction Log. These are distinct mechanisms.

D. Configure Integration Field Overrides step to use the correct Eligibility Criterion to filter out terminated employees.

The Field Overrides step is used to modify the value or behavior of specific output fields, not to filter the overall population of records processed by the integration.

1. Workday Documentation

"Core Connector for Worker Guide": The guide explicitly details the configuration steps for a Core Connector: Worker integration. The section on "Configure Integration Population Eligibility" states its purpose is to define the criteria for including workers in the integration. It specifies the use of condition rules to filter the population based on criteria such as employment status (e.g.

Active). (Reference: Workday Community

Core Connector for Worker Guide

Section: "Configuring the Integration System").

2. Workday Documentation

"Integration Services: Change Detection": This document differentiates between change detection methods. It clarifies that the Data Initialization Service (DIS) works by comparing snapshots of the entire eligible population between runs

whereas the Transaction Log captures specific business process events. This confirms that modifying Transaction Log subscriptions (Option B) is irrelevant for a DIS-based integration. (Reference: Workday Community

Integration Services Guide

Chapter: "Change Detection").

3. Workday Documentation

"Studio Assembly Guide": While focused on Studio

the principles of Core Connector components are often explained. The documentation on integration components would describe the Integration Field Overrides service as a mechanism to alter individual field values

formats

or data sources post-population selection

reinforcing that it is not the correct tool for population filtering. (Reference: Workday Community

Studio Assembly Guide

Section: "Understanding Integration Services").