fe98fadf61
Sending an engagement triggered template.send_mail(), which logged the outbound email to the chatter as a `notification` message with the internal `Note` subtype. That's correct for nexa-side bookkeeping (we don't want the raw email body propagating to the customer), but it meant nothing public was posted — so the entech-side My Tickets inbox showed no activity. The employee couldn't tell their request had been escalated for approval. _fc_reset_engagement now posts a follow-up public message via message_post (subtype mail.mt_comment, message_type='comment') with: ⏳ Awaiting owner approval from <owner_name>. Their decision will appear here when they reply. Our reply: > <findings text> This survives the entech _public_messages filter (comment + non-internal subtype) and propagates to the employee's My Tickets thread, giving them context AND the engineer's reply without exposing the raw outbound email or the owner's email address. Smoke-tested live on ticket #54: re-engaged with the same owner, the new mail.message (id=348213) is subtype=Discussions / internal=False / message_type=comment, and contains both the awaiting-approval notice and the findings text. _public_messages would surface it. Bumps fusion_helpdesk_central to 19.0.2.4.1.
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.1',
|
|
'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,
|
|
}
|