The scenario involves a Core Connector: Worker integration configured to output Position Title and Business Title fields for workers who meet the Integration Population Eligibility criteria (Is Manager = true), with the Transaction Log service subscribed to the "Position Edit Event." The integration is launched with specific date parameters, and a test is performed by updating Jared Ellis’ Business Title using the "Change Business Title" related action. Jared is a manager, and the change is logged with an effective date of 05/24/2024 and an entry moment of 05/24/2024 07:58:53 AM. Despite this, Jared does not appear in the output. Let’s determine why and identify the configuration element that needs modification.

In Workday, the Core Connector: Worker integration uses the Transaction Log service to detect changes based on subscribed transaction types. The subscribed transaction type in this case is "Position Edit Event," which is triggered when a position is edited via the "Edit Position" business process. However, the test scenario involves a "Change Business Title" related action, which is a distinct business process in Workday. This action updates the Business Title field but does not necessarily trigger a "Position Edit Event." Instead, it generates a different event type, such as a "Title Change Event" (as noted in Jared’s worker history), depending on how the system logs the action.

The date launch parameters provided are:

As of Entry Moment: 05/25/2024 12:00:00 AM – The latest point for entry moments.

Effective Date: 05/25/2024 – The latest effective date for changes.

Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM – The starting point for entry moments from the last run.

Last Successful Effective Date: 05/23/2024 – The starting point for effective dates from the last run.

Jared’s change has:

Entry Moment: 05/24/2024 07:58:53 AM – Falls between 05/23/2024 12:00:00 AM and 05/25/2024 12:00:00 AM.

Effective Date: 05/24/2024 – Falls between 05/23/2024 and 05/25/2024.

The date parameters correctly cover the time window of Jared’s change, meaning the issue is not with the date range but with the event detection logic. The Transaction Log subscription determines which events are processed by the integration. Since the subscription is set to "Position Edit Event" and the change was made via "Change Business Title" (logged as a "Title Change Event"), the integration does not recognize this event because it is not subscribed to the appropriate transaction type.

To include Jared Ellis in the output, the Transaction Log subscription must be modified to include the event type associated with the "Change Business Title" action, such as "Title Change Event" or a broader category like "Position Related Event" that encompasses both position edits and title changes. This ensures the integration captures the specific update made to Jared’s Business Title.

Let’s evaluate the other options:

B. Date launch parameters: The parameters already include Jared’s entry moment and effective date within the specified ranges (05/23/2024 to 05/25/2024). Adjusting these would not address the mismatch between the subscribed event type and the actual event triggered.

C. Integration Field Attributes: These are set to output Position Title and Business Title, and the change to Business Title is within scope. The field configuration is correct and does not need modification.

D. Integration Population Eligibility: This is set to "Is Manager = true," and Jared is a manager. This filter is functioning as intended and is not the issue.

The root cause is the Transaction Log subscription not aligning with the event type generated by the "Change Business Title" action, making A. Transaction log subscription the correct answer.

Workday Pro Integrations Study Guide References

Workday Integrations Study Guide: Core Connector: Worker – Section on "Transaction Log Configuration" explains how subscribing to specific transaction types filters the events processed by the integration.

Workday Integrations Study Guide: Change Detection – Details how different business processes (e.g., Edit Position vs. Change Business Title) generate distinct event types in the Transaction Log.

Workday Integrations Study Guide: Event Subscription – Notes the importance of aligning subscription types with the specific business actions being tested or monitored.