fusion_claims: fix handoff_to_client Selection ordering (v19.0.8.0.4)
In v19.0.8.0.3 the new handoff_to_client MOD state was inserted between project_complete and pod_submitted in the Selection list, so it rendered near the bottom of status dropdowns even though it happens very early in the workflow. Also forgot to add it to _expand_mod_statuses, so it would not appear as a kanban column without holding records. Fixes: - Move handoff_to_client in the Selection tuple to position 6 (right after quote_submitted, right before awaiting_funding) — parallel to quote_submitted as the alternative entry into awaiting_funding - Add handoff_to_client to the main list in _expand_mod_statuses so it always appears as a kanban column - Add handoff_to_client AND awaiting_funding to statusbar_visible on the sale_order form view (awaiting_funding was also missing before) Deployed to odoo-westin (westin-v19) and odoo-mobility (mobility). Re-ran -u fusion_claims on both so Odoo resynced the Selection sequence column. Verified: both databases now show sequence 0..15 with handoff_to_client at sequence 5, identical between servers.
This commit is contained in:
@@ -1479,7 +1479,7 @@
|
||||
<field name="x_fc_is_mod_sale" invisible="1"/>
|
||||
<field name="x_fc_mod_status" widget="statusbar"
|
||||
invisible="not x_fc_is_mod_sale"
|
||||
statusbar_visible="need_to_schedule,assessment_scheduled,assessment_completed,processing_drawings,quote_submitted,funding_approved,contract_received,in_production,project_complete,case_closed"
|
||||
statusbar_visible="need_to_schedule,assessment_scheduled,assessment_completed,processing_drawings,quote_submitted,handoff_to_client,awaiting_funding,funding_approved,contract_received,in_production,project_complete,case_closed"
|
||||
nolabel="1"/>
|
||||
</xpath>
|
||||
</field>
|
||||
|
||||
Reference in New Issue
Block a user