Pass Workday-Pro-Integrations Exam with Updated Workday-Pro-Integrations Exam Dumps PDF 2026 [Q26-Q48]

Topic	Details
Topic 1	Integrations: This section of the exam measures the skills of Integration Specialists and covers the full spectrum of integration techniques in Workday. It includes an understanding of core integration architecture, APIs, Workday Studio, and integration system user setup. The focus is on building scalable, maintainable, and secure integrations that ensure seamless system interoperability.
Topic 2	Enterprise Interface Builders: This section of the exam measures the skills of Integration Developers and covers the use of Workday’s Enterprise Interface Builder (EIB) to design, deploy, and maintain inbound and outbound integrations. It evaluates the candidate’s ability to create templates, configure transformation rules, schedule integrations, and troubleshoot EIB workflows efficiently.
Topic 3	Cloud Connect: This section of the exam measures the skills of Workday Implementation Consultants and focuses on using Workday Cloud Connect solutions for third-party integration. It includes understanding pre-built connectors, configuration settings, and how to manage data flow between Workday and external systems while ensuring security and data integrity.

Q26. You are configuring an EIB that uses a custom report as its data source. When attempting to transfer ownership of the report to the Integration System User (ISU), the ISU does not appear as an option for new report owners. You confirm that the ISU already has the necessary access to the report data source and related fields.
Within the Custom Report Creation domain, which security configuration should you update to allow the ISU to appear as a valid report owner?

Assign the ISSG to a row within the Report/Task Permissions table that has Modify access enabled.

Assign the ISSG to a row within the Integration Permissions table that has Get access enabled.

Assign the ISSG to a row within the Report/Task Permissions table that has View access enabled.

Assign the ISSG to a row within the Integration Permissions table that has Put access enabled.

Q27. What is the purpose of a namespace in the context of a stylesheet?

Provides elements you can use in your code.

Indicates the start and end tag names to output.

Restricts the data the processor can access.

Controls the filename of the transformed result.

In the context of a stylesheet, particularly within Workday’s Document Transformation system where XSLT (Extensible Stylesheet Language Transformations) is commonly used, a namespace serves a critical role in defining the scope and identity of elements and attributes. The correct answer, as aligned with Workday’s integration practices and standard XSLT principles, is that a namespace “provides elements you can use in your code.” Here’s a detailed explanation:
Definition and Purpose of a Namespace:
A namespace in an XML-based stylesheet (like XSLT) is a mechanism to avoid naming conflicts by grouping elements and attributes under a unique identifier, typically a URI (Uniform Resource Identifier). This allows different vocabularies or schemas to coexist within the same document or transformation process without ambiguity.
In XSLT, namespaces are declared in the stylesheet using the xmlns attribute (e.g., xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” for XSLT itself). These declarations define the set of elements and functions available for use in the stylesheet, such as <xsl:template>, <xsl:value-of>, or <xsl:for-each>.
For example, when transforming Workday data (which uses its own XML schema), a namespace might be defined to reference Workday-specific elements, enabling the stylesheet to correctly identify and manipulate those elements.
Application in Workday Context:
In Workday’s Document Transformation integrations, namespaces are essential when processing XML data from Workday (e.g., Core Connector outputs) or external systems. The namespace ensures that the XSLT processor recognizes the correct elements from the source XML and applies the transformation rules appropriately.
Without a namespace, the processor might misinterpret elements with the same name but different meanings (e.g., <name> in one schema vs. another). By providing a namespace, the stylesheet gains access to a specific vocabulary of elements and attributes, enabling precise coding of transformation logic.
Why Other Options Are Incorrect:
B . Indicates the start and end tag names to output: This is incorrect because namespaces do not dictate the structure (start and end tags) of the output. That is determined by the XSLT template rules and output instructions (e.g., <xsl:output> or literal result elements). Namespaces only define the identity of elements, not their placement or formatting in the output.
C . Restricts the data the processor can access: While namespaces help distinguish between different sets of elements, they do not inherently restrict data access. Restrictions are more a function of security settings or XPath expressions within the stylesheet, not the namespace itself.
D . Controls the filename of the transformed result: Namespaces have no bearing on the filename of the output. In Workday, the filename of a transformed result is typically managed by the Integration Attachment Service or delivery settings (e.g., SFTP or email configurations), not the stylesheet’s namespace.
Practical Example:
Suppose you’re transforming a Workday XML file containing employee data into a custom format. The stylesheet might include:
<xsl:stylesheet version=”1.0″ xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” xmlns:wd=”http://www.workday.com/ns”>
<xsl:template match=”wd:Employee”>
<EmployeeName><xsl:value-of select=”wd:Name”/></EmployeeName>
</xsl:template>
</xsl:stylesheet>
Here, the wd namespace provides access to Workday-specific elements like <wd:Employee> and <wd:Name>, which the XSLT processor can then use to extract and transform data.
Workday Pro Integrations Study Guide Reference:
Workday Integration System Fundamentals: Explains XML and XSLT basics, including the role of namespaces in identifying elements within stylesheets.
Document Transformation Module: Highlights how namespaces are used in XSLT to process Workday XML data, emphasizing their role in providing a vocabulary for transformation logic (e.g., “Understanding XSLT Namespaces”).
Core Connectors and Document Transformation Course Manual: Includes examples of XSLT stylesheets where namespaces are declared to handle Workday-specific schemas, reinforcing that they provide usable elements.
Workday Community Documentation: Notes that namespaces are critical for ensuring compatibility between Workday’s XML output and external system requirements in transformation scenarios.

Q28. A calculated field used as a field override in a Connector is not appearing in the output. Assuming the field has a value, what could cause this to occur?

Access not provided to calculated field data source.

Access not provided to all fields in the calculated field.

Access not provided to Connector calculated field web service.

Access not provided to all instances of calculated field.

Q29. Refer to the following scenario to answer the question below.
You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data. The vendor receiving the file requires marital status values to be sent using a list of codes that they have provided instead of the text values that Workday uses internally and if a text value in Workday does not align with the vendors list of codes the integration should report ” OTHER ” .
What configuration is required to output the list of codes required from by the vendor instead of Workday ‘ s values in this integration?

Configure Integration Maps with a blank Default

Configure Integration Attributes with a blank Default

Configure Integration Maps with ” OTHER ” as a Default

Configure Integration Attributes with ” OTHER ” as a Default

The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data. The vendor requires marital status values to be transformed from Workday’s internal text values (e.g., ” Married, ” ” Single ” ) to a specific list of codes (e.g., ” M, ” ” S ” ), and any Workday value not matching the vendor’s list should output ” OTHER. ” Let’s analyze the configuration:
* Requirement:Transform the ” Marital Status ” field values into vendor-specific codes, with a fallback to
” OTHER ” for unmapped values. This is a field-level transformation, common in Core Connectors when aligning Workday data with external system requirements.
* Integration Maps:In Core Connectors, Integration Maps are the primary tool for transforming field values. You create a map that defines source values (Workday’s marital status text) and target values (vendor’s codes). The ” Default ” setting in an integration map specifies what value to output if a Workday value isn’t explicitly mapped. Here, setting the default to ” OTHER ” ensures that any marital status not in the vendor’s list (e.g., a new Workday value like ” Civil Union ” not recognized by the vendor) is output as ” OTHER. “
* Option Analysis:
* A. Configure Integration Maps with a blank Default: Incorrect. A blank default would leave the field empty or pass the original Workday value for unmapped cases, not ” OTHER, ” failing the requirement.
* B. Configure Integration Attributes with a blank Default: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery method), not field value transformations. They don’t support mapping or defaults for specific fields like marital status.
* C. Configure Integration Maps with ” OTHER ” as a Default: Correct. This uses Integration Maps to map Workday values to vendor codes and sets ” OTHER ” as the default for unmapped values, meeting the requirement fully.
* D. Configure Integration Attributes with ” OTHER ” as a Default: Incorrect. Integration Attributes don’t handle field-level transformations or defaults for data values, making this option inapplicable.
* Implementation:
* Edit the Core Connector: Worker integration.
* Use the related action Configure Integration Maps.
* Create a map for the ” Marital Status ” field (e.g., ” Married ” # ” M, ” ” Single ” # ” S ” ).
* Set the Default Value to ” OTHER ” in the map configuration.
* Test the output to ensure mapped values use vendor codes and unmapped values return ” OTHER. ” References from Workday Pro Integrations Study Guide:
* Core Connectors & Document Transformation: Section on ” Configuring Integration Maps ” explains mapping field values and using defaults for unmapped cases.
* Integration System Fundamentals: Highlights how Core Connectors transform data to meet vendor specifications.

Q30. What XSL component is required to execute valid transformation instructions in the XSLT code?

xsl:template

xsl:apply-template

xsl:call-template

xsl:output

Q31. What is the limitation when assigning ISUs to integration systems?

An ISU can be assigned to five integration systems.

An ISU can be assigned to an unlimited number of integration systems.

An ISU can be assigned to only one integration system.

An ISU can only be assigned to an ISSG and not an integration system.

Q32. You have been asked to refine a report which outputs one row per worker and is being used in an integration that sends worker data to one of your third-party systems. The integration should only send workers who have been hired in the last 30 days. Where in the custom report definition can you specify a condition that would include only workers who have been hired in the last 30 days?

Subfilter

Output

Columns

Filter

In Workday, when refining a custom report to include specific conditions such as limiting the output to workers hired in the last 30 days, the appropriate place to specify this condition is within theFiltertab of the custom report definition. The Filter tab allows you to define criteria that determine which instances of the primary business object (in this case, “Worker”) are included in the report output. This is critical for integrations, as the filtered data ensures that only relevant records are sent to the third-party system.
The requirement here is to restrict the report to workers hired within the last 30 days. In Workday reporting, this can be achieved by adding a filter condition on the “Hire Date” field of the Worker business object.
Specifically, you would configure the filter to compare the “Hire Date” against a dynamic date range, such as
“Current Date minus 30 days” to “Current Date.” This ensures the report dynamically adjusts to include only workers hired in the last 30 days each time it runs, which aligns with the needs of an integration sending real- time data to a third-party system.
Here’s why the other options are incorrect:
* A. Subfilter: Subfilters in Workday are used to further refine data within a related business object or a subset of data already filtered by the primary filter. They are not the primary mechanism for applying a condition to the main dataset (e.g., all workers). For this scenario, asubfilter would be unnecessary since the condition applies directly to the Worker business object, not a related object.
* B. Output: The Output section of a custom report definition controls how the report is displayed or delivered (e.g., file format, scheduling), not the data selection criteria. It does not allow for specifying conditions like hire date ranges.
* C. Columns: The Columns tab defines which fields are displayed in the report output (e.g., Worker ID, Name, Hire Date). While you can add the “Hire Date” field here for visibility, it does not control which workers are included in the report-that is the role of the Filter tab.
To implement this in practice:
* In the custom report definition, go to theFiltertab.
* Add a new filter condition.
* Select the “Hire Date” field from the Worker business object.
* Set the operator to “in the range” and define the range as “Current Date – 30 days” to “Current Date” (using dynamic date functions available in Workday).
* Save and test the report to ensure it returns only workers hired within the last 30 days.
This filtered report can then be enabled as a web service (via the Advanced tab) or used in an Enterprise Interface Builder (EIB) or Workday Studio integration to send the data to the third-party system, meeting the integration requirement.
References from Workday Pro Integrations Study Guide:
* Workday Report Writer Fundamentals: Section on “Creating and Managing Filters” explains how filters are used to limit report data based on specific conditions, such as date ranges.
* Integration System Fundamentals: Discusses how custom reports serve as data sources for integrations and the importance of filters in defining the dataset.
* Core Connectors & Document Transformation: Highlights the use of filtered custom reports in outbound integrations to third-party systems.

Q33. You are creating an outbound connector using the Core Connector: Organization Outbound template. The vendor has provided the following requirements for how the data should appear in the output file.

The vendor would also like to change the default document retention policy of 30 days to 7 days. What tasks do you need to use to configure this in your connector?

Configure Integration Maps and Configure Integration Attributes

Configure Integration Field Overrides and Configure Integration Field Attributes

Configure Integration Field Overrides and Configure Integration Attributes

Configure Integration Maps and Configure Integration Field Attributes

Q34. This is the XML file generated from a Core Connector; Positions integration.

When performing an XSLT Transformation on the Core Connector: Positions XML output file, you want to show a hyperlink of positions that are not available for hiring as an entry in the Message tab.
What are all the needed ETV items to meet the above requirements?

Q35. Refer to the following XML to answer the question below.

You are an integration developer and need to write XSLT to transform the output of an EIB which is using a web service enabled report to output worker data along with their dependents. You currently have a template which matches on wd:Dependents_Group to iterate over each dependent. Within the template which matches on wd:Dependents_Group you would like to output a relationship code by using an < xsl:choose > statement.
What XSLT syntax would be used to output SP when the dependent relationship is spouse, output CH when the dependent relationship is child, otherwise output OTHER?

Q36. Refer to the following scenario to answer the question below.
You have configured a Core Connector: Worker integration, which utilizes the following basic configuration:
* Integration field attributes are configured to output the Position Title and Business Title fields from the Position Data section.
* Integration Population Eligibility uses the field Is Manager which returns true if the worker holds a manager role.
* Transaction Log service has been configured to Subscribe to specific Transaction Types: Position Edit Event.
You launch your integration with the following date launch parameters (Date format of MM/DD/YYYY):
* As of Entry Moment: 05/25/2024 12:00:00 AM * Effective Date: 05/25/2024
* Last Successful As of Entry Moment: 05/23/2024 12:00:00 AM
* Last Successful Effective Date: 05/23/2024
To test your integration, you made a change to a worker named Jared Ellis who is assigned to the manager role for the IT Help Desk department. You use the Change Business Title related action on Jared and update the Business Title of the position to a new value. Jared Ellis’ worker history shows the Title Change Event as being successfully completed with an effective date of 05/24/2024 and an Entry Moment of 05/24/2024 07:58:53 AM however Jared Ellis does not show up in your output. What configuration element would have to be modified for the integration to include Jared Ellis in the output?

Transaction log subscription

Date launch parameters

Integration Field Attributes

Integration Population Eligibility

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 Reference
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.

Q37. You are configuring the Core Connector: Location to send location data to a new global facilities management system. You must meet three specific requirements:
Task A: The facilities system requires that in addition to the default public address, the private address should also be included.
Task B: The facilities system uses the status codes “A” for Active and “I” for Inactive. You need to translate Workday’s “Active” and “Inactive” values from the Location Status field.
Task C: The facilities system requires a “Building Manager” value. You have already built a Calculated Field that retrieves the Facilities Manager role for each location, and you need to send this data in the integration.
How do you configure these tasks in the integration system?

Task A: Integration Attributes
Task B: Integration Field Override
Task C: Integration Map

Task A: Integration Attribute
Task B: Integration Map
Task C: Integration Field Override

Task A: Integration Map
Task B: Integration Attribute
Task C: Integration Field Override

Task A: Integration Field Override
Task B: Integration Map
Task C: Integration Attribute

Q38. Refer to the following scenario to answer the question below.
You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data. The vendor receiving the file requires marital status values to be sent using a list of codes that they have provided instead of the text values that Workday uses internally and if a text value in Workday does not align with the vendors list of codes the integration should report “OTHER”.
What configuration is required to output the list of codes required from by the vendor instead of Workday’s values in this integration?

Configure Integration Maps with a blank Default

Configure Integration Attributes with a blank Default

Configure Integration Maps with “OTHER” as a Default

Configure Integration Attributes with “OTHER” as a Default

The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data. The vendor requires marital status values to be transformed from Workday’s internal text values (e.g., “Married,” “Single”) to a specific list of codes (e.g., “M,” “S”), and any Workday value not matching the vendor’s list should output “OTHER.” Let’s analyze the configuration:
Requirement:Transform the “Marital Status” field values into vendor-specific codes, with a fallback to “OTHER” for unmapped values. This is a field-level transformation, common in Core Connectors when aligning Workday data with external system requirements.
Integration Maps:In Core Connectors, Integration Maps are the primary tool for transforming field values. You create a map that defines source values (Workday’s marital status text) and target values (vendor’s codes). The “Default” setting in an integration map specifies what value to output if a Workday value isn’t explicitly mapped. Here, setting the default to “OTHER” ensures that any marital status not in the vendor’s list (e.g., a new Workday value like “Civil Union” not recognized by the vendor) is output as “OTHER.” Option Analysis:
A . Configure Integration Maps with a blank Default: Incorrect. A blank default would leave the field empty or pass the original Workday value for unmapped cases, not “OTHER,” failing the requirement.
B . Configure Integration Attributes with a blank Default: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery method), not field value transformations. They don’t support mapping or defaults for specific fields like marital status.
C . Configure Integration Maps with “OTHER” as a Default: Correct. This uses Integration Maps to map Workday values to vendor codes and sets “OTHER” as the default for unmapped values, meeting the requirement fully.
D . Configure Integration Attributes with “OTHER” as a Default: Incorrect. Integration Attributes don’t handle field-level transformations or defaults for data values, making this option inapplicable.
Implementation:
Edit the Core Connector: Worker integration.
Use the related action Configure Integration Maps.
Create a map for the “Marital Status” field (e.g., “Married” → “M,” “Single” → “S”).
Set the Default Value to “OTHER” in the map configuration.
Test the output to ensure mapped values use vendor codes and unmapped values return “OTHER.” Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on “Configuring Integration Maps” explains mapping field values and using defaults for unmapped cases.
Integration System Fundamentals: Highlights how Core Connectors transform data to meet vendor specifications.

Q39. The following XML code was generated through a RaaS that will be used in an EIB.

Within a template that matches on wd:Report_Entry, what XPath expression do you use to select the value of the Relationship_ID element?

wd:Dependents_Group/wd:Relationship/wd:ID/wd:type=’Relationship_ID’

wd:Dependents_Group/wd:Relationship/wd:ID

./wd:Dependents_Group/wd:Relationship/wd:ID

Q40. Refer to the following scenario to answer the question below.
You need to configure a Core Connector: Candidate Outbound integration for your vendor. The connector requires the data initialization service (DIS).
The vendor requests additional formatting of the candidate Country field. For example, if a candidate’s country is the United States of America, the output should show USA.
What steps do you follow to meet this request?

Use an Evaluated Expression calculation and add it to the integration’s report data source.

Use the integration related action Configure Integration Population Eligibility.

Use the integration services to only output shortened country codes.

Use the integration related action Configure Integration Maps.

The scenario involves a Core Connector: Candidate Outbound integration with the Data Initialization Service (DIS), where the vendor requires the “Country” field to be formatted differently (e.g., “United States of America” to “USA”). This is a data transformation requirement, and Core Connectors provide specific tools to handle such formatting. Let’s evaluate the solution:
* Requirement:The vendor needs a shortened country code (e.g., “USA” instead of “United States of America”) in the output file. This involves transforming the delivered “Country” field value from the Candidate business object into a vendor-specific format.
* Integration Maps:In Workday Core Connectors, integration maps are used to transform or map field values from Workday’s format to a vendor’s required format. For example, you can create a map that replaces “United States of America” with “USA,” “Canada” with “CAN,” etc. This is configured via the
“Configure Integration Maps” related action on the integration system, allowing you to define a lookup table or rule-based transformation for the Country field.
* Option Analysis:
* A. Use an Evaluated Expression calculation and add it to the integration’s report data source:
Incorrect. While an Evaluate Expression calculated field could transform the value (e.g., if-then logic), Core Connectors don’t directly use report data sources for output formatting. Calculated fields are better suited for custom reports or EIBs, not Core Connector field mapping.
* B. Use the integration related action Configure Integration Population Eligibility: Incorrect. This action filters the population of candidates included (e.g., based on eligibility criteria), not the formatting of individual fields like Country.
* C. Use the integration services to only output shortened country codes: Incorrect. Integration services define the dataset or events triggering the integration, not field-level formatting or transformations.
* D. Use the integration related action Configure Integration Maps: Correct. Integration maps are the standard Core Connector tool for transforming field values (e.g., mapping “United States of America” to “USA”) to meet vendor requirements.
* Implementation:
* Navigate to the Core Connector: Candidate Outbound integration system.
* Use the related action Configure Integration Maps.
* Create a new map for the “Country” field (e.g., Source Value: “United States of America,” Target Value: “USA”).
* Apply the map to the Country field in the integration output.
* Test the output file to ensure the transformed value (e.g., “USA”) appears correctly.
References from Workday Pro Integrations Study Guide:
* Core Connectors & Document Transformation: Section on “Configuring Integration Maps” details how to transform field values for vendor-specific formatting.
* Integration System Fundamentals: Explains how Core Connectors handle data transformation through maps rather than calculated fields or services for field-level changes.

Q41. Refer to the following XML data source to answer the question below.

You need the integration file to format the ps:Position_ID field to 10 characters, truncate the value if it exceeds, and align everything to the left.
How will you start your template match on ps:Position to use Document Transformation (DT) to do the transformation using XTT?

Q42. Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled that runs once daily. The integration must extract only active worker records with changes to compensation, home address, or business title since the last run 24 hours ago, using Workday’s change detection to avoid full extracts.
During testing, an employee’s home address is updated, but the integration does not detect the change in the output. The employee is eligible, the connector uses the correct integration field attributes, and the launch parameters are properly configured for a Full-Diff extract.
What configuration task must you modify from the integration system to ensure the expected change is included in the output?

Configure Integration Field Overrides

Maintain Integration Attributes

Edit Subscriptions

Configure Integration Transaction Log

This question pertains to a Core Connector: Worker integration configured with Data Initialization Service (DIS) enabled and scheduled to run once daily. The integration is set to extract only those worker records where changes have occurred in compensation, home address, or business title since the last execution – leveraging Workday’s change detection to avoid full file extracts.
In testing, when a home address update occurs, the integration fails to capture this change in its output. However, all other components – such as worker eligibility, integration field attributes, and Full-Diff parameters – are confirmed to be correctly configured.
The critical element missing here is the event subscription. In Workday, for a Core Connector to recognize changes via Full-Diff or delta mode, it must be properly subscribed to the specific change events that should trigger inclusion in the output. This is done using the Edit Subscriptions configuration.
From the Workday Pro: Integrations documentation:
“The Edit Subscriptions task defines the set of data changes (e.g., job changes, address changes, compensation updates) that the integration system listens for. If an event type is not included in the subscription, changes related to that event will not be picked up in either delta or Full-Diff mode, regardless of other configuration.” In this scenario, although the integration is configured for Full-Diff, failure to include “Home Address Change” in the subscription list prevents the system from recognizing the update, thereby omitting it from the output file.
Incorrect Options Explained:
A . Configure Integration Field OverridesThis option is used to override or map integration field values but has no impact on whether a change is detected or included in the output.
B . Maintain Integration AttributesWhile this configuration manages connector behavior and filtering rules, it does not control the detection of specific event changes.
D . Configure Integration Transaction LogThis is used for tracking and audit purposes but does not affect change detection or output inclusion.
Reference:
Workday Pro: Integrations Curriculum – Core Connector: Worker
Workday Community Article: Configuring Core Connectors and Change Detection with Edit Subscriptions GPC_PECI_DeploymentGuide_CloudPay_2.9.pdf – Section: Integration Configuration & Subscriptions

Q43. What task is needed to build a sequence generator for an EIB integration?

Put Sequence Generator Rule Configuration

Create ID Definition/Sequence Generator

Edit Tenant Setup – Integrations

Configure Integration Sequence Generator Service

Q44. Refer to the following scenario to answer the question below.
You need to configure a Core Connector: Candidate Outbound integration for your vendor. The connector requires the data initialization service (DIS).
The vendor requests additional formatting of the candidate Country field. For example, if a candidate’s country is the United States of America, the output should show USA.
What steps do you follow to meet this request?

Use an Evaluated Expression calculation and add it to the integration’s report data source.

Use the integration related action Configure Integration Population Eligibility.

Use the integration services to only output shortened country codes.

Use the integration related action Configure Integration Maps.

The scenario involves a Core Connector: Candidate Outbound integration with the Data Initialization Service (DIS), where the vendor requires the “Country” field to be formatted differently (e.g., “United States of America” to “USA”). This is a data transformation requirement, and Core Connectors provide specific tools to handle such formatting. Let’s evaluate the solution:
* Requirement:The vendor needs a shortened country code (e.g., “USA” instead of “United States of America”) in the output file. This involves transforming the delivered “Country” field value from the Candidate business object into a vendor-specific format.
* Integration Maps:In Workday Core Connectors,integration mapsare used to transform or map field values from Workday’s format to a vendor’s required format. For example, you can create a map that replaces “United States of America” with “USA,” “Canada” with “CAN,” etc. This is configured via the
“Configure Integration Maps” related action on the integration system, allowing you to define a lookup table or rule-based transformation for the Country field.
* Option Analysis:
* A. Use an Evaluated Expression calculation and add it to the integration’s report data source: Incorrect. While an Evaluate Expression calculated field could transform the value (e.g., if-then logic), Core Connectors don’t directly use report data sources for output formatting.
Calculated fields are better suited for custom reports or EIBs, not Core Connector field mapping.
* B. Use the integration related action Configure Integration Population Eligibility: Incorrect.
This action filters the population of candidates included (e.g., based on eligibility criteria), not the formatting of individual fields like Country.
* C. Use the integration services to only output shortened country codes: Incorrect. Integration services define the dataset or events triggering the integration, not field-level formatting or transformations.
* D. Use the integration related action Configure Integration Maps: Correct. Integration maps are the standard Core Connector tool for transforming field values (e.g., mapping “United States of America” to “USA”) to meet vendor requirements.
* Implementation:
* Navigate to the Core Connector: Candidate Outbound integration system.
* Use the related actionConfigure Integration Maps.
* Create a new map for the “Country” field (e.g., Source Value: “United States of America,” Target Value: “USA”).
* Apply the map to the Country field in the integration output.
* Test the output file to ensure the transformed value (e.g., “USA”) appears correctly.
References from Workday Pro Integrations Study Guide:
* Core Connectors & Document Transformation: Section on “Configuring Integration Maps” details how to transform field values for vendor-specific formatting.
* Integration System Fundamentals: Explains how Core Connectors handle data transformation through maps rather than calculated fields or services for field-level changes.

Q45. Refer to the following XML to answer the question below.

You are an integration developer and need to write XSLT to transform the output of an EIB which is making a request to the Get Job Profiles web service operation. The root template of your XSLT matches on the <wd:
Get_Job_Profiles_Response> element. This root template then applies a template against <wd:Job_Profile>.
What XPath syntax would be used to select the value of the wd:Job_Code element when the <xsl:value-of> element is placed within the template which matches on <wd:Job_Profile>?

wd:Job_Profile/wd:Job_Profile_Data/wd:Job_Code

wd:Job_Profile_Data[@wd:Job_Code]

wd:Job_Profile_Data/wd:Job_Code

wd:Job_Profile_Reference/wd:ID[@wd:type=’Job_Profile_ID’]

Q46. Refer to the following scenario to answer the question below. Your integration has the following runs in the integration events report (Date format of MM/DD/YYYY):
Run #1
* Core Connector: Worker Integration System was launched on May 15, 2024 at 3:00:00 AM
* As of Entry Moment: 05/15/2024 3:00:00 AM
* Effective Date: 05/15/2024
* Last Successful As of Entry Moment: 05/01/2024 3:00:00 AM
* Last Successful Effective Date: 05/01/2024
Run #2
* Core Connector: Worker Integration System was launched on May 31, 2024 at 3:00:00 AM
* As of Entry Moment: 05/31/2024 3:00:00 AM
* Effective Date: 05/31/2024
* Last Successful As of Entry Moment: 05/15/2024 3:00:00 AM
* Last Successful Effective Date: 05/15/2024
On May 13, 2024 Brian Hill receives a salary increase. The new salary amount is set to $90,000.00 with an effective date of May 22, 2024. Which of these runs will include Brian Hill’s compensation change?

Brian Hill will only be included in the first integration run.

Brian Hill will be included in both integration runs.

Brian Hill will only be included the second integration run.

Brian Hill will be excluded from both integration runs.

Q47. You have successfully configured an ISU and an ISSG with the correct security policies and have assigned them to an EIB.
What task do you need to run before you can launch the EIB?

Activate Pending Security Policy Changes

View Security for Securable Item

Assign the ISSG to only one security policy

Maintain Integration Security Policies

Q48. Refer to the following scenario to answer the question below.
You have been asked to build an integration using the Core Connector: Worker template and should leverage the Data Initialization Service (DIS). The integration will be used to export a full file (no change detection) for employees only and will include personal data.
What configuration is required to ensure that when outputting phone number only the home phone number is included in the output?

Configure an integration map to map the phone type.

Include the phone type integration field attribute.

Configure the phone type integration attribute.

Configure an integration field override to include phone type.

The scenario involves a Core Connector: Worker integration using DIS to export a full file of employee personal data, with the requirement to output only the home phone number when including phone data. Workday’s “Phone Number” field is multi-instance, meaning a worker can have multiple phone types (e.g., Home, Work, Mobile). Let’s determine the configuration:
Requirement:Filter the multi-instance “Phone Number” field to include only the “Home” phone number in the output file. This involves specifying which instance of the phone data to extract.
Integration Field Attributes:In Core Connectors, Integration Field Attributes allow you to refine how multi-instance fields are handled in the output. For the “Phone Number” field, you can set an attribute like “Phone Type” to “Home” to ensure only home phone numbers are included. This is a field-level configuration that filters instances without requiring a calculated field or override.
Option Analysis:
A . Configure an integration map to map the phone type: Incorrect. Integration Maps transform field values (e.g., “United States” to “USA”), not filter multi-instance data like selecting a specific phone type.
B . Include the phone type integration field attribute: Correct. This configures the “Phone Number” field to output only instances where the phone type is “Home,” directly meeting the requirement.
C . Configure the phone type integration attribute: Incorrect. “Integration attribute” refers to integration-level settings (e.g., file format), not field-specific configurations. The correct term is “integration field attribute.” D . Configure an integration field override to include phone type: Incorrect. Integration Field Overrides are used to replace a field’s value with a calculated field or custom value, not to filter multi-instance data like phone type.
Implementation:
Edit the Core Connector: Worker integration.
Navigate to the Integration Field Attributes section for the “Phone Number” field.
Set the “Phone Type” attribute to “Home” (or equivalent reference ID for Home phone).
Test the output file to confirm only home phone numbers are included.
Reference from Workday Pro Integrations Study Guide:
Core Connectors & Document Transformation: Section on “Integration Field Attributes” explains filtering multi-instance fields like phone numbers by type.
Integration System Fundamentals: Notes how Core Connectors handle multi-instance data with field-level attributes.

Pass Workday-Pro-Integrations Exam with Updated Workday-Pro-Integrations Exam Dumps PDF 2026 [Q26-Q48]

Workday Workday-Pro-Integrations Exam Syllabus Topics:

Leave a Reply Cancel reply