summaryrefslogtreecommitdiff
path: root/addons/hr_recruitment/data/digest_data.xml
diff options
context:
space:
mode:
authorOdoo's Mergebot <robodoo@odoo.com>2020-08-12 16:12:33 +0200
committerGitHub <noreply@github.com>2020-08-12 16:12:33 +0200
commit9039183fbbd288800a8bf4166780f9f86cc61b52 (patch)
treed37d462f6f45ccee249d3f5e9db7474f77ba1dbd /addons/hr_recruitment/data/digest_data.xml
parentd9bbf1db4bb88498fe74083a86a0f5a91e863396 (diff)
parent73b5dfd64a8290ef8922cdeff8b1a34a8e9424eb (diff)
[FW][MERGE] digest, various: add or improve digest tips and digest layout
PURPOSE Review the tips and digest layout design to make sure they have a WOW effect and increase trial conversion/retention. SPECIFICATIONS: LAYOUT Besides changing the tips, a cleaning of digest layout was performed. Emails were reported to look not neat in Outlook and somewhat random in mail.com or gmail.com. Most recent HTML CSS cannot be used to make HTML emails because each email provider renders emails its own way. This means a given email may renders differently in gmail.com and outlook. The layout of the email was composed of several levels of embedded tables which means huge maintenance effort. So it was totally rewritten with divs and CSS, but some properties are not taken into account. A lot of page component improvements were done. It consisted in replacing most of the style attribute in tags with CSS classes and ids. This step is especially useful for tip formatting because before, if a style modification was needed, it had to be performed on each tip individually. SPECIFICATIONS: TIPS Add / Improve tips in cmr, purchase, hr_recruitment, website, hr_expense, project, digest, sale_management, im_livechat, stock, mrp, account. LINKS COM PR: odoo/odoo#53580 ENT PR: odoo/enterprise#11394 closes odoo/odoo#55807 Forward-port-of: odoo/odoo#53580 Related: odoo/enterprise#12372 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Diffstat (limited to 'addons/hr_recruitment/data/digest_data.xml')
-rw-r--r--addons/hr_recruitment/data/digest_data.xml19
1 files changed, 11 insertions, 8 deletions
diff --git a/addons/hr_recruitment/data/digest_data.xml b/addons/hr_recruitment/data/digest_data.xml
index 61790aba91c..b8bfcd234ba 100644
--- a/addons/hr_recruitment/data/digest_data.xml
+++ b/addons/hr_recruitment/data/digest_data.xml
@@ -8,16 +8,19 @@
<data>
<record id="digest_tip_hr_recruitment_0" model="digest.tip">
- <field name="name">Recruitment: Create new applicants from incoming emails</field>
- <field name="sequence">4</field>
- <field name="group_id" ref="hr_recruitment.group_hr_recruitment_user"/>
+ <field name="name">Tip: Let candidates apply by email</field>
+ <field name="sequence">1300</field>
+ <field name="group_id" ref="hr_recruitment.group_hr_recruitment_manager" />
<field name="tip_description" type="html">
<div>
- <b class="font-16" style="font-size: 20px;line-height: 30px">Create new applicants from incoming emails</b>
- <p class="font-12" style="color:#888888;font-size: 15px; line-height: 25px; margin-top: 0">You just need to set email aliases in your job positions' settings.</p>
- <div style="text-align:center;margin-top:5px;margin-bottom:10px;">
- <a href="/web#action=hr_recruitment.action_hr_job_config" target="_blank" style="display:inline-block;background-color:#875a7b;line-height:40px;text-decoration: none;color: #ffffff;border-radius: 3px;font-size:13px;font-weight:bold;text-align:center; padding:0 10px;">Set Email Aliases</a>
- </div>
+ <p class="tip_title">Tip: Let candidates apply by email</p>
+ <p class="tip_content">
+ By setting an alias to a job position, emails sent to this address create applications automatically. You can even use multiple trackers to get statistics according to the source of the application: LinkedIn, Monster, Indeed, etc.
+ % set record = object.env['hr.job'].search([('alias_name', '!=', False)], limit=1)
+ % if record and record.alias_domain
+ <a href="mailto:${record.alias_id.display_name}" target="_blank" style="color: #875a7b; text-decoration: none;">Try sending an email</a>
+ % endif
+ </p>
</div>
</field>
</record>