feat(fusion_clock): multi-day leave requests (date range)
Request Leave now takes a From/To date range instead of a single day (the To field is optional -> single-day). Added date_to to fusion.clock.leave.request (start kept as leave_date), with overlap detection on submit and a date_to >= leave_date constraint. The absence check and reports now treat a leave as covering its whole span. The form shows two date inputs; the controller accepts date_from/date_to (the old single leave_date payload is still honoured). A migration backfills date_to = leave_date for existing rows. Live and verified on entech 19.0.3.13.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -8,6 +8,7 @@
|
||||
<field name="arch" type="xml">
|
||||
<list>
|
||||
<field name="leave_date"/>
|
||||
<field name="date_to"/>
|
||||
<field name="employee_id"/>
|
||||
<field name="reason"/>
|
||||
<field name="state" decoration-success="state == 'reviewed'"
|
||||
@@ -34,6 +35,7 @@
|
||||
<group>
|
||||
<field name="employee_id"/>
|
||||
<field name="leave_date"/>
|
||||
<field name="date_to"/>
|
||||
<field name="created_from"/>
|
||||
</group>
|
||||
<group>
|
||||
|
||||
Reference in New Issue
Block a user