The scenario describes a Core Connector: Worker integration with specific configurations, and a test case where Jeff Gordon's data doesn't appear in the output despite an Edit Position event. Let's analyze why Jeff Gordon is excluded and what needs to change:
* Current Configuration:
* Integration Field Attributes: Outputs Position Title and Business Title from Position Data.
* Integration Population Eligibility: Filters workers where "Is Manager" = True (only managers).
* Transaction Log Service: Subscribes to "Position Edit Event" transactions.
* Launch Parameters:
* 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
* Test Case:
* Worker: Jeff Gordon (not a manager).
* Action: Edit Position, updating Business Title.
* Event Details: Effective Date 05/24/2024, Entry Moment 05/24/2024 07:58:53 AM.
* Result: Jeff Gordon does not appear in the output.
* Analysis:
* Date Parameters: The integration captures changes between the Last Successful As of Entry Moment (05/23/2024 12:00:00 AM) and the current As of Entry Moment (05/25/2024 12:00:00 AM). Jeff's Edit Position event (Entry Moment 05/24/2024 07:58:53 AM) falls within this range, and its Effective Date (05/24/2024) is before the integration's Effective Date (05/25/2024), making it eligible from a date perspective.
* Transaction Log: Subscribed to "Position Edit Event," which matches Jeff's action (Edit Position), so the event type is correctly captured.
* Field Attributes: Outputs Position Title and Business Title, and Jeff's update to Business Title aligns with these fields.
* Population Eligibility: Filters for "Is Manager" = True. Jeff Gordon is explicitly noted as "not assigned to the manager role," meaning "Is Manager" = False for him. This filter excludes Jeff from the population, regardless of the event or date eligibility.
* Why Jeff is Excluded:TheIntegration Population Eligibilityrestriction ("Is Manager" = True) prevents Jeff Gordon from being included, as he isn't a manager. This filter applies to the entire worker population before events or fields are considered, overriding other conditions.
* Option Analysis:
* A. Transaction Log Subscription: Incorrect. The subscription already includes "Position Edit Event," which matches Jeff's action. Modifying this wouldn't address the population filter.
* B. Integration Population Eligibility: Correct. Changing this to include non-managers (e.g., removing the "Is Manager" = True filter or adjusting it to include all employees) would allow Jeff Gordon to appear in the output.
* C. Date Launch Parameters: Incorrect. Jeff's event (05/24/2024) falls within the date range, so the parameters are not the issue.
* D. Integration Field Attributes: Incorrect. The attributes already include Business Title, which Jeff updated, so this configuration is irrelevant to his exclusion.
* Modification Needed:Adjust theIntegration Population Eligibilityto either:
* Remove the "Is Manager" = True filter to include all workers, or
* Modify it to align with the scenario's intent (e.g., "Worker Type equals Employee") if managers were an unintended restriction.
* Implementation:
* Edit the Core Connector: Worker integration.
* Use the related actionConfigure Integration Population Eligibility.
* Remove or adjust the "Is Manager" = True condition.
* Relaunch the integration and verify Jeff Gordon appears in the output.
References from Workday Pro Integrations Study Guide:
* Core Connectors & Document Transformation: Section on "Configuring Integration Population Eligibility" explains how eligibility filters the worker population before event processing.
* Integration System Fundamentals: Details how population scoping interacts with event subscriptions and launch parameters.