Authentic Workday Certification Exam Workday-Pro-Integrations Questions Answers

In the Workday Pro Integrations program, the process of uploading an XSLT file for a brand-new Document Transformation system follows a specific workflow designed to ensure the transformation logic is properly attached and configured within the integration system. The correct sequence involves first creating the XSLT Attachment Transformation and then configuring the Integration Attachment Service to utilize it. Here's a step-by-step breakdown based on Workday's integration methodology:

Create XSLT Attachment Transformation:

The initial step is to create an XSLT Attachment Transformation object within Workday. This involves uploading the XSLT file, which contains the transformation logic needed to convert XML data into the desired format for the Document Transformation system. In Workday, XSLT (Extensible Stylesheet Language Transformations) is used to define how data from a source (typically in XML format) is transformed into an output format compatible with an external system.

To do this, you navigate to the Integration System, access the related actions, and select the option to create a new "XSLT Attachment Transformation." You then name the transformation, upload the XSLT file (with a size limit of 30 MB as per Workday specifications), and save it. This step establishes the transformation logic as an object that can be referenced by the integration system.

Configure Integration Attachment Service:

Once the XSLT Attachment Transformation is created, the next step is to configure the Integration Attachment Service to incorporate this transformation. The Integration Attachment Service is a component of the Document Transformation system that handles the delivery or processing of the transformed data.

In this step, you edit the integration system, navigate to the "Services" tab, and configure the Integration Attachment Service. Here, you specify the previously created XSLT Attachment Transformation as the transformation to be applied. This links the XSLT logic to the integration workflow, ensuring that the data processed by the Document Transformation system is transformed according to the uploaded XSLT file.

Why Other Options Are Incorrect:

A. Configure XSLT Attachment Transformation, then Create Integration Attachment Service: This is incorrect because you cannot "configure" an XSLT Attachment Transformation before it exists. It must first be created as an object in Workday before any configuration or association with services can occur.

C. Create Integration Attachment Service, then Configure Integration Attachment Service: This option skips the creation of the XSLT Attachment Transformation entirely, which is a critical step. Without the transformation defined, configuring the service alone would not enable the XSLT upload or its functionality.

D. Configure Integration Attachment Service, then Create Integration Service Attachment: This sequence is reversed and misleading. The Integration Attachment Service must be configured to use an existing XSLT Attachment Transformation, not the other way around. Additionally, "Create Integration Service Attachment" is not a standard term in this context within Workday documentation.

Workday Pro Integrations Study Guide References:

Workday Integration System Fundamentals: This section outlines the components of an integration system, including the use of XSLT for document transformation and the role of attachment services.

Document Transformation Module: Specifically details the process of uploading and applying XSLT files, emphasizing the creation of an XSLT Attachment Transformation followed by its configuration within the integration services.

Core Connectors and Document Transformation Course Manual: Provides practical steps for setting up transformations, including the sequence of creating and then configuring transformation attachments (e.g., Activities related to "Upload a Custom XSLT Transformation" and "Edit XSLT Attachment Transformation").

Workday Community Documentation: Confirms that XSLT files are uploaded as attachment transformations and then linked to services like the Integration Attachment Service for processing.

To surface a Calculated Field in a Core Connector: Worker (CCW) outbound, you use an Integration Field Override to substitute the connector’s default source with your calculated value. An integration map (Option A) is intended to translate or normalize code values (for example, mapping internal Worker Type codes to the vendor’s codes), not to replace the source of a field. Integration attributes (Option D) and integration field attributes (Option C) manage connector behavior and attributes, but they do not replace a field’s data source with a calculated field. Therefore, the correct method to “pull” a calculated field into the CCW output is an Integration Field Override (Option B).

Why the other elements in the scenario matter (and how they’re handled) — with exact extracts from your materials:

Mapping Worker Type to external codes → Integration Maps (supports, but not the asked action):Your deployment guides call out maintaining and using Integration System Maps for code translations. This is exactly where you’d map “Worker Type” to the external system’s codes, but it is not how you inject a calculated field into the payload.

“Maintenance of Integration System Maps”

“WORKDAY SETUP – NON STATIC MAPS” and “WORKDAY SETUP – STATIC MAPS” (table of contents for configuration of maps)

Filename requires timestamp/sequence number → Sequence Generator (supports the scenario):Your Time Tracking/PECI deployment guide explicitly includes a Sequence Generator configuration that’s used with certified connectors to build compliant, unique file names (often with timestamps and/or sequence numbers) before delivery.

“3.6 Sequence Generator” (configuration item for certified integrations used in file naming)

Transformation before delivery → Standard integration flow (transform then deliver):The same deployment materials describe document/file delivery mechanics (for example, SFTP), which occur after the integration produces/transforms the document. This supports the scenario requirement that transformation happens prior to transmission.

“4. FILE DELIVERY SERVICE … 4.4 SFTP Configuration” (document delivery occurs after the integration generates/transforms the output)

Security posture for integrations (context):For outbound/system users and secure delivery, the Workday Authentication & Security guide documents integration-appropriate authentication (e.g., X.509) and general integration security steps — relevant background for productionizing CCW but not directly affecting how to bring a calculated field into the payload.

“X509 Recommended for web services users and integrations that use an integration system user account.”

Putting it all together for the scenario:

Use Integration Field Override to point the CCW field to your Calculated Field for UPN → (Correct answer: B).

Use Integration Maps to translate Worker Type to the vendor’s codes (supports the mapping requirement).

Configure filename rules via Sequence Generator to include timestamp and sequence in the produced file name (supports the file-naming requirement).

Ensure the document transformation runs as part of the integration generation step and then deliver via SFTP (file delivery service).

References (Workday Pro: Integrations-aligned materials):

GPC_PECI_TimeTracking_DeploymentGuide_CloudPay.pdf — Sections “3.6 Sequence Generator” and “4. File Delivery Service” (delivery occurs after file generation/transform).

GPC_PECI_DeploymentGuide_CloudPay_2.9.pdf — Map configuration sections (“WORKDAY SETUP – NON STATIC MAPS”, “WORKDAY SETUP – STATIC MAPS”).

GPC_PECI_UserGuide_CloudPay_2.1.1.pdf — “Maintenance of Integration System Maps.”

Admin-Guide-Authentication-and-Security.pdf — Integration security notes, including X.509 recommendation for integrations.

This scenario addresses an issue where a Core Connector: Worker integration — with DIS enabled and Full-Diff mode configured — unexpectedly includes terminated workers in the output, despite a requirement to include only active workers.

The correct step to address this issue is the configuration of Integration Population Eligibility.

From the Workday Pro: Integrations – Core Connector Configuration Guide, the relevant extract states:

“The Integration Population Eligibility step allows users to define which workers or populations are eligible to be included in the integration output. This includes filtering by worker status, organization, supervisory org, or other eligibility criteria. If this is not configured to exclude terminated workers, the integration will include all workers who meet the event conditions, regardless of their current status.”

Even though the integration uses change detection and the correct launch parameters, Workday still considers any worker with a qualifying change, including those terminated, unless they are explicitly excluded via eligibility rules.

Therefore, to prevent terminated workers from appearing in the output, you must set a filter in the Integration Population Eligibility step to include only active workers (e.g., using Worker.Status = Active or similar criteria).

Incorrect Options Explained:

A. Configure Integration Attributes... Include Inactive Workers in Full FileThis option would cause inactive (e.g., terminated) workers to be included when enabled. It doesn’t help filter them out.

B. Configure Integration Transaction Log... subscribe to everything except terminationSubscription controls which events trigger processing but does not control population eligibility. Terminated workers with address changes prior to termination could still appear if eligibility is not defined.

D. Configure Integration Field Overrides... use Eligibility CriterionField Overrides change data mappings or formats, not population eligibility. It cannot exclude terminated workers.