Workday Updated Workday-Pro-Integrations Exam Questions and Answers by tia

The requirement is population filtering, not output formatting. In a Core Connector: Worker integration, Integration Population Eligibility determines which workers qualify for extraction before the connector produces the output file. To include only active workers in the Clinical Staff job family, the eligibility rule must evaluate worker status and job family together. Integration Field Overrides are used when replacing or adding output values, such as a calculated License ID. Integration Attributes control connector-level configuration and do not restrict the worker population. Transaction Log configuration controls which transaction types are detected for change processing, not whether a worker belongs to the desired eligible population. Therefore, the correct configuration step is Integration Population Eligibility.

================

The requirement is to filter a custom report to show only workers terminated after a user-prompted date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions can be combined using AND/OR logic to refine the dataset. Let’s analyze the requirement and options:

Key Conditions:

Workers must be terminated, so the " Worker Status " field must equal " Terminated. "

The termination must occur after a user-specified date, so the " Termination Date " must be greater than the prompted value.

Both conditions must be true for a worker to appear in the report, requiring an AND combination.

Option Analysis:

A. Worker Status is equal to the value " Terminated " OR Termination Date is greater than a value retrieved from a prompt: Incorrect. Using OR means the report would include workers who are terminated (regardless of date) OR workers with a termination date after the prompt (even if not terminated), which doesn’t meet the strict requirement of terminated workers after a specific date.

B. Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a value retrieved from a prompt: Incorrect. Worker Status shouldn’t be a prompted value (it’s fixed as " Terminated " ), and " less than " would show terminations before the date, not after.

C. Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a value retrieved from a prompt: Incorrect. Worker Status shouldn’t be prompted, and " equal to " limits the filter to exact matches, not " after " the date. OR logic also broadens the scope incorrectly.

D. Worker Status is equal to the value " Terminated " AND Termination Date is greater than a value retrieved from a prompt: Correct. This ensures workers are terminated (fixed value) AND their termination date is after the user-entered date, precisely meeting the requirement.

Implementation:

In the custom report’s Filter tab, add two conditions:

Field: Worker Status, Operator: equals, Value: " Terminated " .

Field: Termination Date, Operator: greater than, Value: Prompt for Date (configured as a report prompt).

Set the logical operator between conditions to AND.

Test with a sample date to verify only terminated workers after that date appear.

References from Workday Pro Integrations Study Guide:

Workday Report Writer Fundamentals: Section on " Creating and Managing Filters " details combining conditions with AND/OR logic and using prompts.

Integration System Fundamentals: Notes how filtered reports support integration data sources with dynamic user inputs.

In an XSLT stylesheet, the purpose of declaring the XSLT namespace is to differentiate XSLT instructions (like < xsl:template > , < xsl:value-of > , etc.) from the elements in the source XML.

“XSLT uses XML syntax, so to avoid confusion with the actual data, all XSLT elements must be associated with the XSL namespace xmlns:xsl= " http://www.w3.org/1999/XSL/Transform " .”

This ensures the processor interprets < xsl:* > tags as transformation logic, not content.

Why others are incorrect:

A. XML version is declared separately ( < ?xml version= " 1.0 " ? > )

C. Encoding is set in the XML declaration, not in namespaces.

D. Namespaces are not used to retrieve external transformation rules.

Creating or associating a filename sequence generator is not enough by itself. The EIB must be configured so the File Name launch parameter determines its value at runtime from the sequence generator utility. The correct runtime field is Next Sequence for Integration File Utility. If the launch parameter is not set this way, Workday can still use a static or manually supplied filename, which means the configured sequence generator will not drive the final output filename. Typing the sequence generator name as a static value would not invoke the generator. The issue is also not simply a transformation problem or delivery endpoint problem. The key configuration gap is that the runtime filename value was not linked to the sequence generator output.

================