You need to create a validation that warns a worker if they have multiple time blocks with overtime in a time period. What is the top-level business object?

The validation needs to evaluate multiple time blocks within a specific period. The Time Week business object serves as an aggregate of all Time Block and Time Day data for a seven-day period. By using Time Week as the top-level business object, the validation rule can access and evaluate all time blocks within that week to count the instances of overtime. This aggregated view is necessary to check for a condition like "multiple time blocks with overtime," which cannot be assessed by looking at a single time block in isolation.

B. A validation on Time Block can only evaluate itself; it cannot easily look at other time blocks to count occurrences of overtime within the period.
C. Time Day aggregates blocks for a single day, which is too narrow if the "time period" in the requirement is a week.
D. Worker is too high-level. The validation is concerned with time entry data within a specific week, not the worker's overall record.

1. Workday Administrator Guide, "Time Tracking Validations". The guide lists available business objects for validations and explains their hierarchical relationship, positioning Time Week as an aggregator for Time Day and Time Block.

2. Workday Community, "Calculated Fields for Time Tracking Validations". This resource provides examples of creating aggregate-based calculated fields, often using Time Week to sum or count hours across a period for use in validation rules.

3. Workday Pro Time Tracking Courseware, "Module 5: Advanced Validations". This section details how to build complex validations that require aggregation, highlighting Time Week as the appropriate business object for weekly summaries.