Refer to the following scenario to answer the question below. Your integration has the following runs in the integration events report (Date format…

The Core Connector: Worker integration evaluates changes based on two key parameters: the transaction's entry date and its effective date, relative to the integration's run parameters. For Run #1 (Effective Date: May 15), the salary change is not included. Although the transaction was entered on May 13 (within the entry date window), its effective date of May 22 is in the future. The integration reports the data as it exists on May 15, at which time the new salary is not yet active. For Run #2 (Effective Date: May 31), the salary change is included. The integration's change detection logic compares the worker's data as of May 31 against the data from the last successful run (effective May 15). Since the salary increase became effective on May 22, a change is detected, and the new data is included in the output.

A. Brian Hill will only be included in the first integration run. This is incorrect because the change is future-dated relative to the first run's effective date and will not be reflected in the output.
B. Brian Hill will be included in both integration runs. This is incorrect. While the worker's record might be processed in the first run, the specific compensation change will not be included as it is not yet effective.
D. Brian Hill will be excluded from both integration runs. This is incorrect because the second run's effective date is after the change's effective date, ensuring the change is captured and processed.

1. Workday Documentation, "Core Connectors: Worker Guide": Section: Change Detection. This guide explains that change detection integrations identify differences in worker data between the Last Successful Effective Date and the current run's Effective Date. A future-dated event, like the one in the scenario, will cause a change to be detected on the first run after its effective date has passed.

2. Workday Documentation, "Integrations Administration Guide": Section: Integration Launch Parameters. This document defines the Effective Date parameter as the primary date for retrieving effective-dated data. It specifies that the integration processes a snapshot of data that is effective as of this date, which is why the future-dated change is ignored in Run #1 but captured in Run #2.