34a65f9c4a
Previous engagement notice used <blockquote> to style the findings quote. Odoo's mail.thread renderer auto-tags every <blockquote> with data-o-mail-quote-node="1" and the chatter UI then HIDES the content behind a "..." widget — exactly the wrong UX since the findings are the load-bearing content, not throwaway quoted text. Swapped both quote blocks for styled <div>s with the same visual treatment (left border, light background, padding) so they render fully inline with no toggle. Also expanded the notice to mirror more of what the owner sees in the engagement email: now includes BOTH "Our reply" (the findings) and "Summary sent to the owner" (the AI summary). The employee can see the full context being used for the decision, not just the engineer's reply. Skipped the Original Request section because the employee wrote it themselves — would just clutter the thread. white-space:pre-wrap preserves multi-line findings/summaries that the engineer typed with line breaks. The two sections are visually distinct: findings in light blue (matching the email's "Our Reply" treatment), summary in light grey (matching "Summary for the Decision" in the email). Verified live on ticket #54: new message body has no <blockquote>, no data-o-mail-quote attribute, and contains both section headers with their content rendered inline. Bumps fusion_helpdesk_central to 19.0.2.4.2.
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.2',
|
|
'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,
|
|
}
|