Pasco Digital New

Leave Periods (V747) — your leave years, e.g. "FY 2026-27". They may not overlap and exactly one is marked current. Closing and re-opening a period was deliberately left out: closing has to run year-end carry-forward and check for requests still in flight, and neither existed yet, so a Close button would have produced a period that looked settled while nothing had been. CLOSED exists as a value but is unreachable — the screen offers Draft and Open, the server refuses Closed. Leave Types (V748/V750) — the catalogue: earned, casual, sick, maternity and so on, twelve standard Indian types seeded. Each records how it behaves: paid or not, whether unused days carry forward, whether it can be cashed in, who's eligible, whether a medical certificate is needed. How much of each you get is deliberately not here — that's a policy decision that varies by grade and location. Types are never deleted, only switched off, because a deleted type would leave historical requests pointing at nothing. The menu entry was hidden in V749 and put back in V750 once the screen actually existed. Weekly-off patterns (V751) — the old model was a flat yes/no per weekday, which can't express the two arrangements most Indian employers actually use: "second and fourth Saturday off", and rotational offs on a service floor where the day off moves through the week. Employees on either had their leave counted wrongly. Three kinds now: fixed, nth-weekday, and rotational. A pattern can cover a whole branch or one person, and is date-bounded so an arrangement can change without losing what it used to be. Important: this does not yet change clock-in/clock-out — attendance still reads working hours exactly as before. Wiring the two together was held back deliberately because it changes something people rely on daily. Leave Policies (V752) — where the actual numbers live. A policy applies to a group described by scope rows (branch, department, designation, employment type, state, or any combination). Where two policies both match someone, the more specific one wins; where they're equally specific, higher priority wins. Inside a policy there's one rule per leave type carrying entitlement, accrual, carry-forward, and limits — plus service-based slabs for "15 days in your first two years, 21 thereafter". Encashment, restricted holidays and notice-period settings were left out on purpose: showing HR a setting that changes nothing is worse than not showing it. Holiday calendars (V753/V754) — didn't exist anywhere in the product. Holidays differ by state and by site so they're held as calendars, not one national list, and a calendar belongs to one leave year because the dates move. Which calendar applies to you resolves in order: personally assigned → your department's → your primary branch's → the default. One national calendar is seeded as default, containing only the four holidays whose dates never move (the three India mandates for every establishment, plus Christmas). Festival dates follow the lunar calendar — seeding those would have invented dates that are wrong by year two while looking authoritative. Leave approval configuration (V755) — nothing about the approval chain is hardcoded. A level resolves to the applicant's reporting manager, their department head, anyone holding a role or permission, or one named person, and the chain is read in level order at submit time. The scope on a level is mandatory, deliberately: a level resolving on "anyone with the approve permission" with no scope fans out company-wide, and a request in one branch lands in an inbox three states away. Every change to a chain is versioned, because "who was allowed to approve this" gets questioned months later and the answer has to be what the chain looked like at the time.