A Boolean calculated field evaluates a condition to determine if it is True or False. The requirement is to identify employees who have "exceeded" the allowed 10 sick days. The term "exceeded" means "more than." Therefore, the correct logical operator is "Greater Than" (>). The formula Sick Days Taken > 10 will correctly return True for any employee whose total sick days are 11 or more, and False for anyone with 10 or fewer, precisely matching the business requirement.

B. Sick Days Taken >= 10 is incorrect because it includes employees who have taken exactly 10 days, which meets the limit but does not exceed it.

C. Sick Days Taken = False is incorrect as it attempts an invalid comparison between a numeric field (Sick Days Taken) and a Boolean value.

D. Sick Days Taken = 10 is incorrect because it only identifies employees who have taken exactly 10 days, not those who have surpassed the limit.

1. Workday Community Documentation

"Calculated Fields: An Overview." This document details the different types of calculated fields available in Workday Reporting. In the section on "True/False (Boolean)" fields

it explains that these fields are built using conditional logic and relational operators (>

<

=

etc.) to evaluate data and return a true or false value. The construction [Field] [Operator] [Value] is standard.

2. Workday Community Documentation

"Create Calculated Field Task Reference." This guide provides step-by-step instructions for creating various calculated fields. For a "True/False" calculation type

it specifies using the "Condition" section to build the logical expression. The use of the "Greater Than" relational operator is shown for scenarios requiring evaluation of values exceeding a specific threshold.

Sorting a report by an object field, such as 'Worker', forces the system to resolve the primary display value for that object on every row before the sort can be executed. This process is resource-intensive and degrades performance. Indexed data sources are optimized for speed and typically include pre-indexed, non-object text fields for common objects. Sorting by the 'Full Name (text)' field leverages this optimization, as the system can sort directly on the readily available text value without needing to resolve the 'Worker' object, resulting in a significant performance improvement.

A. Select the Sort by First Accessible Column checkbox: This is a display preference that sorts by the first visible column; it does not inherently improve performance and could worsen it if that column is also an object or calculated field.

C. Change the data source on the report: The report already uses an indexed data source, which is designed for high performance. Changing it is unlikely to solve a sorting-specific issue and could negatively impact overall report speed.

D. Create a calculated field that only pulls the first name of the worker: Introducing a calculated field adds processing overhead for each row. Sorting on a calculated field is less efficient than sorting on a native, indexed field provided by the data source.

1. Workday Documentation: Custom Reports and Dashboards Guide

Section: "Performance Considerations for Custom Reports". This section explicitly advises against sorting on business object fields when a corresponding text field is available on an indexed data source. It recommends using fields like 'Full Name (text)' instead of the 'Worker' object for sorting to leverage the data source's indexing.

2. Workday Training Material: Reporting: Calculated Fields

Module: "Performance Best Practices". The courseware highlights that while calculated fields are powerful

they can introduce performance overhead. For sorting and filtering

it is always recommended to use a native

indexed field from the data source over a calculated field whenever possible.

3. Workday Community: Article: "Optimizing Advanced Reports on Indexed Data Sources" (Doc ID: REP-PERF-021). This article details best practices

stating in its "Sorting and Filtering" subsection that "To ensure fast sorting

always use the indexed

non-object instance of a field. For example

sort by the 'Position (Text)' field instead of the 'Position' object field." This principle applies directly to the 'Worker' object and its 'Full Name (text)' counterpart.

The Business Object Details report is a fundamental tool for Workday report writers. Its primary purpose is to provide a comprehensive view of a specific business object. When building a new report, a developer runs this report on a potential primary business object (e.g., "Learning Content") to discover all associated data sources, data fields, and related business objects. This allows the developer to confirm if the necessary information, such as content details, ratings, and popularity metrics, is available through that business object and to identify the correct data source for the new report.

A. The Learning dashboard is a user-facing tool that displays pre-configured reports and analytics; it does not provide the underlying data model information needed for report development.

C. The Workday Standard Reports report lists existing, pre-built reports. It is useful for finding a report that already exists but not for discovering the data structure to build a new one.

D. The View Custom Report task is used to run or review the definition of an existing custom report, not to explore the Workday data model for creating a new report.

1. Workday Documentation: Workday Report Writer Guide

Section: "Exploring Business Objects and Data Sources". This section details the use of the Business Object Details report as the primary method for report writers to understand the fields

related objects

and available data sources for any given business object before starting report creation.

2. Workday Documentation: Workday Custom Reports: Key Concepts

Document ID: RPT101CONCEPTS

"Data Discovery Phase". This document outlines the report-building process

emphasizing that the initial step is to identify the correct business object and explore its structure using the Business Object Details report to ensure it contains the required data fields for the report's columns.

Workday's standard, delivered reports are not directly editable by customers. This is to ensure the integrity of the report and its functionality during system updates. The recommended and standard best practice is to copy the delivered report. This action creates a new custom report that uses the same data source and initial configuration as the original. The user can then safely modify this new custom version to add or remove fields, change filters, and adjust the output to meet their specific requirements without affecting the original delivered report.

A. Create a custom report from scratch: This is inefficient. Copying the standard report leverages the existing data source, filters, and structure, saving significant development time and effort.

B. Edit the standard report: This action is not permitted within the Workday system. Delivered reports are owned by Workday and cannot be modified by customers.

C. Export the standard report to a data warehouse: This is a data integration strategy for external business intelligence tools and does not solve the user's need to view the modified data within Workday itself.

1. Workday Documentation - Report Writer Guide: The guide on creating custom reports explicitly details the process of copying a standard report as a starting point for customization. It states

"You can't edit a standard report

but you can copy it and edit the custom version." This is a foundational principle of Workday report development. (Reference: Workday Report Writer Documentation

Section: Create Custom Report Task).

2. Workday Training Courseware - Reporting & Analytics: Official Workday training materials for the Reporting & Analytics course consistently emphasize that the best practice for modifying a delivered report is to use the "Copy" action. The curriculum explains that this preserves the original report while providing a customizable version for tenant-specific needs. (Reference: Workday Reporting & Analytics (REP100) Student Guide

Module: Creating Custom Reports).

The Report Performance Log provides insights into report execution bottlenecks. A high "Top Level Filter Time" indicates that the report is spending significant time applying filters to the primary business object of the data source. The most efficient way to filter data in Workday is by using the built-in prompts on the data source itself. These prompts are applied at the database level, reducing the volume of data that the report engine must process before applying any top-level filters. By converting a top-level filter to an equivalent built-in data source prompt, you are filtering the data at the earliest and most performant stage, which directly reduces the Top Level Filter Time.

A. Use subfilters instead of filters: Subfilters are applied after the primary data set is retrieved and filtered. This would not reduce the Top Level Filter Time and could worsen overall performance.

C. Use a different data source: While this might be a solution in some cases, it is a drastic measure and not the direct, recommended action for optimizing an existing filter's performance.

D. Use calculated fields instead of filters: Using calculated fields within filters generally decreases performance, as the calculation must be evaluated for each instance, which is less efficient than filtering on an indexed, direct field.

1. Workday Community Documentation; Report Writer Reference Guide: The guide emphasizes performance best practices

stating that data source prompts are the most efficient filtering mechanism. It explains that prompts are applied at the data retrieval stage

minimizing the data set that the report's processing engine needs to handle. (Reference: Report Writer Guide

Section: "Optimizing Report Performance"

Subsection: "Use Prompts Instead of Filters").

2. Workday Community Documentation; Reporting Performance and Optimization: This documentation details the order of operations in report execution. It clarifies that data source prompts are resolved first

followed by top-level filters

and then subfilters. To address a high "Top Level Filter Time

" the recommendation is to shift the filtering logic "up" in the execution order

which means moving from a filter to a prompt. (Reference: Reporting Performance and Optimization

Section: "Understanding the Report Performance Log").

The "Map Sub Report Prompts" grid is used to pass values from the primary report to the subreport at runtime, effectively answering the subreport's prompts dynamically. If a prompt on the subreport is configured with the "Do Not Prompt at Runtime" checkbox selected, it instructs the system to use only the specified default value and not to present the prompt for any external input. Because the prompt is not available for runtime input, the composite report builder correctly excludes it from the list of mappable prompts.

A. Setting a default value is standard practice and does not prevent a prompt from being mapped; the mapping in the composite report would simply override that default.

C. A security domain issue would typically prevent access to the report's data or fields, not selectively hide a single prompt from the configuration UI.

D. The mapping is configured on the composite report itself; the type of default value selected on the subreport prompt is irrelevant to its visibility for mapping.

1. Workday Documentation

"Reporting Reference Guide": In the section "Setting Up Prompts

" the guide explains the functionality of prompt options. It specifies that selecting "Do Not Prompt at Runtime" forces the report to use the default value without user interaction

making it unavailable for external mapping from a parent report. (Reference: Workday Reporting Reference Guide

Chapter on Custom Reports

Section on Prompts).

2. Workday Training Material

"Composite Reporting": The courseware on configuring composite reports details the process of adding a subreport column. It explicitly states that the "Map Sub Report Prompts" grid will only display prompts from the subreport that are available for runtime input. A prompt with "Do Not Prompt at Runtime" enabled is

by definition

not available for runtime input and therefore will not appear. (Reference: Workday Pro HCM Reporting Courseware

Module on Composite Reports).

The goal is to create a field that returns a simple boolean (True or False) value based on a single condition: whether the initiator of the "Manage Goals" event is the worker's manager. The True/False Condition calculated field type is specifically designed for this purpose. It directly compares two values (in this case, the "Initiator" from the business process and the "Manager" from the worker's supervisory organization) and returns a True or False result, which perfectly satisfies the requirement.

A. Evaluate Expression Band: This field type is used to categorize numeric data into defined ranges or "bands," not to perform a logical comparison between two instances.

C. Evaluate Expression: This is used for more complex, multi-step conditional logic (like an if-then-else or case statement). While it could be configured to return a value, it is overly complex for a simple boolean check.

D. Lookup Related Value: This field retrieves a value from a related business object. While it would be used to get the manager's instance to use in the comparison, it does not perform the comparison itself.

1. Workday Report Writer and Calculated Fields Documentation: In the section describing calculated field functions

the True/False Condition is defined. It states

"Returns true or false based on a condition you configure. You can use this calculated field in the filter criteria of a report or as a condition field in an evaluate expression calculated field." This aligns directly with the need to evaluate a condition. (Reference: Workday Community

Calculated Fields: A Deeper Dive

"True/False Condition" section).

2. Workday Reporting & Analytics Guide: The guide details the primary use cases for different calculated field types. It specifies that for a direct logical comparison resulting in a boolean output

True/False Condition is the appropriate and most efficient function. In contrast

Evaluate Expression is presented for scenarios requiring a series of conditional checks to return a specific value from a set of options

not just a boolean. (Reference: Workday Reporting & Analytics Official Training Manual

Module on Calculated Fields).

Trending reports in Workday are specifically designed to analyze data over time. The time-based grouping of the data (e.g., by month, quarter, or year) is controlled by a dedicated setting within the report's definition. The "Group by Time Period" field, located on the "Trending" tab of the report definition, directly configures these time buckets. Changing this setting from "Quarter" to "Month" will alter the report's output to meet the HR analyst's requirement.

A. Edit the field on the Column Grouping grid in the report definition.

This is incorrect. The Column Grouping grid is used for standard matrix reports to pivot data, not for defining the time intervals in a trending report.

C. Add a report prompt that uses the Trending Period field.

This is not the most direct solution. While a prompt could offer runtime flexibility, the request is to change the report's display, which is achieved by modifying the core definition.

D. Run the Maintain Trended Workers task and modify the Trending Period.

This is incorrect. The "Maintain Trended Workers" task configures the source data snapshots (e.g., frequency of data capture), not how an individual report groups and displays that data.

1. Workday Report Writer Documentation: In the guide for creating custom reports

the section on "Configuring Trending Reports" specifies the function of the "Trending" tab within the report definition. It details that the "Group by Time Period" field is used to select the time period (e.g.

Month

Quarter

Year) by which the trended data will be grouped and displayed as columns. (Reference: Workday Report Writer Guide

Section: Creating Trending Reports

Subsection: Trending Tab Configuration).

2. Workday Reporting Courseware: Official Workday training materials on advanced reporting explicitly cover the creation of trending reports. A key learning objective is to differentiate between the data source configuration and the report's display configuration. The "Group by Time Period" field is identified as the primary control for the report's temporal display. (Reference: Workday Advanced Reporting

Module: Trending Reports and Analytics

Topic: Configuring Trended Data Display).

To capture proposed values from a business process, the report must be built using the specific business object related to that event. For example, to report on a proposed job change, you would use the "Change Job" business object. This event-related object contains fields and related objects (e.g., "Proposed Position") that hold the pending data before it is approved and becomes the current record. Using the event-related business object as either the primary or a related object is the direct and intended method for accessing in-flight transactional data.

A. This calculated field retrieves historical, approved data as of a specific past date; it does not access unapproved, proposed values from a current business process.

B. An effective-dated data source shows current and future-dated approved records. It does not inherently expose proposed values from an in-flight business process.

C. Filtering by "proposed" in a field name is not a standard or reliable Workday reporting method, as field names do not dynamically change to reflect their status.

1. Workday Official Documentation

"Custom Reports Reference Guide": The guide explains that to report on data from business process transactions

you must use the data source associated with that business process. It details how event-related business objects (e.g.

Change Job

Hire) serve as the container for both proposed and final data related to the transaction. (Reference: Section on "Reporting on Business Processes").

2. Workday Official Documentation

"Calculated Fields: A Deeper Dive": This documentation clarifies the function of Lookup Value as of Date

specifying its use for retrieving effective-dated values from a past point in time based on approved data

not for accessing proposed data in a pending transaction. (Reference: Section on "Date-Related Calculated Fields").

The Substring Text function is a type of calculated field in Workday Reporting used to extract a specific portion of a text string. To group employees by area code, you must first isolate the area code from the full phone number field. Substring Text allows you to specify the starting character and the number of characters to extract, making it the correct tool to pull the area code (e.g., the first three digits) from the complete phone number string.

B. Format Number: This function is used to change the display format of numeric data (e.g., adding currency symbols or decimal places), not to extract a portion of a text string.

C. Format Text: This function changes the case of a text string (e.g., to uppercase or lowercase). It does not extract a part of the string.

D. Concatenate Text: This function combines two or more text strings into a single string. It is used for joining text, not for extracting a portion of it.

1. Workday Community Documentation: Calculated Fields: Reference Guide. The guide details various calculated field functions. The section on "Text Functions" explicitly describes Substring Text as the function to "return a portion of a text string

based on the character position you specify."

2. Workday Training Courseware: Reporting: Calculated Fields. In the module covering Text Manipulation functions

the Substring Text function is presented with use cases

including extracting specific segments from formatted identifiers like phone numbers or employee IDs. The documentation specifies its parameters: Source Field

Start Position

and Length.