4e0b74d7ae
Replaces the generic Draft/Confirmed/In Progress/Done statusbar with
a shop-configurable list of plating-specific milestones. Bar advances
automatically as recipe steps complete; no manual button clicks.
What ships
==========
* New model: fp.job.workflow.state
Catalog of milestones (name, code, sequence, color, triggers).
Triggers can be:
- trigger_default_kinds: "receiving,inspect" matches by step.default_kind
- trigger_first_step_started: any wet/bake/mask/rack step started
- trigger_all_steps_done: every non-cancelled step in done/skipped
- block_when_quality_hold: held back while NCR/hold open
Plus per-recipe-node override (see below).
* Default 7-state seed (data/fp_workflow_state_data.xml):
Draft → Confirmed → Received → In Progress → Inspected → Shipped → Done
noupdate=1 so per-shop edits survive module upgrade.
* Recipe-side trigger field on fusion.plating.process.node:
triggers_workflow_state_id (Many2one, optional)
Wins over default_kind matching. Lets the recipe author pin a
specific step as a milestone trigger even when default_kind isn't
set or doesn't match. Exposed in the Recipe Tree Editor properties
panel (dropdown sourced from the catalog).
* fp.job.workflow_state_id (computed, stored)
Iterates the catalog in sequence order; lands at the highest passed
milestone. Recomputes on step state / kind / recipe_node / quality
hold changes. Replaces fp.job.state on the form's statusbar.
* Settings UI: Configuration > Workflow States
Standard list+form pages so admins can add / edit / deactivate
states. Manager-group write permission, supervisor read.
What this does NOT do
=====================
* Doesn't drop fp.job.state — that field still drives the internal
state machine (button_confirm, action_cancel, etc.). Only the
UI statusbar is reassigned.
* No migration for existing jobs — they auto-recompute on next read
because workflow_state_id is a stored compute with the right
api.depends. Existing WH/JOB/00342 will display its current
workflow state on next page load.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
41 lines
1.4 KiB
Python
41 lines
1.4 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
#
|
|
# Phase 2 of the native plating job model migration. Models are added
|
|
# task-by-task in Tasks 2.2 onwards.
|
|
|
|
from . import fp_job_workflow_state # Sub 14 — must load before fp_job (FK target)
|
|
from . import fp_job
|
|
from . import fp_job_step
|
|
from . import fp_job_node_override
|
|
from . import fp_portal_job
|
|
from . import account_move
|
|
from . import res_config_settings
|
|
from . import sale_order
|
|
from . import sale_order_line
|
|
|
|
# Phase 3 — parallel job/step links on dependent modules' models.
|
|
from . import fp_batch
|
|
from . import fp_quality_hold
|
|
from . import fp_certificate
|
|
from . import fp_thickness_reading
|
|
from . import fp_delivery
|
|
from . import fp_racking_inspection
|
|
|
|
# Phase 4 — light refactors batch B (notifications, KPI source tag).
|
|
from . import fp_notification_trigger
|
|
from . import fusion_plating_kpi_value
|
|
|
|
# Phase 5 — Job Margin report.
|
|
from . import report_fp_job_margin
|
|
|
|
# Phase 1 of MRP cut-out (Sub 11) — relocated from fusion_plating_bridge_mrp.
|
|
# (fp.qc.checklist.template lives in fusion_plating_quality; can't depend
|
|
# back on jobs without a cycle.)
|
|
from . import fp_job_consumption
|
|
# fp.work.role, fp.operator.proficiency, fp_process_node inherit, and the
|
|
# hr.employee shop-roles inherit live in fusion_plating core so every
|
|
# downstream module (cgp, bridge_mrp residue, etc.) sees them without a
|
|
# transitive dep on jobs.
|