Workday-Pro-Absence Exam Dumps

A leave type without balance tracking supports simple leave request and approval functionality. Although it does not maintain a fixed entitlement, administrators can still define who is eligible, determine which days count in the leave request, and specify whether leave is measured in days or hours. Some validation rules can also be applied to control invalid requests.

The complete configuration normally includes a leave family, On Leave status visibility, eligible worker type, unit of time, calendar-display option, and Days to Include. The eligibility design can contain additional criteria based on Worker or Position data. What the configuration cannot contain is an entitlement calculation that produces and tracks a remaining leave balance.

Accrual frequency, upper and lower limits, carryover, period schedules, and accrual priorities belong to time off plans rather than non-balance leave types. Entitlement-per-event functionality is relevant to balance-tracking leave types because Workday must create and reduce an entitlement balance for each qualifying event.

Option A therefore identifies the applicable elements without incorrectly introducing time off plan balance mechanics or leave entitlement accounting.

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

Workday's primary leave-of-absence setup components are leave families and leave types. The Maintain Leave Families task creates the high-level categories used to group related leave types. Examples can include Regulatory Leave, Company Leave, or Disability Leave. When a user initiates a leave request, Workday displays the leave family as the category containing the available leave types.

The Create/Edit Leave Type task establishes the detailed rules for a specific leave. It configures eligibility, validations, unit of time, On Leave status visibility, entitlement, balance tracking, balance-calendar dates, Days to Include, supporting data, coordinated leave relationships, and cross-functional effects. The leave type must be associated with a leave family.

Maintain Time Off Types and Create Period Schedule relate to time off configuration. Configure Absence Type Groups can improve the request-selection interface by grouping time offs, absence tables, and leaves, but it does not create the underlying leave definition. Create Absence Table manages cascading time off plans, while accrual tasks govern time off balance additions. Therefore, Maintain Leave Families and Create/Edit Leave Type are the two foundational leave setup tasks.

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

Clearing Do Not Allow Request converts the applicable validation from a blocking error into a warning. When the request fails the validation, Workday displays the warning message but permits the user to save and submit the request. The request can then continue through the configured business process, where a manager or administrator can review, approve, send back, or deny it.

When Do Not Allow Request is selected, Workday prevents the employee from saving a request that fails the validation and displays an error. Clearing the checkbox does not cause Workday to correct the quantity automatically or present guided correction prompts. It only changes the validation's enforcement level.

This configuration is available for supported validations such as Maximum Unpaid Time Off Units Allowed, Consecutive Days Maximum, and Consecutive Days Minimum. Administrators can also define custom text to explain the warning and optionally place that text before the standard message. If Allow Override for Entry on Behalf of Worker is configured, authorized managers or administrators can proceed when entering an otherwise invalid request for an employee.

Study Guide reference: Time Off Validations -- Do Not Allow Request.

Scheduling: Worker Hired Mid-Period identifies workers whose hire date occurs after the applicable period has started. Adding this calculation as a scheduling rule provides a separate trigger for the front-loaded accrual when a worker is hired after January 1. The accrual amount calculation can then apply the required proration.

The January scheduling condition processes the regular full-year award for workers who are already eligible at the beginning of the year. That condition alone does not ensure that a worker hired later receives an accrual because the worker was not eligible when the January event was processed. Scheduling: Worker Hired Mid-Period captures this second event.

Scheduling: Last Period of the Balance Period would process the accrual near the end of the balance year and contradicts the stated requirement. Scheduling: Front-Loaded identifies the nature of front-loaded processing but does not independently isolate mid-period hires. The scheduling grid can contain separate rows, applying OR logic between rows, so either the annual January condition or the mid-period-hire condition can initiate processing.

Study Guide reference: Calculations for Time Off Plans -- Scheduling Rules and Front-Loaded Accruals.

The correct answer is the organizational policy and how the absence is tracked and reported for that specific absence type. When configuring absence types in Workday, the unit of measure (hours or days) should reflect how your organization actually tracks and manages that absence. For example, you might track sick leave in hours to allow partial-day absences, while tracking vacation in days for full-day increments. The choice is a business decision based on your organization's absence management practices, not automatically determined by employment status, geography, or absence duration. While some jurisdictions have legal requirements, the unit of measure itself is a configuration choice made during absence type setup.