WORKDAY-PRO-INTEGRATIONS practice question 10 of 15
Refer to the following scenario to answer the question below. You have configured a Core Connector: Worker integration, which utilizes the following…
Full set: 108 questionsThe integration fails to include Jared Ellis because the change made to his position is future-dated relative to the integration's launch parameters. The integration runs with an Effective Date of 05/25/2024, which means it evaluates worker data as it exists on that specific date. However, the Edit Position event for Jared Ellis has an effective date of 05/27/2024. Although the transaction's entry moment (05/24/2024) is correctly captured by the transaction log, the actual data change is not yet in effect as of the integration's run date. To include this change, the Effective Date launch parameter must be set to 05/27/2024 or later.
A. Integration Population Eligibility: The scenario states Jared Ellis is a manager, satisfying the Is Manager eligibility rule, so this configuration is correct.
C. Integration Field Attributes: The integration is configured to output the Business Title, which is the specific field that was updated in the Edit Position event.
D. Transaction log subscription: The integration is correctly subscribed to the Position Edit Event, which is the business process that was initiated for the worker.
1. Workday Pro Integrations Courseware
"Core Connectors: Change Detection" Module. This official training material explains that change detection integrations use a combination of launch parameters to create a processing window. The As of Entry Moment parameters identify which transactions occurred
while the Effective Date parameter determines the point-in-time data snapshot for the output. A transaction will be detected but the change will not appear in the output if its effective date is after the integration's effective date.
2. Workday Documentation
"Core Connectors and Document Transformation" Guide
Section: Integration Launch Parameters. This guide details the function of each launch parameter. It specifies that the Effective Date parameter is used to retrieve data as of a specific date. For future-dated events
the Effective Date of the integration run must be on or after the event's effective date to reflect the updated data.
3. Workday Documentation
"Workday Integrations" Guide
Section: Understanding Effective Dating. This section clarifies the concept of effective dating in Workday. It states
"When you run an integration
Workday uses the effective date you specify to determine which data to include... It only includes transactions that are effective on or before that date." This directly supports why Jared Ellis's future-dated change was not included in the output.
Keep practicing
Take the free WORKDAY-PRO-INTEGRATIONS practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other WORKDAY-PRO-INTEGRATIONS practice questions
- Question 1After configuring domain security policies, what task must you run to ensure the most rec…
- Question 2Refer to the following scenario to answer the question below. You have configured a Core …
- Question 3When creating an ISU, what should you do to ensure the user only authenticates via web se…
- Question 4You are configuring integration security for a Core Connector integration system. How do …
- Question 5What option for an outbound EIB uses a Workday-delivered transformation to output a forma…
- Question 6Refer to the following scenario to answer the question below. You have been asked to buil…
