When a base calendar was configured with a non-standard number of working hours per day (e.g. 5 hours instead of 8), the Availability Calculation in the Resource Plan always assumed a full day and returned incorrect availability values. For example, a calendar with 5h/day × 22 working days should yield 110 hours, but the grid reported 176 hours (8 × 22).
What changed:
A new optional configuration parameter availUnit has been added to the Advanced Grid JSON configuration. It accepts two values:
Value |
Behaviour |
|---|---|
"day" (default) |
Availability is calculated per day — same as before. No change needed for existing configurations. |
"hour" |
Availability is calculated per hour, using the actual working hours defined in the base calendar. |
The grid now passes the selected unit (days or hours) to the availability API via the outputUnit parameter, which the plugin already supported but was not previously exposed.
What consultants need to do:
▪No action required for customers who work with full-day calendars (8h/day).
▪Enable availUnit: "hour" only for customers whose base calendars define a variable or reduced number of working hours per day.
▪When enabling availUnit: "hour", set availFactor to 1 to avoid a double-conversion (the availFactor multiplier is still applied on top).
Example JSON configuration change:
{
"availFactor": 1,
"availUnit": "hour"
}
▶ No database migration or downtime is required. The change is purely configuration-driven and backwards-compatible.