Workday Workday-Pro-Integrations - Workday Pro Integrations Certification Exam Certification Exam
Question #1 (Topic: Demo Questions)
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
Explanation:
The requirement is to filter a custom report to show only workers terminated after a user-prompted
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.
Question #2 (Topic: Demo Questions)
You need to create a report that includes data from multiple business objects. For a supervisory
organization specified at run time, the report must output one row per worker, their active benefit
plans, and the names and ages of all related dependents. The Worker business object contains the
Employee, Benefit Plans, and Dependents fields. The Dependent business object contains the employee's dependent's Name and Age fields.
How would you select the primary business object (PBO) and related business objects (RBO) for the
report?
Correct Answer: B
Explanation:
In Workday reporting, selecting the appropriate Primary Business Object (PBO) and Related Business
In Workday reporting, selecting the appropriate Primary Business Object (PBO) and Related Business
Objects (RBOs) is critical to ensure that the report retrieves and organizes data correctly based on the
requirements. The requirement here is to create a report that outputs one row per worker for a
specified supervisory organization, including their active benefit plans and the names and ages of all
related dependents. The Worker business object contains fields like Employee, Benefit Plans, and
Dependents, while the Dependent business object provides the Name and Age fields for dependents.
Why Worker as the PBO?The report needs to output "one row per worker," making the Worker
business object the natural choice for the PBO. In Workday, the PBO defines the primary dataset and
determines the granularity of the report (i.e., one row per instance of the PBO). Since the report
revolves around workers and their associated data (benefit plans and dependents), Worker is the
starting point. Additionally, the requirementspecifies a supervisory organization at runtime, which is
a filter applied to the Worker business object to limit the population.
Why Dependent as an RBO?The Worker business object includes a "Dependents" field, which is a
multi-instance field linking to the Dependent business object. To access detailed dependent data
(Name and Age), the Dependent business object must be added as an RBO. This allows the report to
pull in the related dependent information for each worker. Without the Dependent RBO, the report
could only reference the existence of dependents, not their specific attributes like Name and Age.
Analysis of Benefit Plans:The Worker business object already contains the "Benefit Plans" field, which
provides access to active benefit plan data. Since this is a field directly available on the PBO (Worker),
no additional RBO is needed to retrieve benefit plan information.
Option Analysis:
A . PBO: Dependent, RBO: Worker: Incorrect. If Dependent were the PBO, the report would output one row per dependent, not one row per worker, which contradictsthe requirement. Additionally,
Worker as an RBO would unnecessarily complicate accessing worker-level data.
B . PBO: Worker, RBO: Dependent: Correct. This aligns with the requirement: Worker as the PBO
ensures one row per worker, and Dependent as the RBO provides access to dependent details (Name
and Age). Benefit Plans are already accessible via the Worker PBO.
C . PBO: Dependent, no RBOs: Incorrect. This would result in one row per dependent and would not
allow easy access to worker or benefit plan data, failing to meet the "one row per worker"
requirement.
D . PBO: Worker, no RBOs: Incorrect. While Worker as the PBO is appropriate, omitting the
Dependent RBO prevents the report from retrieving dependent Name and Age fields, which are
stored in the Dependent business object, not directly on Worker.
Implementation:
Create a custom report with Worker asthe PBO.
Add a filter for the supervisory organization (specified at runtime) on the Worker PBO.
Add Dependent as an RBO to access Name and Age fields.
Include columns from Worker (e.g., Employee, Benefit Plans) and Dependent (e.g., Name, Age).
Reference from Workday Pro Integrations Study Guide:
Workday Report Writer Fundamentals: Section on "Selecting Primary and Related Business Objects"
explains how the PBO determines the report’s row structure and RBOs extend data access to related
objects.
Integration System Fundamentals: Discusses how multi-instance fields (e.g., Dependents on Worker)
require RBOs to retrieve detailed attributes.
Question #3 (Topic: Demo Questions)
What XSL component is required to execute valid transformation instructions in the XSLT code?
Correct Answer: A
Explanation:
The < xsl:template > is the core component in XSLT. It defines the transformation rules that will be applied to nodes in the XML document.
The < xsl:template > is the core component in XSLT. It defines the transformation rules that will be applied to nodes in the XML document.
“Without at least one < xsl:template > element, an XSLT file cannot perform any transformation. This is the execution block where processing logic begins.”
Why the others are incorrect:
B. < xsl:apply-templates > applies templates but is not valid without the actual template definitions.
C. < xsl:call-template > calls named templates — which must first exist.
D. < xsl:output > defines format but does not perform transformation logic.
[Reference:W3C XSLT Specification – Section: xsl:template Required for ExecutionWorkday XSLT Examples – “Template-Based Transformations in Workday”, , ]
Question #4 (Topic: Demo Questions)
Refer to the scenario. You are configuring a Core Connector: Worker integration with the Data Initialization Service (DIS) enabled. The integration must extract worker contact details and job information, including a calculated field override that determines phone allowance eligibility.
When testing, you run the Test Security Related Action from the Configure Integration Field Override step. Several field overrides display “No” in the Available by User column.
To ensure the ISSG has access to these field overrides and that “Yes” is displayed in the Test Security step, what configuration should you review?
Correct Answer: A
Explanation:
The Test Security Related Action shows Available by User = No when the security group running the integration lacks View permissions to the fields used in the override logic.
The Test Security Related Action shows Available by User = No when the security group running the integration lacks View permissions to the fields used in the override logic.
From Workday documentation:
Field Overrides require the ISSG to have View access to the domain policies securing each field referenced in the override, otherwise Workday blocks the field from execution.
Therefore, the appropriate fix is to:
• Identify the domains that secure the calculated fields and overridden fields
• Grant the ISSG View access in those domain security policies
• Activate pending changes
Options B and C incorrectly focus only on web service operations.
Option D incorrectly suggests Modify access — but View is the required minimum.
[References:Admin‑Guide‑Authentication‑and‑Security.pdf — Access to Workday Data: View access required for outbound integration fields, , ]
Question #5 (Topic: Demo Questions)
Your manager has asked for a value on their dashboard for how many days away the birthdays are of their direct reports. The format of the output should be [Worker ' s Name] ' s birthday is in [X] days, where you must calculate the number of days until a Worker ' s next birthday. An example output is " Logan McNeil ' s birthday is in 103 days. "
Which calculated field functions do you need to accomplish this?
Correct Answer: C
Explanation:
The requirement is to create a calculated field for a dashboard that displays a worker’s name and the number of days until their next birthday in the format " [Worker ' s Name] ' s birthday is in [X] days " (e.g., " Logan McNeil ' s birthday is in 103 days " ). This involves calculating the difference between today’s date and the worker’s next birthday, then formatting the output as a text string. Let’s break down the necessary functions: