Workday Pro Integrations Certification Workday-Pro-Integrations Exam Questions

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.

Answer : B

Each task maps to a different Core Connector configuration feature. Including the private address is controlled by an integration attribute because it changes what delivered connector data sections or address types are included in the output. Translating Workday's Location Status values into vendor-specific codes is a value-mapping requirement, so Integration Maps are the correct tool. Adding the Building Manager calculated field requires an Integration Field Override because the value is custom-built and must be inserted into the connector output. Option B is the only option that matches all three configuration purposes. Field overrides are not used for standard code translation, and integration maps do not add calculated fields to the output structure.

================

Answer : A

An outbound EIB is organized around three main configuration components: Get Data, Transform, and Deliver. The Get Data section uses one data source, commonly a custom report or another supported source. The Transform section applies one transformation, such as an XSLT transformation, when formatting is required. The Deliver section sends the output to one delivery endpoint, such as SFTP, email, or another supported transport. Multiple data sources or multiple delivery endpoints are not the standard three-part model for a basic outbound EIB. A web service call and sequence generator may be used in some integration scenarios, but they are not the three primary EIB components. Therefore, option A matches the EIB architecture.

================

Answer : D

Let's break this down:

Effective Date of salary change: May 10, 2024

Entry Moment (data entry timestamp): May 13, 2024, 2:00 PM

Integration Run As of Entry Moment: May 11, 2024, 2:00 PM

Salary data was entered AFTER this moment (May 13 vs May 11)

So based on Workday's Change Detection logic:

A worker is included in the integration output only if the transaction was entered into Workday after the last successful entry moment, and the effective date is on or after the ''Last Successful Effective Date''.

In this case:

Entry was made after the last As-of Entry Moment (May 13 > May 11)

Effective date (May 10) is after the last successful effective date (May 9)

Both conditions are met, so Brian Hill will be included, and the new salary of $90,000.00 will be reflected in the output.

Why other options are incorrect:

A . The effective date is valid.

B . $60,000 would be outdated.

C . Entry moment is after the As-of date, so not excluded.

Answer : A

The requirement combines CSV output formatting with a required-value check for date fields. For Workday transformation formatting classes, XTT is the correct attribute family. xtt:class defines reusable transformation formatting rules, xtt:name names the class, and xtt:dateFormat controls the rendered date pattern. The required US format is MM/dd/yyyy, and the EU format is dd.MM.yyyy. xtt:required='true' ensures the Entry Date has a value when the output is produced. ETV attributes are used for validation rules rather than transformation formatting classes in this context. The bracketed date tokens in options C and D do not match the required dateFormat style shown for these XTT classes. Therefore, option A is the correct configuration.

Answer : A

In Workday integrations, Document Transformation (DT) using XSLT with Workday Transformation Toolkit (XTT) attributes is used to transform XML data, such as the output from a Core Connector or EIB, into a specific format for third-party systems. In this scenario, you need to transform the ps:Position_ID field within the ps:Position element to a fixed length of 10 characters, truncate the value if it exceeds 10 characters, and align the output to the left. The template must match the ps:Position element and apply these formatting rules using XTT attributes.

Here's why option A is correct:

Template Matching: The <xsl:template match='ps:Position'> correctly targets the ps:Position element in the XML, as shown in the provided snippet, ensuring the transformation applies to the appropriate node.

XTT Attributes:

xtt:fixedLength='10' specifies that the Pos_ID field should be formatted to a fixed length of 10 characters. If the ps:Position_ID value exceeds 10 characters, it will be truncated (by default, XTT truncates without raising an error unless explicitly configured otherwise), meeting the requirement to truncate if the value exceeds.

xtt:align='left' ensures that the output is left-aligned within the 10-character field, aligning with the requirement to align everything to the left.

XPath Selection: The <xsl:value-of select='ps:Position_Data/ps:Position_ID'/> correctly extracts the ps:Position_ID value (e.g., 'P-00030') from the ps:Position_Data child element, as shown in the XML structure.

Output Structure: The <Position><Pos_ID>...</Pos_ID></Position> structure ensures the transformed data is wrapped in meaningful tags for the target system, maintaining consistency with Workday integration practices.

Why not the other options?

B .

xml

WrapCopy

<xsl:template xtt:align='left' match='ps:Position'>

<Position>

<Pos_ID xtt:fixedLength='10'>

<xsl:value-of select='ps:Position_Data/ps:Position_ID'/>

</Pos_ID>

</Position>

</xsl:template>

This applies xtt:align='left' to the xsl:template element instead of the Pos_ID element. XTT attributes like fixedLength and align must be applied directly to the element being formatted (Pos_ID), not the template itself, making this incorrect.

C .

xml

WrapCopy

<xsl:template match='ps:Position'>

<Position xtt:fixedLength='10'>

<Pos_ID xtt:align='left'>

<xsl:value-of select='ps:Position_Data/ps:Position_ID'/>

</Pos_ID>

</Position>

</xsl:template>

This applies xtt:fixedLength='10' to the Position element and xtt:align='left' to Pos_ID. However, XTT attributes like fixedLength and align should be applied to the specific field being formatted (Pos_ID), not the parent element (Position). This misplacement makes it incorrect.

D .

xml

WrapCopy

<xsl:template xtt:fixedLength='10' match='ps:Position'>

<Position>

<Pos_ID xtt:align='left'>

<xsl:value-of select='ps:Position_Data/ps:Position_ID'/>

</Pos_ID>

</Position>

</xsl:template>

This applies xtt:fixedLength='10' to the xsl:template element and xtt:align='left' to Pos_ID. Similar to option B, XTT attributes must be applied to the specific element (Pos_ID) being formatted, not the template itself, making this incorrect.

To implement this in XSLT for a Workday integration:

Use the template from option A to match ps:Position, apply xtt:fixedLength='10' and xtt:align='left' to the Pos_ID element, and extract the ps:Position_ID value using the correct XPath. This ensures the ps:Position_ID (e.g., 'P-00030') is formatted to 10 characters, truncated if necessary, and left-aligned, meeting the integration file requirements.

:

Workday Pro Integrations Study Guide: Section on 'Document Transformation (DT) and XTT' -- Details the use of XTT attributes like fixedLength and align for formatting data in XSLT transformations, including truncation behavior.

Workday Core Connector and EIB Guide: Chapter on 'XML Transformations' -- Explains how to use XSLT templates with XTT attributes to transform position data, including fixed-length formatting and alignment.

Workday Integration System Fundamentals: Section on 'XTT in Integrations' -- Covers the application of XTT attributes to specific fields in XML for integration outputs, ensuring compliance with formatting requirements like length and alignment.

Answer : D

The task involves processing the 'Legal Name - First Name' field in Workday to meet a third-party vendor's requirement of accepting only one-word first names. For workers with multiple names (e.g., 'John Paul'), separated by a single space, the logic must:

Extract the value before the space (e.g., 'John' from 'John Paul').

Count the characters in the extracted value.

Check if the character count is greater than 0.

Use the extracted value if the count is greater than 0; otherwise, use the original 'Legal Name - First Name' field.

This logic is typically implemented in Workday using calculated fields within a custom report or integration (e.g., EIB or Studio). Let's break down the required functions:

Substring Text:This function is needed to extract the portion of the 'Legal Name - First Name' field before the space. In Workday, the Substring Text function allows you to specify a starting position (e.g., 1) and extract text up to a delimiter (e.g., a space). For example, Substring Text('John Paul', 1, Index of ' ') would return 'John.'

Text Length:After extracting the substring (e.g., 'John'), the logic requires counting its characters to ensure it's valid. The Text Length function returns the number of characters in a text string (e.g., Text Length('John') = 4). This is critical for the condition check.

True/False Condition:The logic involves a conditional check: 'Is the number of characters greater than 0?' The True/False Condition function evaluates this (e.g., Text Length(extracted value) > 0), returning True if the extracted value exists and False if it's empty (e.g., if no space exists or extraction fails).

Evaluate Expression:This function implements the if-then-else logic: if the character count is greater than 0, use the extracted value (e.g., 'John'); otherwise, use the original 'Legal Name - First Name' field (e.g., 'John Paul'). Evaluate Expression combines the True/False Condition with the output values.

Option Analysis:

A . Extract Single Instance, Text Length, Numeric Constant, True/False Condition: Incorrect. Extract Single Instance is used for multi-instance fields (e.g., selecting one dependent), not text parsing. Numeric Constant isn't needed here, as no fixed number is involved.

B . Text Constant, Substring Text, Arithmetic Calculation, Evaluate Expression: Incorrect. Text Constant provides a fixed string (e.g., 'abc'), not dynamic extraction. Arithmetic Calculation isn't required, as this is a text length check, not a numeric operation beyond comparison.

C . Format Text, Convert Text to Number, True/False Condition, Evaluate Expression: Incorrect. Format Text adjusts text appearance (e.g., capitalization), not extraction. Convert Text to Number isn't needed, as Text Length already returns a number.

D . Substring Text, Text Length, True/False Condition, Evaluate Expression: Correct. These functions align perfectly with the requirements: extract the first name, count its length, check the condition, and choose the output.

Implementation:

Create a calculated field using Substring Text to extract text before the space.

Use Text Length to count characters in the extracted value.

Use True/False Condition to check if the length > 0.

Use Evaluate Expression to return the extracted value or the original field based on the condition.

Reference from Workday Pro Integrations Study Guide:

Workday Calculated Fields: Section on 'Text Functions' details Substring Text and Text Length usage.

Integration System Fundamentals: Explains how calculated fields with conditions (True/False, Evaluate Expression) transform data for third-party systems.

Core Connectors & Document Transformation: Highlights text manipulation for outbound integration requirements.