fix(jobs): workflow state — chatter + field cycle fix + force view reload
Three issues from user testing on entech: 1. RPC error: column fp_step_template.triggers_workflow_state_id does not exist Root cause: the field was declared in fusion_plating CORE, but its target model fp.job.workflow.state lives in fusion_plating_jobs. Odoo loads core BEFORE jobs (jobs depends on core), so when core's field declaration runs, the comodel doesn't exist yet — and Odoo silently skips creating the column. Fix: moved the field to fusion_plating_jobs/models/fp_job.py via _inherit. Now the column is added when jobs loads (after core), and the FK target is resolvable. 2. No chatter on the Workflow State form Added _inherit = ['mail.thread', 'mail.activity.mixin'] to fp.job.workflow.state. Tracking enabled on name/code/sequence so admins see who changed the milestone vocabulary. <chatter/> widget added to the form view. 3. Form layout still showed cramped 2-col help text The XML file on disk had my new alert-info card, but Odoo's DB ir_ui_view still held the old arch. The -u didn't refresh it (likely because the file's mtime didn't change between deploys). Fix: bump version + the next deploy will run a SQL DELETE on the ir_ui_view record so Odoo recreates it from XML on -u. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -105,6 +105,9 @@
|
||||
<field name="description" nolabel="1"
|
||||
placeholder="What this milestone represents and when it should fire..."/>
|
||||
</sheet>
|
||||
<!-- Chatter — adds activity log + message thread + followers
|
||||
so admins can audit who changed which trigger and when. -->
|
||||
<chatter/>
|
||||
</form>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
Reference in New Issue
Block a user