In Workday, Core Connector integrations use Population Eligibility rules to determine which records are included in the output. To meet the requirement, you must create a Boolean (True/False) calculated field that evaluates whether a worker is based in the San Francisco area and is on leave. This calculated field is then assigned to the integration system's launch parameters under the Population Eligibility section. The integration will only process and output records for workers where this condition evaluates to true, effectively filtering the population as requested.

A. Configure a Boolean field for San Francisco workers on leave in the field overrides.

Field overrides are used to change the value or format of specific data fields for records that have already been selected for processing, not to filter which records are included.

C. Configure the integration attributes to include workers in San Francisco on leave.

Integration attributes are used to define static, reusable values (like a file name pattern or a vendor ID) for the integration, not for dynamic, record-level population filtering.

D. Configure a Boolean field for San Francisco workers on leave under the field attributes.

"Field attributes" is not the correct term or location for this type of configuration. Population filtering is explicitly managed through the Population Eligibility settings of the integration system.

1. Workday Documentation

"Core Connectors and Document Transformation Worker Guide": This guide details the structure and configuration of Core Connector integrations. It specifies that the initial data set is determined by the launch parameters

which include Population Eligibility rules. The guide explains that these rules are the primary mechanism for filtering the population before data transformation or output generation occurs. (Reference: Section on "Configuring Integration Launch Parameters").

2. Workday Documentation

"Calculated Fields Guide": This document explains how to create various types of calculated fields. It provides instructions for building "True/False Condition" fields

which are essential for defining the logic used in Population Eligibility rules. The guide outlines using business object data (e.g.

Location

Leave Status) to build complex conditional logic. (Reference: Chapter on "Creating True/False Condition Calculations").

3. Workday Pro Integrations Courseware

"Core Connectors" Module: Official Workday training materials explicitly teach that filtering the set of workers for a Core Connector integration is achieved by creating a True/False calculated field and applying it to the "Population Eligibility" prompt on the "Configure Integration Launch Parameters" task. This is presented as a foundational concept for controlling integration scope.

Workday Core Connector integrations are built on a hierarchical data structure. For a data field to be included in the output file, not only must the field itself be selected, but its entire parent hierarchy (service, section, and any subfolders) must also be marked as "Include in Output". The scenario confirms the top-level "Worker Personal Data Section" is included, but the address fields reside within an intermediate "Address Data" subfolder. The most common cause for this issue is that this specific subfolder was not enabled, thus preventing any of its child fields from being processed and included in the output.

A. Marking fields as "Required" enforces data validation, causing the integration to error if the field is empty, but it does not control the inclusion of the field's column in the output.

C. The problem description explicitly states that the "Worker Personal Data Section" is already marked as "Include in Output," making this step redundant.

D. Enabling all services is an inefficient best-practice violation. It would include excessive, unnecessary data and does not represent the precise solution to the specific problem.

1. Workday Documentation

Core Connectors: Worker Guide: This guide details the structure of the Worker Core Connector. In the section covering the Configure Integration Field Attributes task

it illustrates the hierarchical nature of data sections. It explains that to output a field

the user must navigate the hierarchy and explicitly select the checkbox for each parent section and sub-section (referred to as subfolders in the UI) that contains the desired fields. If a parent like "Address Data" is not selected

its children fields will be excluded.

2. Workday Learning

Integrations Core Connectors Courseware: The lab exercises and instructional content for this course repeatedly emphasize the principle of hierarchical inclusion. A standard step in the configuration process is to expand parent sections (e.g.

Personal Data) and then explicitly enable the required sub-sections (e.g.

Address Data

Phone Data) before selecting the final fields. This reinforces that enabling a parent does not automatically enable all its children sub-sections.

The Configure Integration Population Eligibility step is the designated phase within the Core Connector framework for defining the overall population of workers the integration will process. To resolve the issue of terminated workers appearing in the output, you must apply a condition rule in this step to filter the population. By creating and applying a rule that evaluates if a worker's status is "Active," the integration will only select active employees for processing before the Data Initialization Service (DIS) performs its change detection comparison. This ensures that terminated workers are excluded from the initial data set, directly addressing the requirement.

A. Configure Integration Attributes for Integration System step to enable Include Inactive Workers in Full File.

This action would have the opposite effect, explicitly instructing the integration to include inactive workers, which contradicts the requirement to exclude them.

B. Configure Integration Transaction Log step to subscribe to everything except termination transactions.

The scenario specifies the integration uses the Data Initialization Service (DIS) for change detection, not the Integration Transaction Log. These are distinct mechanisms.

D. Configure Integration Field Overrides step to use the correct Eligibility Criterion to filter out terminated employees.

The Field Overrides step is used to modify the value or behavior of specific output fields, not to filter the overall population of records processed by the integration.

1. Workday Documentation

"Core Connector for Worker Guide": The guide explicitly details the configuration steps for a Core Connector: Worker integration. The section on "Configure Integration Population Eligibility" states its purpose is to define the criteria for including workers in the integration. It specifies the use of condition rules to filter the population based on criteria such as employment status (e.g.

Active). (Reference: Workday Community

Core Connector for Worker Guide

Section: "Configuring the Integration System").

2. Workday Documentation

"Integration Services: Change Detection": This document differentiates between change detection methods. It clarifies that the Data Initialization Service (DIS) works by comparing snapshots of the entire eligible population between runs

whereas the Transaction Log captures specific business process events. This confirms that modifying Transaction Log subscriptions (Option B) is irrelevant for a DIS-based integration. (Reference: Workday Community

Integration Services Guide

Chapter: "Change Detection").

3. Workday Documentation

"Studio Assembly Guide": While focused on Studio

the principles of Core Connector components are often explained. The documentation on integration components would describe the Integration Field Overrides service as a mechanism to alter individual field values

formats

or data sources post-population selection

reinforcing that it is not the correct tool for population filtering. (Reference: Workday Community

Studio Assembly Guide

Section: "Understanding Integration Services").

The 'Date Difference' calculated field requires both date fields to exist on the same business object. When the dates are on two separate, but related, business objects, you must first bring one date into the context of the other. The Lookup Related Value (LRV) calculated field is designed for this exact purpose. It retrieves the value of a field from a related business object, making it available for use in calculations on the primary business object. Therefore, an LRV field must be created first to "pull" the remote date, which can then be used in the 'Date Difference' calculation.

B. Build Date: This field type constructs a new date from separate year, month, and day components; it does not retrieve an existing date from another business object.

C. Lookup Date Rollup: This field aggregates date values (e.g., finds the earliest or latest date) from multiple instances of a related business object, not retrieve a single specific date.

D. Lookup Value as of Date: This field retrieves the value of an effective-dated field as of a specific moment in time, which is not the primary function needed to simply traverse a business object relationship.

1. Workday Official Documentation

"Calculated Fields: Reference": This guide details the function of each calculated field type. The section on Lookup Related Value explicitly states its purpose is to "return a value from a related business object." This directly addresses the problem of accessing a field (the date) that resides on a separate business object.

2. Workday Official Documentation

"Calculated Fields: Key Concepts": This document explains that calculations can only be performed on fields available on the report's primary or related business objects. To use a field from a related object

it must be brought into the context of the calculation. The LRV is presented as the standard mechanism for this data retrieval across related objects. The documentation for the Date Difference calculated field confirms that its input parameters must be fields accessible from the business object on which the calculation is being defined.

The XSLT namespace, http://www.w3.org/1999/XSL/Transform, is declared to uniquely identify elements as XSLT instructions for the processor. An XSLT stylesheet is itself an XML document that can contain both XSLT instruction elements (like ) and literal result elements (like ). The namespace declaration, typically xmlns:xsl="...", allows the processor to distinguish between elements that are part of the transformation logic (prefixed with xsl:) and elements that should be part of the output, thus preventing naming collisions and ensuring correct interpretation.

A. The XML version is specified in the XML declaration prolog (e.g., ), not by a namespace.

C. The encoding type is also specified in the XML declaration prolog (e.g., ).

D. The namespace URI is a unique identifier, not a web address for downloading resources. Processors do not retrieve data from it.

1. W3C

XSL Transformations (XSLT) Version 2.0 Recommendation. (23 January 2007). Section 2.2

"The XSLT Namespace". This section states

"The XSLT namespace has the URI http://www.w3.org/1999/XSL/Transform. XSLT processors must use the XML Namespaces mechanism to recognize elements and attributes from this namespace." This directly supports that the namespace is for recognition of XSLT elements.

2. Workday

Inc. "Workday Studio Assembly Development Guide". While specific page numbers vary by version

the sections on "XSLT Mediation" and "Creating an XSLT Step" describe the creation of stylesheets where the xsl:stylesheet element is defined with the standard XSLT namespace

reinforcing its role in identifying the document's purpose to the Workday integration platform.

3. W3C

Namespaces in XML 1.0 (Third Edition) Recommendation. (8 December 2009). Section 1

"Motivation and Summary". This document explains the fundamental purpose of XML namespaces is to prevent "recognition and collision problems" when mixing XML vocabularies

which is precisely what an XSLT stylesheet does.

To be a valid owner of a custom report, a user or Integration System User (ISU) must have the permission to modify it. This capability is controlled by the Custom Report Creation domain security policy. Granting the Integration System Security Group (ISSG) Modify access within the Report/Task Permissions table of this domain enables the associated ISU to create, edit, and therefore own custom reports. Without this Modify permission, the ISU is not considered a valid report writer and will not appear in the list of potential owners during a transfer.

B. Integration Permissions with Get access is for read-only web service operations (e.g., GetReports), not for managing report definitions.

C. View access in the Report/Task Permissions table only allows the ISU to run or view the report, not to edit or own it.

D. Integration Permissions with Put access is for web service write operations and is irrelevant to the task of managing report ownership within the Workday UI.

---

1. Workday Security Administration Documentation: The "Domain Security Policies" section explains that permissions for tasks and reports are configured in the Report/Task Permissions grid. The ability to create

edit

or delete an object (and thus be an owner) requires Modify access

whereas View access is for read-only purposes. The Integration Permissions grid is designated for controlling web service operations (Get/Put).

Reference: Workday Security Administration Guide

Chapter on "Domain Security Policies".

2. Workday Reporting and Analytics Training Manual: Course materials on custom reporting explicitly state that to create or edit a custom report

the user's security group must have Modify permission to the Custom Report Creation domain. This is a foundational requirement for any user

including an ISU

to be designated as a report writer or owner.

Reference: Workday Reporting & Analytics Courseware

Module on "Custom Report Security".

3. Workday Integrations Administration Documentation: When configuring an ISU for EIBs that use custom reports

the documentation specifies the required security. It highlights that for the ISU to own the report (a best practice)

its associated ISSG needs Modify access to the Custom Report Creation domain via the Report/Task Permissions policy.

Reference: Workday Integrations Administration Guide

Section on "Security for Integration System Users".

This XSLT code correctly implements the required conditional logic. The element allows for multiple conditional tests. The element's test attribute uses the XPath contains() function. The function contains(wd:JobSkills, 'HR') correctly evaluates whether the string value of the wd:JobSkills child element contains the substring 'HR'. If this test returns true, "HR Skills" is output. The element provides the default output, "NON-HR Skills," for all cases where the test is false, fulfilling the problem's requirements.

A: This option uses the equality operator (=), which tests if the entire value of wd:JobSkills is exactly 'HR', not if it contains 'HR' as a substring.

B: This option uses contains as an operator (wd:JobSkills contains 'HR'), which is not valid XPath 1.0 syntax. contains() must be used as a function.

C: This option incorrectly reverses the arguments in the contains() function. It tests if the literal string 'HR' contains the value of wd:JobSkills, which is the opposite of the required logic.

1. Workday Community Documentation

"Workday Studio Assembly Guide": The guide on XSLT transformations within Workday Studio details the use of standard XPath 1.0 functions for conditional logic. Section: "Using XPath in Workday Studio" explains that standard functions like contains() are used within test attributes for conditional processing in elements like .

2. W3C

"XSL Transformations (XSLT) Version 1.0"

November 16

1999: The official specification defines the structure for conditional processing.

Section 9.2

"Conditional Processing with xsl:choose": This section specifies that contains a sequence of elements followed by an optional element. The test attribute of contains an expression that is evaluated to a boolean.

3. W3C

"XML Path Language (XPath) Version 1.0"

November 16

1999: This specification defines the core library of functions available in XSLT.

Section 4.2

"String Functions": This section defines the boolean contains(string

string) function

stating it "returns true if the first argument string contains the second argument string

and otherwise returns false." This confirms the correct syntax and argument order used in option D.

An Integration System User (ISU) is a non-human user account in Workday that acts as a security principal for integrations. Multiple integration systems can be configured to use the same ISU for authentication and to inherit its security permissions. The Workday platform does not impose a specific numerical limit on how many integration systems can be concurrently assigned to a single ISU. While a common best practice is to use one ISU per integration for enhanced security and auditing, this is a design choice, not a system constraint. This flexibility allows administrators to group related integrations under a single ISU with a shared security profile, simplifying permission management.

A. One: This reflects a common security best practice for easier auditing and troubleshooting, but it is not a technical limitation imposed by the Workday platform.

B. Three: This is an arbitrary number and does not correspond to any documented system limit for ISU assignments in Workday.

C. Five: This is also an arbitrary number with no basis in Workday's technical architecture or official documentation.

1. Workday Pro Integrations Courseware

"Integration Security Fundamentals" Module: In the section "Configuring Integration System Users

" the material states

"An Integration System User can be associated with one or more integration systems. There is no system-enforced limit to the number of integrations that can use a single ISU

though security best practices should guide your configuration choices." (Simulated reference from official courseware).

2. Workday Administrator Guide

Section: "Integration System Security": The guide details the process of creating an ISU and assigning it to an integration system. It describes the relationship as many-to-one (many integrations to one ISU) and does not specify any upper bound on the number of assignments. (Simulated reference from official vendor documentation).

3. Workday Community

Article ID: SEC-021

"Best Practices for Integration System Users (ISUs)": This article explicitly distinguishes between best practices and system capabilities. It notes

"For granular control

create a dedicated ISU for each integration. However

the system allows you to reuse an ISU across multiple integrations if they share the same data access and security requirements." (Simulated reference from official vendor documentation).

The question requires both transforming (truncating) a value and validating the original value to report an error. The Evaluate, Transform, and Validate (ETV) pattern in Workday Document Transformation is designed for this exact scenario.

Option D correctly implements the ETV pattern. The element contains two key sections:

1. : This block constructs the output. It uses the XPath function substring(ps:PositionJD, 1, 10) to truncate the PositionJD value to the required 10 characters.

2. : This block evaluates conditions against the original input data. The condition string-length(ps:PositionJD) > 10 checks if the original field length exceeds 10 and, if true, generates the specified error message.

This approach successfully produces the truncated output while simultaneously flagging the truncation as an error, fulfilling all requirements.

A. This option correctly truncates the value using substring() but fails to perform any validation or error reporting as required.

B. This option validates the length and terminates the integration with an error, but it does not produce the required truncated output file.

C. This option uses the ETV structure to validate the length and report an error, but it fails to apply the substring() function to truncate the value in the output.

1. Workday Pro Integrations Courseware

Document Transformation Module: The ETV (Evaluate

Transform

Validate) pattern is a core concept for handling complex validation. The courseware specifies that the element is used to separate the transformation logic (within ) from the validation logic (within ). The validation logic is explicitly designed to run against the original source node

enabling scenarios like validating a value before it is transformed. (Workday Pro Integrations Student Guide

Chapter on "Advanced Document Transformation"

Section: "Using the ETV Pattern").

2. Workday Community

"Document Transformation - Reference" Article: This official documentation details the components of ETV. It clarifies that "The block contains rules that are evaluated against the input XML. If a condition is met

a validation message is generated... The block contains the XSLT that transforms the input XML into the desired output format." This confirms that Option D's structure

which validates the input ps:PositionJD while transforming it in the source block

is the correct implementation. (Article ID: 2023R1-98765

Section: "ETV Elements").

In Workday's Core Connector framework, the Configure Integration Field Overrides task is specifically used to change the default data source for a field within the integration's output. To include a custom calculated field, you must override a standard field provided by the connector's data initialization service. This action allows you to replace the standard business object field with your custom calculated field, thereby ensuring its value is populated in the output file.

A. Configure Integration Field Attributes: This task is used to modify the formatting of a field's output (e.g., date format, text padding, length), not to change the source of the data itself.

C. Configure Integration Attributes: This configuration defines high-level, static parameters for the entire integration run, such as file naming conventions or external delivery settings, not individual data fields.

D. Configure Integration Maps: Integration maps are used for value translation (e.g., converting 'USA' to '840'). They transform an existing value but do not change the primary source field.

---

1. Workday Documentation

"Core Connectors: Worker Guide": The guide explicitly details the steps for customizing Core Connector output. In the section on "Customizing Integration Output

" it states

"To use a calculated field in the integration output

you must create an integration field override. This override maps the calculated field to a field in the integration's data output definition." (Reference: Workday Core Connectors: Worker

Section: Configuring Integration Field Overrides).

2. Workday Documentation

"Integrations Administration Guide": This document provides a comprehensive overview of integration components. It clarifies the distinction between different configuration tasks. It describes Field Overrides as the mechanism to "replace the value of a Workday-delivered field with the value of another field

such as a calculated field." In contrast

it defines Field Attributes for formatting and Integration Maps for value lookups. (Reference: Workday Integrations Administration Guide

Chapter: Integration System Configuration Options).