A Simple List Report using the ‘Worker’ data source is the most efficient and maintainable choice. The ‘Worker’ data source contains all the necessary fields: active status, job profile, hire date, and cost center. The ‘hired within last fiscal year’ filter can be built using a relative date filter on the hire date field, and a prompt can be added for cost center. This approach avoids the complexity and potential performance overhead of unnecessary joins or composite structures for a straightforward list requirement.

A Matrix Report is specifically designed for this cross-tabulated view. The core step in creating a Matrix Report is defining the fields for ‘Row Grouping’ (e.g., Location) and ‘Column Grouping’ (e.g., Job Family). The intersection of the rows and columns will automatically display the count (or other summary values) of employees that meet both criteria, perfectly matching the manager’s request for a two-dimensional breakdown.

An Advanced Report is the correct tool for combining data from two related sources. You would add both the ‘Learning Assignment’ and ‘Learning Event’ data sources to the report and create a join between them, most likely on a field like ‘Assignment ID’. This ensures the completion data is correctly matched to each assignment record. You can then create a calculated field to display ‘Complete’ if the completion date exists and is before the due date, otherwise ‘Incomplete’.

The `Today()` function returns the system date where the report is processed, which for a scheduled task is often a server in UTC. `Current_Date()` is context-aware and returns the date relative to the user’s or report’s specified time zone. Replacing `Today()` with `Current_Date()` in your calculated field formula ensures the date logic is evaluated correctly regardless of who runs the report or when a scheduled task executes, making it robust for global deployments.

In Workday, row-level security for sensitive data like compensation is primarily enforced through Domain Security Policies. When a user runs a report containing a field from the ‘Compensation’ domain, the system dynamically filters the results to only include workers for whom the user has ‘View’ access based on those policies. This happens automatically, regardless of how the report is built or shared, ensuring data privacy is maintained at the system level.

Trended Reports work by taking snapshots of data at specified points in time. Selecting ‘All Time’ for the ‘As Of Date’ prompt forces the report to calculate and retrieve data for every single day from the beginning of recorded history, which is incredibly resource-intensive and unnecessary for a 12-month trend. The correct approach is to set the ‘As Of Date’ prompt to a specific date range (e.g., the 1st of each month for the past 12 months) to limit the number of snapshots the report must generate, dramatically improving performance.

A Composite Report is specifically designed to layer multiple report outputs (like a chart and a list) into a single, interactive view. By enabling the ‘Drill-Down’ feature on the chart report (the first layer), you can define that clicking a data point (e.g., a department bar) passes that value as a filter to the second report layer (the termination list). This creates the dynamic, dashboard-like interactivity requested without requiring external tools or complex navigation.

The most efficient and maintainable method is to use Workday’s built-in related business object navigation. When you have a field like ‘Recruiter’ (which is a reference to a Worker), you can expand it in the field browser to select related fields from the Worker object, such as ‘Worker: Name’. This method leverages Workday’s existing data relationships without requiring custom calculated fields or `LOOKUP` functions, and it ensures the data is always in sync with the system.

The ‘is in list’ operator is designed for this exact scenario. It allows you to specify a static list of multiple values (Java, JavaScript) that the field can match. This is cleaner and more performant than creating multiple ‘is equal to’ filter lines. Using ‘contains’ with ‘Java’ would be incorrect, as it would also match unrelated skills like ‘JavaFX’ or ‘Core Java Developer’, returning inaccurate results.

A Simple List Report using the ‘Worker’ data source is the most efficient and maintainable choice. The ‘Worker’ data source contains all the necessary fields: active status, job profile, hire date, and cost center. The ‘hired within last fiscal year’ filter can be built using a relative date filter on the hire date field, and a prompt can be added for cost center. This approach avoids the complexity and potential performance overhead of unnecessary joins or composite structures for a straightforward list requirement.0