Workday Workday-Pro-Absence - Workday Pro Absence Certification Exam

The Daily Quantity Default field specifies the number of hours or days that Workday automatically supplies for each selected date when a user enters a time off request through the calendar. The value can be a fixed quantity, such as eight hours, or a calculation that derives the worker’s scheduled hours or another applicable quantity.

When a conditional calculation provides the default, Workday evaluates the calculation using the first day of the request and can apply that resolved quantity to the requested dates. The field improves entry consistency and reduces the need for workers to manually enter the expected quantity on every date. A time off can also contain an override when its default quantity must differ from the default established on the plan.

Days to Include determines which dates Workday initially includes when the worker selects a date range, such as all days, weekdays, or workdays. It does not specify the quantity for those dates. The Lower Limit determines the point below which time off becomes unpaid. The Accrual Frequency Method determines whether Workday adds accruals at the start or end of a period or according to a custom frequency. Consequently, only Daily Quantity Default controls the automatically populated daily units.

A Leave Family groups related leave types into a recognizable category. When employees, managers, or administrators enter a leave request, Workday presents the leave family as the category under which its associated leave types appear. For example, an organization might create a Regulatory Leave family for jury duty, military leave, and statutory parental leave, while using a Company Leave family for bereavement or discretionary personal leave.

A Leave Type is the transactional configuration that defines the rules for a specific leave, including eligibility, validation, balance tracking, entitlement, and processing effects. It belongs to a leave family but does not perform the broader grouping function. Absence Family is not the delivered Workday component used for this purpose. Time Off Type categorizes time offs such as vacation or sickness and applies to the time off configuration model rather than leave-of-absence types.

Leave families improve navigation and reporting while allowing each included leave type to retain independent eligibility, entitlement, validation, and security configuration. Administrators create and maintain these categories through the Maintain Leave Families task.

Study Guide reference: Leave of Absence – Leave Families .

The user-facing category displayed in the time off request prompt is the Time Off Type name, which is configured through the Maintain Time Off Types task. Workday describes time off types as categories that group one or more underlying time off definitions. For example, a user may see “Vacation” in the request prompt even though the configuration contains separate underlying time offs for full-time and part-time workers.

This separation provides a cleaner employee experience while allowing administrators to maintain different eligibility rules, validations, plan associations, or calculation behavior behind the same visible category. The worker sees the time off type that applies to the request, while Workday resolves the eligible underlying time off based on configuration.

The Name field on the Create Time Off task identifies the individual time off component; it does not determine the category name presented in the selection prompt described by the question. A time off plan name identifies the overall plan and balance structure rather than the request category. The Code field is an administrative identifier and is not the requested user-facing label. Therefore, the required name is maintained in the Name column of Maintain Time Off Types.

An Increment or Decrement Date calculated field starts with an existing date and adds or subtracts a specified interval. The expected due date is the source date, and the calculation decrements that date by 11 weeks to return the required maternity-related date.

Format Date changes how a date is represented as text but does not move the date backward. Date Difference calculates the elapsed number of days, months, or years between two dates and returns an interval rather than a new date. Arithmetic Calculation performs mathematical operations on numeric values and is not the appropriate calculated-field type for deriving a date relative to another date.

The source field must be available from the business object on which the calculated field is created, such as the leave request event or another object containing the expected due date. The result remains a date value and can therefore be referenced in validation rules, supporting data, reports, or other maternity leave calculations. The administrator should confirm whether the tenant calculation accepts weeks directly or requires the equivalent 77-day decrement.

Study Guide reference: Leave of Absence – Calculated Fields Overview .

The 30-day entitlement is awarded at the beginning of the balance period, so the accrual is classified as front-loaded. If a worker subsequently becomes ineligible because of a job change, Workday must calculate the portion of the front-loaded award that the worker was not entitled to retain. Selecting Front-Loaded activates this proration behavior, while the scheduling condition identifies the business event that should initiate the adjustment.

The scheduling row must use Scheduling: Worker Job Change Mid-Period because the triggering event is a change of job that causes eligibility loss during the balance period. Workday then evaluates the job-change effective date, determines the eligible portion of the calendar year, and creates the corresponding accrual adjustment. The termination condition in option A applies to a termination event, not a job change. Selecting None provides no special mid-period proration. Merely selecting Front-Loaded without the required scheduling condition does not identify when the adjustment should occur.

Study Guide references: Absence Management Administration – Accrual Adjustment during a Job Change and Time Off Plans and Components – Accrual Options .

The validation must apply only to Jury Duty requests without restricting multiple same-day requests for unrelated time offs. The administrator should select All Time Off Entries for Worker (for Time Off Validation Set) for Same Date and create a validation set containing Jury Duty.

This scope instructs Workday to evaluate the worker’s entries for the same date only when those entries belong to the designated validation set. If a Jury Duty request already exists for that date, another Jury Duty request triggers the validation. Other time offs outside the validation set remain unaffected and can still be entered multiple times when their own configuration permits it.

Individual Time Off Entry does not compare the request with other same-day entries and therefore cannot prevent duplicates. All Time Off Entries for Worker for Same Date is too broad because it evaluates every time off and could block legitimate multiple requests involving unrelated absence types. Creating a validation set that excludes Jury Duty reverses the intended scope by applying the comparison to the wrong time offs. A validation set containing Jury Duty provides the required targeted control while preserving the organization’s more permissive behavior for other time-off categories.

The time off plan must have the Overrides Allowed checkbox selected. This plan-level setting enables administrators to use Maintain Time Off Plan Carryover Overrides to change a worker’s calculated carryover amount or carryover expiration date when exceptional circumstances justify an exception.

Adjustments/Overrides Allowed on an accrual enables changes to accrual values for individual processing periods. It does not enable carryover overrides. The corresponding setting on a time off permits adjustments or overrides to time off activity, not to the plan’s carryover calculation. A lower limit override controls the amount of paid time off available when the worker’s balance falls below zero and has no relationship to carryover limits.

After overrides are enabled, the administrator can define an employee-specific carryover exception. The override must differ from the amount generated by the plan, cannot duplicate another carryover override, and cannot establish an expiration date before the carryover date. Retroactive carryover overrides may affect calculated balances, so the calculated balance process may need to be rerun after the change.

Study Guide reference: Absence Management Administration – Maintain Time Off Plan Carryover Overrides .

A balance-tracking leave type requires the ordinary leave request configuration plus the elements necessary to calculate an entitlement balance. The leave family organizes the leave type for user selection. On Leave status visibility controls who can see that the worker is on leave, while the eligible worker type establishes whether the leave applies to employees, contingent workers, or both.

Track Balance must be enabled. Calculated fields define the balance-calendar start and end dates, establishing the period over which Workday calculates entitlement minus leave taken. The unit of time ensures that entitlement and leave usage are consistently expressed in hours or days. Calendar Display determines whether entitlement information appears in the Absence Calendar or Time Off and Leave Calendar. Leave entitlement defines the maximum available units, and Days to Include determines which requested dates or hours reduce the balance.

Period schedules, accrual frequency, upper and lower limits, and carryover rules are time off plan mechanics. Payroll, benefit, and stock effects are optional cross-functional settings, not a complete required configuration. Option A contains the full required set identified by Workday.

Leave Type Segmented Security controls which specific leave types a security role can access when placing a worker on leave. Although the worker satisfies the leave type’s eligibility criteria, the leave will not appear for the manager unless it belongs to a Leave Type Security Segment accessible through the manager’s segment-based security group.

The Request Leave of Absence business process security policy determines whether a manager can initiate leave requests generally. If that initiation security were missing, the manager would be unable to initiate the business process, rather than simply being unable to see one newly created leave type. Opting in to segmented security does not automatically assign new leave types to existing segments. New leave types must be added to the appropriate security segment deliberately.

The administrator should add the new leave type to the manager’s Leave Type Security Segment, confirm that the Manager role is included in the associated segment-based security group, and verify access to the Leave Type Segmented Setup domain. Pending security policy changes must also be activated where applicable.

Study Guide reference: Leave of Absence – Leave Type Segment Security .