In Workday HCM, organizations such as Company are used extensively during hiring, job changes, and other staffing events. To control how an organization is presented and selected during these processes, Workday provides two important configuration concepts: default organizations and allowed organizations . Understanding the distinction between these two is essential to achieving the desired behavior.

If Company 1000 needs to be both automatically selected and the only selectable option during the hiring process, it must be configured as both the default and allowed organization . Setting Company 1000 as the default organization ensures that it is pre-populated on the hire event, reducing data entry and minimizing user error. However, default alone does not restrict users from changing the value.

To ensure that Company 1000 is the only company that can be selected , it must also be configured as an allowed organization . Allowed organizations define which values are valid and selectable for a given organization type. By limiting the allowed organization list to Company 1000, Workday prevents users from selecting any other company during the hiring process.

Option A is incomplete because configuring an organization as default does not prevent other companies from being selected. Option D is also insufficient because allowed organization alone does not ensure the value defaults automatically. Option C is unrelated, as superior and subordinate relationships define hierarchy, not selection behavior.

From a Workday Pro HCM best-practice standpoint, combining default and allowed organization configuration provides both efficiency and control. Therefore, the correct and fully verified answer is Configure it as the default and allowed organization .

In Workday HCM, the ability to run reports , including Workday-delivered standard reports , is governed by domain security , not by report writer or administrator roles. Domain security controls access to the data itself , and without access to the underlying domains referenced by a report, a user cannot run the report—even if the report is standard and delivered by Workday.

Standard reports are prebuilt and do not require report creation or modification privileges. Therefore, users do not need to be members of the Report Writer or Report Administrator security groups to run them. Those roles are only required for creating, copying, modifying, or administering reports—not for execution.

Additionally, access to a business process is unrelated to report execution. Business process security determines who can initiate or participate in transactions such as Hire or Termination, but it does not control visibility into report data.

Workday evaluates a user’s domain security policies at runtime to determine whether they can access the data objects used in the report. If the user lacks permission to one or more required domains, the report will either fail to run or return incomplete or restricted results. This applies equally to standard and custom reports.

From a Workday Pro HCM best-practice standpoint, ensuring users have the appropriate domain access —typically through role-based or user-based security groups—is the correct way to enable report execution. Report access groups alone are insufficient without the necessary domain permissions.

Therefore, the correct and Workday-verified reason a user cannot run a Workday Standard Report is that the user does not have access to the appropriate domain .

In Workday, when multiple configurable compensation bases qualify for an employee, the system determines the primary compensation basis using ranking precedence . The compensation basis with the lowest numerical ranking takes priority, provided the employee meets its eligibility criteria. Unranked compensation bases are only used when no ranked bases apply.

In this scenario, the employee is:

Full-time

Not in sales

Located in Mexico

Based on eligibility:

Total Compensation Non-Sales applies (full-time, non-sales).

Total Pay (Mexico) applies (Mexican employees).

Salary and Seniority applies (all employees).

Among these, Total Compensation Non-Sales has the highest priority because it has the lowest ranking value (20) . Although Total Pay (Mexico) is country-specific, its ranking (40) gives it lower precedence. Salary and Seniority is unranked and therefore only applies if no ranked basis qualifies, which is not the case here.

Workday’s compensation basis evaluation logic always selects the highest-ranked (lowest number) qualifying basis as the primary basis for compensation calculations and validations.

Therefore, the correct answer is Total Compensation Non-Sales .

Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core – Reporting and Analytics Guide, 2023R2):

In Workday Reporting, to organize or arrange the display of report results based on specific criteria — such as the Supervisory Organization Name — you use the Sort configuration option.

Sorting determines the order in which records appear when the report is executed. In this case, by sorting on the Supervisory Organization Name field, all workers will be grouped together under their respective organization, making the output intuitive and structured for analysis.

Option B ( Share ) controls who has access to the report.

Option C ( Filter ) limits which records are included in the results.

Option D ( Subfilter ) refines filter logic but does not control display order.

Thus, Sort is the correct configuration feature to organize report results for any user running the report.

Reference (Paraphrased Source):

Workday Pro HCM Core – Reporting Configuration and Design Guide (2023R2), Section: “Sorting, Grouping, and Display Options in Custom Reports.”

In Workday, a subprocess is a step type used within a business process definition to initiate another, independent business process . The purpose of a subprocess is to trigger a set of predefined steps from a separate process that runs as part of the main (parent) process. This provides modularity and reusability across multiple BPs.

For example, when configuring a Hire process, you might add a Request Compensation Change subprocess to automatically launch once the hire is initiated. This avoids duplicating configuration work and ensures consistency in how related actions are handled across events.

Option A is incorrect because approvals are managed through Approval Steps , not subprocesses.

Option C is incorrect — background processes are system-managed and not user-configured through subprocesses.

Option D refers to To-Do or Notification Steps , which are informational, not subprocess-driven.

Thus, subprocesses are a way to embed or chain additional processes into an event flow, promoting flexibility and maintainability.

Reference (Paraphrased Source):

Workday Pro HCM Core – Business Process Configuration Guide (2023R2), Section: “Subprocess Step Type and Configuration Best Practices.”

In Workday, the Manage Basis Total configuration enables organizations to enter a single total compensation amount , which Workday then allocates across multiple compensation plans according to predefined rules, percentages, or limits. This is particularly useful in countries like Italy, where compensation discussions often focus on total compensation rather than individual components.

When Manage Basis Total is enabled on a compensation basis, administrators or managers can enter one total amount during a staffing or compensation event. Workday automatically distributes that amount across salary, allowances, and other included plans based on the compensation basis configuration.

Eligible Earnings Override is a payroll-specific tool and does not control compensation entry behavior. Total Base Pay and Total Salary & Allowances are reporting or calculation concepts, not data entry mechanisms.

By using Manage Basis Total , the company ensures consistency, simplifies compensation entry, and enforces internal rules for Milan-based employees.

Therefore, the correct answer is Manage Basis Total .

In Workday HCM, business process templates define the foundational structure of a business process, including the types of steps that are available to be configured. When administrators need to determine which action steps —such as approvals, To Do steps, notifications, integrations, or subprocesses—can be added to a specific business process, the correct Workday-delivered report to use is View Business Process Template .

The View Business Process Template report displays the delivered template for a given business process and outlines all supported step types and actions that Workday allows for that process. Because templates are system-delivered and cannot be modified, this report serves as the authoritative reference for understanding what configuration options are available before adding or modifying steps in a business process definition.

The other options do not fulfill this purpose. Business Process Security Policy for Functional Area and Domain Security Policies for Functional Area focus on security access and permissions, not step availability. Business Process Configuration Options is used to identify which business process definition applies to specific organizations, not which step types can be added.

From a Workday Pro HCM best-practice perspective, administrators should always consult the View Business Process Template report before designing or troubleshooting business process configurations. This ensures that changes align with Workday’s delivered framework and prevents configuration errors caused by attempting to add unsupported step types.

Therefore, the correct and Workday-verified answer is View Business Process Template , as it identifies which action steps can be added to a business process.

In Workday HCM, period salary plans are specifically designed to support compensation structures where base pay is distributed over a defined number of periods that may not align with standard monthly or annual salary conventions. This is particularly important for countries such as Italy, where statutory or customary compensation practices include additional salary payments , often referred to as the 13th and 14th month salaries . These additional payments result in employees receiving more than 12 months of pay within a year.

A period salary plan allows organizations to define the number of salary periods per year , such as 12, 13, 14, or other values like 14.9, without altering the employee’s annualized base pay. This ensures compliance with local labor laws while maintaining consistent reporting, budgeting, and payroll calculations. Workday then prorates or distributes the annual amount appropriately across the defined periods.

Other plan types do not support this requirement. A salary plan assumes a standard annual salary without accommodating extra pay periods. Hourly plans are designed for workers paid based on time worked, and unit salary plans are used when pay is based on output or units produced, neither of which align with Italy’s statutory base pay structure.

Therefore, a period salary plan is the correct and Workday-recommended solution for handling additional months of base pay in countries with localized pay practices, making option A the correct answer.

Comprehensive and Detailed Explanation (Paraphrased from Workday Pro HCM Core – Organizations Setup and Management Guide 2023R2):

When creating a new supervisory organization that should inherit attributes such as staffing model, company, and cost center from an existing organization, you use the Create Subordinate task.

This task creates the new subordinate organization directly under a superior supervisory organization. It automatically copies inherited settings such as visibility, organization assignments, and staffing model, ensuring hierarchical alignment and simplifying setup.

Option B ( Create Supervisory Organization ) creates a brand-new top-level supervisory org without inheritance.

Option A ( Assign Roles ) only assigns role-based permissions after creation.

Option C ( Assign Included Organizations ) is used for related org relationships, not for hierarchical creation.

Thus, Create Subordinate is the correct task when the new org must inherit settings from a superior one.

Reference (Paraphrased Source):

Workday Pro HCM Core – Organizations Configuration Guide (2023R2), Section: “Creating Subordinate Supervisory Organizations and Inherited Attributes.”

The Compensation Rule Assignment report is designed to provide a configuration-level view of compensation components and the eligibility rules assigned to them . This report lists all compensation plans—such as salary plans, allowance plans, bonus plans, and one-time payments—that reference an eligibility rule.

This report is especially useful for:

Impact analysis before modifying eligibility rules

Auditing which compensation components rely on shared rules

Understanding eligibility dependencies across compensation configuration

The Employee Compensation Audit focuses on worker assignments, not configuration. Compensation Changes tracks transactional history. Compensation Spreadsheets are manual tools and do not reflect rule usage.

Therefore, the correct report for identifying all compensation components using eligibility rules is Compensation Rule Assignment , making option B correct.