32c7026558
The owner only saw the AI summary, which was a paraphrase of the user
report — they couldn't see the actual request OR what we said back.
Restructure the engagement email into three sections so the owner can
read the conversation and not just the AI's take:
1. Original Request (from the reporter) — ticket.description, no
longer buried in a <details> collapsible at the bottom
2. Our Reply — the wizard's "Your Findings" text, now persisted on
the ticket so the email template can render it directly. This is
the engineer's analysis / response to the request.
3. Summary for the Decision — the AI-generated brief
Approve / Reject buttons stay below all three. Bulk email mirrors the
same per-card structure.
New ticket field x_fc_engagement_findings (Text, copy=False) stores
the findings at send-time so they survive as audit history. Wizard's
_action_send_single / _action_send_bulk pass findings into
_fc_reset_engagement; bulk uses per-line findings + per-line summary.
Mail templates are in <data noupdate="1"> so a plain -u doesn't
re-import them. Pre-migration in migrations/19.0.2.4.0/pre-migration.py
deletes the existing template records + ir_model_data so the upgrade's
data load re-creates them with the new body_html. Pre- (not post-)
because data load happens between the two phases.
Smoke-tested live on nexa: rendered template HTML contains all three
section headers at the expected positions with their expected content
markers (ORIGINAL FROM RIYA in Original Request, REPLY-FROM-GURPREET
in Our Reply, the summary text in Summary for the Decision).
Bumps fusion_helpdesk_central to 19.0.2.4.0.
46 lines
1.7 KiB
Python
46 lines
1.7 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1
|
|
{
|
|
'name': 'Fusion Helpdesk Central — Client API Keys',
|
|
'version': '19.0.2.4.0',
|
|
'category': 'Productivity',
|
|
'summary': 'Admin UI on the central Odoo for issuing per-client API '
|
|
'keys used by fusion_helpdesk client deployments.',
|
|
'description': """
|
|
Fusion Helpdesk Central
|
|
=======================
|
|
Companion to `fusion_helpdesk`. Install on the central Odoo (the one
|
|
running the Helpdesk app) to manage **per-client API keys** instead of
|
|
shipping a shared bot password to every client deployment.
|
|
|
|
Each row in *Helpdesk → Configuration → Client API Keys* maps a client
|
|
label (e.g. ENTECH, MOBILITY) to a real `res.users.apikeys` row on the
|
|
shared bot user. The plaintext key is shown ONCE on creation; revoke
|
|
in one click if a deployment is compromised.
|
|
|
|
Depends only on `helpdesk`. No client-side install needed.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'depends': ['helpdesk'],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/ir_config_parameter_data.xml',
|
|
'data/mail_template_ack.xml',
|
|
'data/mail_template_engagement.xml',
|
|
'data/helpdesk_tag_critical.xml',
|
|
'data/ir_cron_engagement_reminder.xml',
|
|
'views/fusion_helpdesk_client_key_views.xml',
|
|
'views/helpdesk_ticket_views.xml',
|
|
'views/engagement_wizard_views.xml',
|
|
'views/engagement_reporting_views.xml',
|
|
'views/portal_templates.xml',
|
|
'views/res_config_settings_views.xml',
|
|
],
|
|
'installable': True,
|
|
'auto_install': False,
|
|
'application': False,
|
|
}
|