{
    "name": "Xenoptics Resignations",
    "version": "19.0.1.2.0",
    "summary": "Employee resignation/separation records, mirroring XENHR's Resignation model",
    "description": """
Feature-parity addition for the XENHR -> Odoo migration's task #11/#12
(resignations module, not in the original gap list -- found while reading
XENHR's actual source).

Mirrors XENHR's `resignations` table and `ResignationController` exactly:
resign_type (resign / end_of_contract / discharge / retirement / terminate
/ transfer / pass_away), resign_date, notice-period start_date, an HR
save_date, a short cause + full narrative detail, and a single attachment.

Same side effect as XENHR's `store()`: creating a resignation record
immediately archives the employee (Odoo's `active=False`, the equivalent
of XENHR's `employment_status = inactive`) and deactivates their linked
user login (`user_id.active = False`, equivalent to XENHR's
`user->is_active = false`) -- there is no draft/approval state in XENHR's
version, so this module doesn't invent one. Deleting a resignation record
does NOT reactivate the employee, matching XENHR's destroy() (which also
only deletes the row).
""",
    "author": "Xenoptics",
    "license": "LGPL-3",
    "category": "Human Resources",
    "depends": ["hr", "xeno_attendance"],
    "data": [
        "security/ir.model.access.csv",
        "views/hr_resignation_views.xml",
        "views/hr_employee_views.xml",
    ],
    "installable": True,
    "application": False,
}