mcm-odooandThibault Delavallée
de1743ab12
RATIONALE
Mail template model holds a field telling odoo mail engine to automatically
add the current user's signature to the body. Its use depends on the use
case
* using the template in the composer on a single record: it is displayed
in the rendered template in the composer, meaning people could change it.
This behavior is interesting as it allows to see the email content;
* using the template in the composer in mass mail mode: it is not displayed
as only the raw jinja is displayed. It is therefore not obvious that it
will be appended to the body of the mail. People could add it manually and
have 2 signatures as a result;
A mechanism automatically adding a signature to sent emails when posting a
message is already implemented and is based on template existence. If a
template has been used when posting, no signature is added in sent emails.
Otherwise it is automatically added. This behavior should not change.
Behavior will therefore be
* use a template -> specify signature usage in it manually through jinja;
* do not use a template -> signature added in sent emails;
SPECIFICATIONS
Remove user_signature.
Update template body accordingly. In customer oriented templates that are using
it and do not already contain it, manually add a call to user.signature within
the jinja code. When set to False, just remove its declaration.
Quickly clean some signature integration.
LINKS
Task ID 2089252
Community PR odoo/odoo#39482
Enterprise PR odoo/enterprise#6459
Upgrade PR odoo/upgrate#761
Related: odoo/enterprise#6459
Related: odoo/upgrade#761
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Co-authored-by: Michaël Mattiello <mcm@odoo.com>
Co-authored-by: Thibault Delavallée <tde@odoo.com>
104 lines
4.4 KiB
XML
104 lines
4.4 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<!-- Email templates -->
|
|
<record id="mail_template_data_track_confirmation" model="mail.template">
|
|
<field name="name">Track: Confirmation</field>
|
|
<field name="model_id" ref="website_event_track.model_event_track"/>
|
|
<field name="subject">Confirmation of ${object.name}</field>
|
|
<field name="use_default_to" eval="True"/>
|
|
<field name="body_html" type="xml">
|
|
<div>
|
|
Dear ${object.partner_name or ''}<br/>
|
|
We are pleased to inform you that your proposal ${object.name} has been accepted and confirmed for the event ${object.event_id.name}.
|
|
<br/>
|
|
You will find more details here:
|
|
<div style="margin: 16px 0px 16px 0px;">
|
|
<a href="/event/${object.event_id.id}/track/${object.id}"
|
|
style="padding: 8px 16px 8px 16px; font-size: 14px; color: #FFFFFF; text-decoration: none !important; background-color: #875A7B; border: 0px solid #875A7B; border-radius:3px">
|
|
View Talk
|
|
</a>
|
|
</div>
|
|
<br/><br/>
|
|
Thank you,
|
|
% if user.signature
|
|
<br />
|
|
${user.signature | safe}
|
|
% endif
|
|
</div></field>
|
|
<field name="lang">${object.partner_id.lang}</field>
|
|
<field name="auto_delete" eval="True"/>
|
|
</record>
|
|
|
|
<record id="event_sponsor_type1" model="event.sponsor.type">
|
|
<field name="name">Bronze</field>
|
|
<field name="sequence">3</field>
|
|
</record>
|
|
<record id="event_sponsor_type2" model="event.sponsor.type">
|
|
<field name="name">Silver</field>
|
|
<field name="sequence">2</field>
|
|
</record>
|
|
<record id="event_sponsor_type3" model="event.sponsor.type">
|
|
<field name="name">Gold</field>
|
|
<field name="sequence">1</field>
|
|
</record>
|
|
|
|
<record id="event_track_stage0" model="event.track.stage">
|
|
<field name="name">Proposal</field>
|
|
<field name="sequence">1</field>
|
|
<field name="color">1</field>
|
|
</record>
|
|
<record id="event_track_stage1" model="event.track.stage">
|
|
<field name="name">Confirmed</field>
|
|
<field name="sequence">2</field>
|
|
<field name="mail_template_id" ref="mail_template_data_track_confirmation"/>
|
|
<field name="color">2</field>
|
|
</record>
|
|
<record id="event_track_stage2" model="event.track.stage">
|
|
<field name="name">Announced</field>
|
|
<field name="sequence">3</field>
|
|
<field name="color">3</field>
|
|
</record>
|
|
<record id="event_track_stage3" model="event.track.stage">
|
|
<field name="name">Published</field>
|
|
<field name="sequence">4</field>
|
|
<field name="is_done" eval="True"/>
|
|
</record>
|
|
<record id="event_track_stage4" model="event.track.stage">
|
|
<field name="name">Refused</field>
|
|
<field name="sequence">5</field>
|
|
<field name="fold" eval="True"/>
|
|
</record>
|
|
<record id="event_track_stage5" model="event.track.stage">
|
|
<field name="name">Cancelled</field>
|
|
<field name="sequence">6</field>
|
|
<field name="fold" eval="True"/>
|
|
<field name="is_cancel" eval="True"/>
|
|
</record>
|
|
|
|
<!-- Event-related subtypes for new track / Chatter -->
|
|
<record id="mt_event_track" model="mail.message.subtype">
|
|
<field name="name">New Track</field>
|
|
<field name="res_model">event.event</field>
|
|
<field name="description">New Track Created</field>
|
|
<field name="default" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Track subtypes -->
|
|
<record id="mt_track_blocked" model="mail.message.subtype">
|
|
<field name="name">Track Blocked</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track blocked</field>
|
|
</record>
|
|
<record id="mt_track_ready" model="mail.message.subtype">
|
|
<field name="name">Track Ready</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track Ready for Next Stage</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|