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

The eight-hour accrual must be entered in the Default Response field of the conditional calculation. A conditional calculation evaluates its configured conditions in sequence. California workers satisfy the California condition and receive 12 hours, while Illinois workers satisfy the Illinois condition and receive 10 hours. Workers who satisfy neither condition fall through to the Default Response and receive eight hours.

The 2nd Operand belongs to a comparison calculation and represents the value against which the first operand is evaluated. It does not define the fallback result of the conditional calculation. Target Instance is used in calculations that resolve or compare a specific business-object instance. Custom field is not the conditional calculation field used to provide an otherwise result.

A default response is essential because the configuration must return a valid numeric accrual amount for every eligible U.S. worker. Without it, workers outside California and Illinois could receive no resolved value. The returned values must use the same unit of time as the associated time off plan—in this scenario, hours.

Study Guide reference: Calculations for Time Off Plans – Conditional Calculations .

Workday distinguishes time off and leave of absence primarily by duration, entitlement structure, return-date certainty, status visibility, and business-process requirements. Time off is generally used for shorter absences such as vacation, sick time, or floating holidays. The organization typically knows when the worker will return, and each day or quantity of time away is entered as part of the request.

Leave of absence is generally longer and can involve an entitlement calculated over a configurable period. The worker’s exact return date may not be known when the leave begins. Workday can display an On Leave indicator next to the worker’s name, and a business process is required to return the worker from leave. Time off uses lighter processing and does not require a return-from-leave event.

These are functional guidelines rather than absolute legal definitions; organizations must evaluate the appropriate configuration for each policy. Time off does not inherently require an employment-status change, and neither function is confined exclusively to Payroll or Benefits. Option B therefore captures the principal operational distinctions recognized by Workday.

Put Period Schedule is the inbound Workday web service used to create or load period schedule data. Workday supports two principal configuration approaches: administrators can manually establish schedules through the Create Period Schedule task, or they can load schedule information through the Put Period Schedule web service, commonly using an Enterprise Interface Builder integration.

The “Put” operation is appropriate because the request changes Workday data by submitting a new or updated business object. A “Get” operation retrieves existing information and therefore cannot create a period schedule. “Get Schedules” and “Put Schedules” are not the delivered service names identified for this Absence configuration requirement.

Period schedules provide consecutive processing periods and may be shared by Workday Absence, Payroll, and Time Tracking when their dates and frequencies align. The inbound data must therefore contain the schedule structure and required period information in a form accepted by the service. Usage must also be configured correctly so that the schedule is available to Absence Management. After loading the data, the administrator should review the schedule, generated periods, application usage, and relevant dates before attaching it to a time off plan.

When the termination is rescinded, Workday automatically reverses the absence consequence associated with that termination. The system removes the termination adjustment that previously reduced the time off plan balance to zero and restores the balance represented by the removed adjustment. This maintains transactional integrity between the worker’s employment status and absence records.

The administrator should not remove the configured Time Off for Termination Adjustment from the plan. That field is part of the plan’s continuing termination-processing design and changing it would affect future terminations. The Overrides Allowed setting is unrelated to reversing a system-generated termination adjustment. Likewise, manually entering a balance override is unnecessary and could create a discrepancy because an override establishes a replacement balance independently of the original termination transaction.

Automatic reversal is significant because the adjustment is linked to the termination business-process event. Rescinding the source event causes Workday to remove its dependent adjustment rather than requiring an administrator to reconstruct the worker’s previous balance manually. Administrators should validate the restored balance and transaction history, but no manual restoration is required under the stated configuration.

Study Guide reference: Absence Management Business Processes – Termination Adjustments and Rescinded Terminations .

Workday classifies leave types according to whether they track an entitlement balance. A leave type without balance tracking supports straightforward leave request and approval processing but does not maintain a fixed entitlement balance. Bereavement or long-term disability can be configured this way when the policy does not require Workday to calculate entitlement minus leave taken.

A balance-tracking leave type retains the same request and approval functionality but adds entitlement accounting. It requires balance-calendar start and end dates, entitlement units or calculations, a unit of time, and rules determining which requested days or hours reduce the entitlement. Workday calculates the remaining balance from entitlement less applicable leave taken, including coordinated leave or intermittent time off where configured.

Paid versus unpaid, statutory versus company-provided, and employee versus contingent-worker distinctions can influence a leave type’s configuration, eligibility, payroll effect, or leave family. They are not the two structural leave-type categories used by Workday. The decisive classification is whether the leave type maintains and calculates a balance. Therefore, option C is the complete technical classification.

A rolling-forward balance calendar begins on the effective date of the leave event—specifically, the First Day of Leave—and ends 12 months after that date. This creates a worker- and event-specific entitlement window that moves forward from the beginning of the applicable leave rather than using fixed calendar-year dates.

Option C reverses the required chronology by placing the calculated date plus 12 months before the original effective date. Options B and D use fixed year boundaries and therefore create calendar-year periods, not rolling-forward periods. Option B also reverses the start and end sequence.

The Balance Calendar Start Date and Balance Calendar End Date calculated fields determine the period over which Workday calculates entitlement minus leave taken. For the requirement that each child generate a separate 180-day entitlement, the leave type should additionally capture the identifying event data, such as the child’s birth date, and use Entitlement Per Event. Those settings distinguish multiple qualifying births, while the balance-calendar configuration establishes the 12-month window for each event.

Study Guide reference: Leave of Absence – Additional Information on the Balance Calendar .

A leave type validation must compare the requested leave with the worker’s available entitlement and respond when the request exceeds the remaining balance. The administrator can use a leave of absence rule based on the delivered sufficient-balance field or an equivalent calculated field, attach it on the leave type’s Validations/Supporting Data tab, and select Do Not Allow Request to make the result a hard error.

Workday evaluates leave validations when the worker submits the request. A hard error prevents the request from continuing through the business process until the amount or dates are corrected. Supporting data can additionally display the current balance, requested amount, and projected remaining entitlement so the worker understands the validation result.

Eligibility determines whether a worker can select the leave type; it does not control how much an eligible worker can request. Hiding the balance changes only what is displayed and provides no enforcement. Absence Accrual Effect indicates that the leave may affect time off accruals and requires related accrual eligibility configuration; it does not enforce the leave entitlement. Therefore, a leave type validation is the control that directly prevents workers from exceeding the 180-day entitlement.

Cascading leave configuration defines the sequence in which one leave type transitions to another. The Long Term Disability Leave Type must therefore be selected in the Next Leave Type field on the Cascading Leave tab of the Short Term Disability Leave Type. This establishes Long Term Disability as the successor when the short-term leave reaches its configured end.

Adding the leave types to the same absence type group only organizes them in the absence-selection interface. A leave family categorizes related leave types but does not create an automated transition. The Additional Leave Types field coordinates leave-taken calculations so that one leave can reduce another leave’s entitlement; it does not define which leave should start after the current leave ends.

The succeeding leave remains subject to its eligibility rules. When automated processing reaches the transition date, Workday can generate a return request for Short Term Disability and a new request for Long Term Disability. The Request Leave of Absence business process must also include the Automated Leave Processing service, normally with a step delay that determines when the transition is evaluated.

Study Guide reference: Absence Management Business Processes – Cascading Leaves .

Balance tracking is a foundational and non-editable characteristic of a time off plan after the plan is saved. Workday specifically identifies Track Balance, Period Schedule, and Unit of Time as fields that cannot be changed after creating and saving the plan. Consequently, an administrator cannot convert the existing plan into a non-balance-tracking plan by clearing either the Track Balance setting or its balance period.

A balance-tracking plan contains architecture that is not present in a basic plan, including a balance period, accrual calculations, carryover behavior, upper and lower limits, balance visibility, and accrual and time-off balance processing. Removing only the balance period would leave the plan configuration internally inconsistent. Adding another accrual would further reinforce balance tracking rather than remove it.

The correct remediation is to remove the incorrectly configured plan and create a new basic time off plan without balance tracking. Before deletion, the administrator should confirm that no production time off requests, accrual results, adjustments, or other transactions depend on the plan. If operational data already exists, the replacement requires controlled migration and effective-dated planning rather than an immediate deletion. Within the stated scenario, deletion and recreation is the valid configuration response.

Workday coordinates short-duration time off with a leave entitlement through the Intermittent Time Offs field on the leave type. The administrator creates the appropriate time off and time off plan, then adds that time off to the Sickness leave type’s Intermittent Time Offs field. Units requested through the intermittent time off are subsequently counted as leave taken and reduce the sickness leave entitlement balance.

When a coordinated intermittent request is processed, Workday evaluates the time off plan balance and the leave entitlement balance independently. The request must satisfy the eligibility and validation rules configured for both the time off and the related leave type. The time off may therefore reduce its time off plan balance while simultaneously reducing the coordinated leave balance.

An absence type group changes how available absence types are organized in the request prompt; it does not coordinate their balances. An accrual calculation adds to a time off plan balance and is not the mechanism for deducting short sickness events from a leave entitlement. Calculated fields can establish an entitlement amount but do not create the transactional relationship between time off taken and leave taken. The Intermittent Time Offs relationship is the configuration designed for this requirement.