The scenario involves a Core Connector: Worker integration with two runs detailed in the integration events report. The goal is to determine whether Brian Hill’s compensation change, effective April 30, 2024, and entered on May 13, 2024, will be included in either of the runs based on their date launch parameters. Let’s analyze each run against the change details to identify the correct answer.
In Workday, the Core Connector: Worker integration in incremental mode (as indicated by the presence of "Last Successful" parameters) processes changes based on the Transaction Log, filtering them by theEntry Moment(when the change was entered) andEffective Date(when the change takes effect). The integration captures changes where:
TheEntry Momentfalls between theLast Successful As of Entry Momentand theAs of Entry Moment, and
TheEffective Datefalls between theLast Successful Effective Dateand theEffective Date.
Brian Hill’s compensation change has:
Entry Moment:05/13/2024 (time not specified, so we assume it occurs at some point during the day, before or up to 11:59:59 PM).
Effective Date:04/30/2024.
Analysis of Run #1
Launch Date:05/15/2024 at 3:00:00 AM
As of Entry Moment:05/15/2024 3:00:00 AM – The latest point for when changes were entered.
Effective Date:05/15/2024 – The latest effective date for changes.
Last Successful As of Entry Moment:05/01/2024 3:00:00 AM – The starting point for entry moments.
Last Successful Effective Date:05/01/2024 – The starting point for effective dates.
For Run #1 to include Brian’s change:
TheEntry Moment(05/13/2024) must be between 05/01/2024 3:00:00 AM and 05/15/2024 3:00:00 AM. Since 05/13/2024 falls within this range (assuming the change was entered before 3:00:00 AM on 05/15/2024, which is reasonable unless specified otherwise), this condition is met.
TheEffective Date(04/30/2024) must be between 05/01/2024 (Last Successful Effective Date) and 05/15/2024 (Effective Date). However, 04/30/2024 isbefore05/01/2024, so this condition isnot met.
Since the effective date of Brian’s change (04/30/2024) precedes theLast Successful Effective Date(05/01/2024), Run #1 will not include this change. In incremental mode, Workday excludes changes with effective dates prior to the last successful effective date, as those are assumed to have been processed in a prior run (before Run #1’s baseline of 05/01/2024).
Analysis of Run #2
Launch Date:05/31/2024 at 3:00:00 AM
As of Entry Moment:05/31/2024 3:00:00 AM – The latest point for when changes were entered.
Effective Date:05/31/2024 – The latest effective date for changes.
Last Successful As of Entry Moment:05/15/2024 3:00:00 AM – The starting point for entry moments.
Last Successful Effective Date:05/15/2024 – The starting point for effective dates.
For Run #2 to include Brian’s change:
TheEntry Moment(05/13/2024) must be between 05/15/2024 3:00:00 AM and 05/31/2024 3:00:00 AM. However, 05/13/2024 isbefore05/15/2024 3:00:00 AM, so this condition isnot met.
TheEffective Date(04/30/2024) must be between 05/15/2024 (Last Successful Effective Date) and 05/31/2024 (Effective Date). Since 04/30/2024 isbefore05/15/2024, this condition is alsonot met.
In Run #2, theEntry Moment(05/13/2024) precedes theLast Successful As of Entry Moment(05/15/2024 3:00:00 AM), meaning the change was entered before the starting point of this run’s detection window. Additionally, theEffective Date(04/30/2024) is well before theLast Successful Effective Date(05/15/2024). Both filters exclude Brian’s change from Run #2.
Conclusion
Run #1:Excluded because the effective date (04/30/2024) is before the Last Successful Effective Date (05/01/2024).
Run #2:Excluded because the entry moment (05/13/2024) is before the Last Successful As of Entry Moment (05/15/2024 3:00:00 AM) and the effective date (04/30/2024) is before the Last Successful Effective Date (05/15/2024).
Brian Hill’s change would have been processed in an earlier run (prior to May 1, 2024) if the integration was running incrementally before Run #1, as its effective date (04/30/2024) predates both runs’ baselines. Given the parameters provided, neither Run #1 nor Run #2 captures this change, makingD. Brian Hill will be excluded from both integration runsthe correct answer.
Workday Pro Integrations Study Guide References
Workday Integrations Study Guide: Core Connector: Worker– Section on "Incremental Processing" explains how changes are filtered based on entry moments and effective dates relative to the last successful run.
Workday Integrations Study Guide: Launch Parameters– Details how "Last Successful As of Entry Moment" and "Last Successful Effective Date" define the starting point for detecting new changes, excluding prior transactions.
Workday Integrations Study Guide: Change Detection– Notes that changes with effective dates before the last successful effective date are assumed processed in earlier runs and are skipped in incremental mode.
