Tuesday, October 6, 2020
5 changes · master
Enhancements to existing features
Automatically generated mailing and campaign source names are now easier to understand and kept unique when duplicates occur. Demo marketing data was also adjusted to avoid unnecessary translation entries, reducing clutter for administrators.
Original PR description
* Simpler and more user friendly generated source name * Avoid duplicate source name in the DB * Add name in mailing.mailing demo data to avoid creating unnecessary i18n lines task id : 2245823
When users test a newly configured outgoing mail server successfully, Odoo now shows a green success notification instead of an orange warning-style message. This makes the result easier to understand and reduces confusion during email setup.
Original PR description
Previously --------------- When user successfully configured outgoing mail server and test connection, system display title and message with 'warning' type in orange box. Now -------- Title is removed and message is updated with 'success' type, will be displayed in green box. Task Id : 2321763
The website editor now shows a clearer confirmation message when a page reload is needed. This helps users better understand what action is required and reduces confusion while editing website content.
Original PR description
PURPOSE The message saying that we need to reload the page isn't clear... SPECIFICATION Before: https://tinyurl.com/y9bkg5pz After: https://tinyurl.com/y9jwmnal task-2349785 Closes https://github.com/odoo/odoo/pull/59115 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Businesses can now use rich text formatting for terms and conditions shown on invoices, sales documents, and website checkout pages. This makes legal and commercial terms easier to read and present consistently across customer-facing documents and portals.
Original PR description
Before this commit, the terms and conditions could not be html formatted text.
taskid: 2304199Payroll managers can now export the key details of an incorrect payslip into a reusable test file, making it easier for support and developers to reproduce payroll problems. Sensitive employee information is anonymized during export, helping protect privacy while speeding up issue resolution.
Original PR description
When the payroll is incorrect, the feedback that we receive is generally: "this doesn't work". This commit add a route in the controller of hr_payroll, to export in a python file, all data useful to reproduce the exact employee situation about the incorrect payslip. Before testing and fixing the incorrect payslip, we need to anonymize all sensitive data about the employee. This commit converts all sensitive data into demo data. This commit add a button in payslip form view to use the new route to export all data about the incorrect payroll. This button is only displayed when we are in debug mode and the current user is a payroll manager. task-2337786