Ë oVXjÒã ó0—ddddddddggd¢d gd ¢id d d œ y)z#Xenoptics Leave Approval Extensionsz 19.0.2.4.0z?Configurable approval chains + HR override actions for Time OffaÊ Feature-parity additions for the XENHR -> Odoo migration's Leave module: - Multi-step leave approval chain (v2), ported from XENHR's real ApproverConfigController/LeaveApprovalStep source: xeno.leave.approver is now an ordered per-department/per-employee step template (employee overrides fully replace the department chain when configured, both always end in a synthetic "any HR/Admin" final step). Submitting a leave snapshots the resolved chain onto xeno.leave.approval.step; each step is approved individually (previous steps must already be approved), and the leave itself only transitions to Approved when the last step clears -- rejecting any single step rejects the whole request, matching XENHR exactly. Legacy leaves with no snapshot fall back to the old, simpler behavior unchanged. - HR override on hr.leave: force-approve / force-reject regardless of current state, and an HR Update wizard to edit dates/type on a leave application after submission -- both restricted to Time Off Officers/Responsible, both logged to the chatter for an audit trail. - "My Team Leaves" action: leaves currently pending at a stage where the logged-in user is the configured approver (employee-specific rule wins, else department rule, else falls back to normal group-based access so nothing already working today gets locked out). - Per-leave-type request timing limits (advance notice / max backdate), mirroring XENHR's leave_types.advance_days / max_backdate_days and its exact validation priority -- enforced on self-service creation only, bypassed for Time Off Officers creating on an employee's behalf (same as XENHR's storeForEmployee). - Terminology: relabels Odoo's standard approval action buttons on both hr.leave and hr.leave.allocation (form/list/kanban) from "Validate"/ "Refuse" to "Approve"/"Reject", so the wording matches this module's own Force Approve/Force Reject buttons. - New standalone "HR" app (additive -- Employees/Attendances/Leave are untouched) with two custom pages styled after XENHR's own screens: "Leave List" (pill status tabs, Export/Import/New Request, per-row approval-chain stepper, Edit/Add Approver/Override/Cancel actions) and "Leave Approval" (Pending My Approval with a Your Step/Full Chain view and Approve/Reject, plus a My Team Leaves history section below). Both are thin OWL front-ends over the existing approval-chain data/actions above -- no new approval logic, just a different, XENHR-matching UI. Ú XenopticszLGPL-3zHuman Resources/Time OffÚ hr_holidays) zsecurity/ir.model.access.csvzsecurity/leave_security.xmlzviews/leave_approver_views.xmlzviews/leave_type_views.xmlz wizard/leave_hr_update_views.xmlz'wizard/leave_approver_preview_views.xmlz#wizard/leave_add_approver_views.xmlzviews/hr_leave_views.xmlz%views/leave_approval_status_views.xmlz views/leave_allocation_views.xmlz!views/leave_terminology_views.xmlzviews/hr_app_menu.xmlzweb.assets_backend) z1xeno_leave/static/src/xml/pivot_measure_color.xmlz3xeno_leave/static/src/scss/pivot_measure_color.scssz0xeno_leave/static/src/scss/leave_apply_form.scssz+xeno_leave/static/src/js/leave_hr_common.jsz-xeno_leave/static/src/js/leave_list_action.jsz1xeno_leave/static/src/js/leave_approval_action.jsz2xeno_leave/static/src/xml/leave_list_templates.xmlz6xeno_leave/static/src/xml/leave_approval_templates.xmlz,xeno_leave/static/src/scss/leave_hr_app.scssTF) ÚnameÚversionÚsummaryÚ descriptionÚauthorÚlicenseÚcategoryÚdependsÚdataÚassetsÚ installableÚ applicationN©róú__manifest__.pyúrsGðà 1ØØPð'ðPØØ*؈ò ð ò  ð ðØóYMr