Workday Workday-Pro-Integrations Practice Test Questions Answers

The scenario involves a Core Connector: Worker integration using DIS to export a full file of personal data, restricted to employees only (excluding contingent workers). In Workday, the Worker business object includes both employees and contingent workers, so a filter is needed to limit the population. Let’s explore the configuration:

Requirement:Ensure the integration outputs only employees, not contingent workers. This is a population-level filter, not a field transformation or override.

Integration Population Eligibility:In Core Connectors, the Configure Integration Population Eligibility related action defines which workers are included in the integration’s dataset. You can set eligibility rules, such as "Worker Type equals Employee" (or exclude "Contingent Worker"), to filter the population before data is extracted. For a full file export (no change detection), this ensures the entire output is limited to employees.

Option Analysis:

A. Configure the Integration Population Eligibility: Correct. This filters the worker population to employees only, aligning with the requirement at the dataset level.

B. Configure a map for worker type in the Integration Maps: Incorrect. Integration Maps transform field values (e.g., "Employee" to "EMP"), not filter the population of workers included in the extract.

C. Configure worker type in the Integration Field Attributes: Incorrect. Integration Field Attributes refine how a field is output (e.g., phone type), not the overall population eligibility.

D. Configure eligibility in the Integration Field Overrides: Incorrect. Integration Field Overrides replace field values with custom data (e.g., a calculated field), not define the population of workers.

Implementation:

Edit the Core Connector: Worker integration.

Use the related action Configure Integration Population Eligibility.

Add a rule: "Worker Type equals Employee" (or exclude "Contingent Worker").

Save and test to ensure only employee data is exported.

References from Workday Pro Integrations Study Guide:

Core Connectors & Document Transformation: Section on "Configuring Integration Population Eligibility" explains filtering the worker population for outbound integrations.

Integration System Fundamentals: Discusses population scoping in Core Connectors to meet specific export criteria.

The task is to write XSLT within a template matching wd:Report_Data/wd:Report_Entry to categorize wd:Job_Skills data, outputting "HR Skills" if the value contains "HR" and "NON-HR Skills" if it does not, using a series of elements. The correct syntax must use the contains() function to check for the substring "HR" within wd:Job_Skills, as the question implies partial matching (e.g., "HR Specialist" or "Senior HR"), not exact equality.

Let’s analyze each option:

Option A:

xml

HR Skills

NON-HR Skills

Issues:

is misused here. It outputs the result of the expression (e.g., "true" or "false" for a comparison), not the conditional text. The inside won’t execute as intended.

The = operator checks for exact equality (e.g., wd:Job_Skills must be exactly "HR"), not substring presence, which contradicts the requirement to check if "HR" is contained within the value.

is malformed (self-closing without a test attribute) and misplaced.

Verdict: Incorrect syntax and logic.

Option B:

xml

HR Skills

NON-HR Skills

Issues:

Similar to A, outputs the boolean result of contains() ("true" or "false"), not the conditional text "HR Skills" or "NON-HR Skills."

The elements are inside invalid tags (self-closing, no test), rendering them ineffective.

While contains() is correct for substring checking, the structure fails to meet the requirement.

Verdict: Incorrect structure despite using contains().

Option C:

xml

HR Skills

NON-HR Skills

Analysis:

Uses correctly with test attributes, satisfying the "series of elements" requirement.

However, wd:Job_Skills='HR' tests for exact equality, not whether "HR" is contained within the value. For example, "HR Specialist" would fail this test, outputting "NON-HR Skills" incorrectly.

Verdict: Semantically incorrect due to exact matching instead of substring checking.

Option D:

xml

HR Skills

NON-HR Skills

Analysis:

Correctly uses with test attributes, aligning with the question’s requirement.

The contains() function properly checks if "HR" is a substring within wd:Job_Skills (e.g., "HR Manager" or "Senior HR" returns true).

not(contains()) ensures the opposite condition, covering all cases (mutually exclusive).

outputs the exact strings "HR Skills" or "NON-HR Skills" as required.

Note: The closing tag is a typo in the option (should be ), but in context, it’s an obvious formatting error, not a substantive issue.

Verdict: Correct logic and syntax, making D the best answer.

Correct Implementation in Context:

xml

HR Skills

NON-HR Skills

Example Input: Senior HR Analyst → Output: HR Skills

Example Input: IT Specialist → Output: NON-HR Skills

Workday Pro Integrations Study Guide: "Configure Integration System - TRANSFORMATION" section, detailing and contains() for conditional XSLT logic in Workday.

Workday Documentation: "XSLT Transformations in Workday" under EIB, confirming wd: namespace usage and string functions.

W3C XSLT 1.0 Specification: Section 9.1, "Conditional Processing with ," and Section 11.2, "String Functions" (contains()).

Workday Community: Examples of substring-based conditionals in XSLT for report transformations.

To create a connector-based integration with additional custom configurations such as dynamic file naming and internal-to-external value mapping, the following steps must be followed:

Enable Needed Integration Services:

This step involves activating the required integration services to ensure that the necessary API calls, security, and processing capabilities are available within Workday.

Configure Integration Field Attributes:

Integration Field Attributes allow customization of fields within the integration, enabling changes to formats, mappings, and transformations, such as including a dynamically generated file name with the current date and integration run number.

Configure Integration Maps:

Integration Maps are used to transform internal values into external values as per the vendor’s requirements. This ensures that data fields in Workday align correctly with external system specifications.

Configure Sequence Generator:

The Sequence Generator is used to append unique identifiers to output files, ensuring each integration run produces a uniquely named file (e.g., including the current date and run number).

This workflow ensures that the integration is set up efficiently while meeting the vendor’s additional configuration needs.

When creating a Date Difference calculated field in Workday, both dates must exist on the same business object. If they are on different business objects, you need to first bring the second date onto the primary object. To do that, you use a:

Lookup Related Value calculated field — this allows you to retrieve a field (like a date) from a related business object, so it can then be used in further calculations.

Example scenario:

You want to subtract Hire Date (on the Worker object) from Dependent’s Birth Date (on the Dependent object).

These are on different objects → use Lookup Related Value to pull the second date into the current object context.

Then, create the Date Difference using both dates on the same object.

Why other options are incorrect:

B. Build Date creates a synthetic date, not for bridging objects.

C. Lookup Date Rollup rolls up values across multiple related objects, not typically used for 1-to-1 value bridging.

D. Lookup Value as of Date is used for time-sensitive lookups (e.g., point-in-time values), not structural bridging.

When creating an outbound connector using the Workday Core Connector: Organization Outbound template, you need to configure the connector to meet specific vendor requirements, such as formatting output data and adjusting document retention policies. Let's break down the question and analyze the requirements and options based on Workday's integration framework, specifically focusing on the Core Connector and its configuration tasks.

Understanding the Requirements

Output Data Formatting:The vendor has provided a table specifying how organization types should appear in the output file (e.g., Cost Center as "CC", Pay Group as "PAY", Supervisory as "S", and any other value as "OTHER"). This indicates a need to transform or map Workday organization data into specific output values, which is typically handled by configuring how fields are processed or mapped in the integration.

Document Retention Policy Change:The vendor wants to change the default document retention policy from 30 days to 7 days. In Workday, document retention policies for integrations (e.g., files stored on SFTP or other delivery methods) are managed through integration settings, specifically attributes related to file retention or delivery options.

Analyzing Workday Core Connector: Organization Outbound

The Core Connector: Organization Outbound template is a pre-built Workday integration template used to extract organization-related data (e.g., cost centers, pay groups, supervisory organizations) and send it to an external system. It leverages Workday's integration framework, including integration maps, field overrides, and attributes, to customize data output and behavior.

Integration Maps: Used to define how data is transformed or mapped from Workday to the output format, often involving XSLT or predefined mappings.

Integration Field Overrides: Allow you to override or customize how specific fields are displayed or formatted in the output, such as mapping "Cost Center" to "CC" as per the vendor's table.

Integration Attributes: Control broader integration settings, such as delivery methods, file formats, and retention policies (e.g., document retention duration).

Integration Field Attributes: Typically focus on specific field-level properties but are less commonly used for retention policies or broad mappings compared to the above options.

Evaluating the Vendor's Output Requirements

The table provided (Cost Center → "CC", Pay Group → "PAY", Supervisory → "S", any other value → "OTHER") suggests a need to transform or override the default output values for organization types. This is a field-level customization, best handled by Integration Field Overrides, which allow you to specify custom values or formats for specific fields in the output.

For example, in the Core Connector, you can use Integration Field Overrides to map the Workday organization type (e.g., "Cost_Center") to the vendor's desired output ("CC"). This is a common practice for outbound integrations where external systems require specific formatting.

Evaluating the Retention Policy Change

The default document retention policy of 30 days needs to be changed to 7 days. In Workday, retention policies for integration output files (e.g., files delivered via SFTP or email) are configured as part of the integration's attributes, not field-level settings.

Integration Attributes are used to manage integration-wide settings, including delivery options, file retention periods, and other global configurations. You can specify the retention period (e.g., 7 days) in the attributes section of the Core Connector configuration.

This is distinct from field-level overrides or maps, as retention is not tied to individual data fields but to the integration's output management.

Analyzing the Options

Now, let's evaluate each option to determine which tasks are needed to meet both requirements:

A. Configure Integration Maps and Configure Integration Attributes

Integration Maps: These are used for broader data transformations or mappings, such as converting Workday XML to another format or defining complex data relationships. While they could theoretically handle the output value mappings (e.g., Cost Center → "CC"), they are typically more complex and less granular than field overrides for simple value changes.

Integration Attributes: Correct for configuring the retention policy (e.g., changing from 30 to 7 days), as attributes manage integration-wide settings like retention.

Why Not Sufficient?: Integration Maps are overkill for simple field value overrides like the vendor's table, and field-level customization is better handled by Integration Field Overrides for precision and ease.

B. Configure Integration Field Overrides and Configure Integration Field Attributes

Integration Field Overrides: Correct for mapping specific field values (e.g., Cost Center → "CC"), as they allow granular control over output formats for individual fields.

Integration Field Attributes: These are less commonly used and typically focus on field-specific properties (e.g., data type, length), not broad integration settings like retention policies. Retention is not managed at the field level, so this is incorrect for the retention requirement.

Why Not Sufficient?: Integration Field Attributes do not handle retention policies, making this option incomplete.

C. Configure Integration Field Overrides and Configure Integration Attributes

Integration Field Overrides: Perfect for mapping the vendor's output values (e.g., Cost Center → "CC", Pay Group → "PAY", etc.), as they allow precise control over field-level output formatting.

Integration Attributes: Correct for configuring the retention policy (e.g., changing from 30 to 7 days), as attributes manage integration-wide settings like file retention.

Why Sufficient?: This combination addresses both requirements—field-level output formatting and integration-wide retention policy changes—making it the most accurate choice.

D. Configure Integration Maps and Configure Integration Field Attributes

Integration Maps: As explained, these are better for complex transformations, not simple field value overrides like the vendor's table. They could work but are less efficient than field overrides.

Integration Field Attributes: As noted, these do not handle retention policies or broad integration settings, making them incorrect for the retention requirement.

Why Not Sufficient?: This combination fails to address retention effectively and uses Integration Maps when Integration Field Overrides would be more appropriate for the output formatting.

Conclusion

Based on the analysis, the vendor's requirements for output formatting (mapping organization types to specific values) and changing the retention policy (from 30 to 7 days) are best met by:

Integration Field Overrides: To customize the output values for organization types (e.g., Cost Center → "CC") as shown in the table.

Integration Attributes: To adjust the document retention policy from 30 days to 7 days.