Pass the Workday Workday Integrations Workday-Pro-Integrations Questions and answers with CertsForce

For recurring integration schedules, Workday limits how far into the future a recurrence can be scheduled. The maximum end date is tied to the next calendar year, not simply to the same month next year or the current year. Therefore, December 31st of the next calendar year is the correct maximum end date. This allows the integration to continue through the full next calendar year without requiring a shorter May-based cutoff. The current calendar year would end too soon for a monthly recurring schedule configured to continue beyond year-end. The second calendar year option extends too far and exceeds the normal scheduling limit. This question tests schedule governance, not transformation or report logic.

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

The requirement states that the connector output must be transformed before the file is delivered to the endpoint. This means the Document Transformation step must run first, followed by the Document Delivery step.

In Workday, this is managed through the Business Process (BP) attached to the integration system.

From Workday documentation:

“To transform an integration file before delivery, configure the Business Process to run the Document Transformation step before the Document Delivery Service step.”

This ensures that:

The file is converted (via XSLT) to the correct format (e.g., CSV or flat XML)

Only the final, transformed file is sent to the endpoint

Why the others are incorrect:

A. Scheduling separately does not ensure correct sequence.

B. Delivery before transformation would send the wrong file.

D. A separate integration system is unnecessary and not best practice for chained transformations.