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 output the value of a calculated field which you created for inclusion in this integration?
Correct Answer: B
The scenario involves a Core Connector: Worker integration using the Data Initialization Service (DIS) to export a full file of employee personal data, with a requirement to include a calculated field in the output. Core Connectors rely on predefined field mappings, but custom calculated fields need specific configuration to be included. Let's analyze the solution: * Requirement:Output the value of a calculated field created for this integration. In Workday, calculated fields are custom-built (e.g., using Report Writer or Calculated Fields) and not part of the standard Core Connector template, so they must be explicitly added to the output. * Integration Field Overrides:In Core Connectors,Integration Field Overridesallow you to replace a delivered field's value or add a new field to the output by mapping it to a calculated field. This is the standard method to include custom calculated fields in the integration file. You create the calculated field separately,then use overrides to specify where its value appears in the output structure (e.g., as a new column or replacing an existing field). * Option Analysis: * A. Configure Integration Field Attributes: Incorrect. Integration Field Attributes refine how delivered fields are output (e.g., filtering multi-instance data like phone type), but they don't support adding or mapping calculated fields. * B. Configure Integration Field Overrides: Correct. This configuration maps the calculated field to the output, ensuring its value is included in the exported file. * C. Configure Integration Attributes: Incorrect. Integration Attributes define integration-level settings (e.g., file name, delivery protocol), not field-specific outputs like calculated fields. * D. Configure Integration Maps: Incorrect. Integration Maps transform existing field values (e. g., "Married" to "M"), but they don't add new fields or directly output calculated fields. * Implementation: * Create the calculated field in Workday (e.g., via Create Calculated Field task). * Edit the Core Connector: Worker integration. * Navigate to theIntegration Field Overridessection. * Add a new override, selecting the calculated field and specifying its output position (e.g., a new field ID or overriding an existing one). * Test the integration to confirm the calculated field value appears in the output file. References from Workday Pro Integrations Study Guide: * Core Connectors & Document Transformation: Section on "Configuring Integration Field Overrides" explains how to include calculated fields in Core Connector outputs. * Integration System Fundamentals: Notes the use of overrides for custom data in predefined integration templates.
Question 42
Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled to extract worker demographic and contact information. The integration must include worker fields such as name, address, and a calculated field identifying workers eligible for a phone allowance. The Phone Allowance Type calculated field exists and is functional in the tenant, but it is not displaying in the output. What configuration step should you complete to include this field in the output?
Correct Answer: D
In this scenario, a calculated field (Phone Allowance Type) is available and validated in the tenant, but it does not appear in the Core Connector: Worker output. The integration is configured with DIS enabled, and the expected behavior is for all specified worker data - including name, address, and calculated fields - to be included in the output file. The correct action is to enable the field from the Configure Integration Field Attributes step. From Workday Pro: Integrations materials: "In order for a calculated field to be included in a Core Connector output, it must be explicitly located and selected from within the Configure Integration Field Attributes task. This step determines what fields are extracted in the integration output - including any standard or calculated fields available in the object model." Even though the field exists and is functional, it must be manually located within the relevant section (e.g., Worker Data > Compensation or Worker Details), and marked to include in the output. Incorrect Options Explained: A . Configure Integration Field Overrides: This is used to change or override output formatting but does not control field visibility. B . Configure Integration Maps: Used for mapping values or converting code sets, not for selecting fields for output. C . Create a Custom Field Override service: This is not necessary for simply adding a calculated field; the existing field can be enabled via attributes configuration. Reference: Workday Pro: Core Connector - Field Selection Using Configure Integration Field Attributes Workday Community: How to Include Calculated Fields in Connector Outputs
Question 43
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 currentlyhave 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?
Correct Answer: C
In Workday integrations, XSLT is used to transform XML data, such as the output from an Enterprise Interface Builder (EIB) or a web service-enabled report, into a desired format for third-party systems. In this scenario, you need to write XSLT to process wd:Dependents_Group elements and output a relationship code based on the value of the wd:Relationship attribute or element. The requirement is tooutput "SP" for a "Spouse" relationship, "CH" for a "Child" relationship, and "OTHER" for any other relationship, using an <xsl:choose> statement within a template matching wd:Dependents_Group. Here's why option C is correct: * XSLT <xsl:choose> Structure: The <xsl:choose> element in XSLT provides conditional logic similar to a switch statement. It evaluates conditions in <xsl:when> elements sequentially, executing the first matching condition, and uses <xsl:otherwise> for any case that doesn't match. * Relationship as an Attribute: Based on the provided XML snippet, wd:Relationship is an attribute (e. g., <wd:Relationship>Spouse</wd:Relationship> within wd:Dependents_Group). However, in Workday XML for integrations, wd:Relationship is often represented as an attribute (@wd: Relationship) rather than a child element, especially in contexts like dependent data in reports. The syntax @wd:Relationship in the test attribute of <xsl:when> correctly references this attribute, aligning with Workday's typical XML structure for such data. * Condition Matching: * The first <xsl:when test="@wd:Relationship='Spouse'">SP</xsl:when> checks if the wd: Relationship attribute equals "Spouse" and outputs "SP" if true. * The second <xsl:when test="@wd:Relationship='Child'">CH</xsl:when> checks if the wd: Relationship attribute equals "Child" and outputs "CH" if true. * The <xsl:otherwise>OTHER</xsl:otherwise> handles all other cases, outputting "OTHER" if the relationship is neither "Spouse" nor "Child." * Context in Template: Since the template matches on wd:Dependents_Group, the test conditions operate on the current wd:Dependents_Group element and its attributes, ensuring the correct relationship code is output for each dependent. The XML snippet shows wd:Relationship as an element, but Workday documentation and integration practices often standardize it as an attribute in XSLT transformations, making @wd:Relationship appropriate. Why not the other options? * A. xml WrapCopy <xsl:choose> <xsl:when test="wd:Relationship='Spouse'">SP</xsl:when> <xsl:when test="wd:Relationship='Child'">CH</xsl:when> <xsl:otherwise>OTHER</xsl:otherwise> </xsl:choose> This assumes wd:Relationship is a child element of wd:Dependents_Group, not an attribute. The XML snippet shows wd:Relationship as an element, but in Workday integrations, XSLT often expects attributes for efficiency and consistency, especially in report outputs. Using wd:Relationship without @ would not match the attribute-based structure commonly used, making it incorrect for this context. * B. xml WrapCopy <xsl:choose> <xsl:when test="@wd:Relationship='Spouse'">SP</xsl:when> <xsl:when test="@wd:Relationship='Child'">CH</xsl:when> <xsl:otherwise>OTHER</xsl:otherwise> </xsl:choose> This correctly uses @wd:Relationship for an attribute but has a logical flaw: if wd:Relationship='Child', the second <xsl:when> would output "CH," but the order of conditions matters. However, the primaryissue is that it doesn't match the exact structure or intent as clearly as option C, and Workday documentation often specifies exact attribute-based conditions like those in option C. * D. xml WrapCopy <xsl:choose> <xsl:when test="/wd:Relationship='Spouse'">SP</xsl:when> <xsl:when test="/wd:Relationship='Child'">CH</xsl:when> <xsl:otherwise>OTHER</xsl:otherwise> </xsl:choose> This uses an absolute path (/wd:Relationship), which searches for a wd:Relationship element at the root of the XML document, not within the current wd:Dependents_Group context. This would not work correctly for processing dependents in the context of the template matching wd:Dependents_Group, making it incorrect. To implement this in XSLT: * Within your template matching wd:Dependents_Group, you would include the <xsl:choose> statement from option C to evaluate the wd:Relationship attribute and output the appropriate relationship code ("SP," "CH," or "OTHER") based on its value. This ensures the transformation aligns with Workday's XML structure and integration requirements for processing dependent data in an EIB or web service- enabled report, even though the provided XML shows wd:Relationship as an element-XSLT transformations often normalize to attributes for consistency. References: * Workday Pro Integrations Study Guide: Section on "XSLT Transformations for Workday Integrations" - Details the use of <xsl:choose>, <xsl:when>, <xsl:otherwise>, and XPath for conditional logic in XSLT, including handling attributes like @wd:Relationship. * Workday EIB and Web Services Guide: Chapter on "XML and XSLT for Report Data" - Explains the structure of Workday XML (e.g., wd:Dependents_Group, @wd:Relationship) and how to use XSLT to transform dependent data, including attribute-based conditions. * Workday Reporting and Analytics Guide: Section on "Web Service-Enabled Reports" - Covers integrating report outputs with XSLT for transformations, including examples of conditional logic for relationship codes.
Question 44
A vendor needs an EIB that uses a custom report to output a list of new hires and their child dependent(s). You have been asked to create a calculated field that will be used to add only child dependent(s). Which calculated field functions do you need to accomplish this?
Correct Answer: D
In this case, you're asked to create a calculated field that: * Filters dependent records * Includes only child relationships This means: * The worker has multiple dependents (a multi-instance field). * You need to extract only those dependent(s) where the relationship is "Child". To achieve this in Workday, use: * True/False Condition # check if the relationship descriptor = "Child" * Extract Multi-Instance # filters the multi-instance field (Dependents) using the above condition to return only matching records This two-step logic filters multi-instance relationships correctly. Why the other options are incorrect: * A and B are missing Extract Multi-Instance, which is required to filter multi-values. * C includes Text Constant unnecessarily - only True/False Condition and Extract Multi-Instance are required. Reference:Workday Pro: Calculated Fields - Filtering Multi-Instance Fields (Dependents, Emergency Contacts)Workday Community: Best Practice for Extracting Specific Relationships in EIB Reports
Question 45
You need to filter a custom report to only show workers that have been terminated after a user-prompted date. How do you combine conditions in the filter to meet this requirement?
Correct Answer: D
The requirement is to filter a custom report to show only workers terminated after a user-prompted date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions can be combined using AND/OR logic to refine the dataset. Let's analyze the requirement and options: Key Conditions: Workers must be terminated, so the "Worker Status" field must equal "Terminated." The termination must occur after a user-specified date, so the "Termination Date" must be greater than the prompted value. Both conditions must be true for a worker to appear in the report, requiring an AND combination. Option Analysis: A . Worker Status is equal to the value "Terminated" OR Termination Date is greater than a value retrieved from a prompt: Incorrect. Using OR means the report would include workers who are terminated (regardless of date) OR workers with a termination date after the prompt (even if not terminated), which doesn't meet the strict requirement of terminated workers after a specific date. B . Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a value retrieved from a prompt: Incorrect. Worker Status shouldn't be a prompted value (it's fixed as "Terminated"), and "less than" would show terminations before the date, not after. C . Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a value retrieved from a prompt: Incorrect. Worker Status shouldn't be prompted, and "equal to" limits the filter to exact matches, not "after" the date. OR logic also broadens the scope incorrectly. D . Worker Status is equal to the value "Terminated" AND Termination Date is greater than a value retrieved from a prompt: Correct. This ensures workers are terminated (fixed value) AND their termination date is after the user-entered date, precisely meeting the requirement. Implementation: In the custom report's Filter tab, add two conditions: Field: Worker Status, Operator: equals, Value: "Terminated". Field: Termination Date, Operator: greater than, Value: Prompt for Date (configured as a report prompt). Set the logical operator between conditions to AND. Test with a sample date to verify only terminated workers after that date appear. Reference from Workday Pro Integrations Study Guide: Workday Report Writer Fundamentals: Section on "Creating and Managing Filters" details combining conditions with AND/OR logic and using prompts. Integration System Fundamentals: Notes how filtered reports support integration data sources with dynamic user inputs.
