Tuesday, October 6, 2020
5 changes · master
Enhancements to existing features
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
Resolved issues and error corrections
This fix makes event pages more reliable as installable web apps by showing the install prompt more consistently and keeping offline cache storage under control. It also improves support for custom language URLs, helping multilingual event sites work correctly.
Original PR description
This PR aims at preventing the cluttering of the ServiceWorker's cache by filtering out non-necessary assets and preventing "opaque" responses from being cached. Also, it registers earlier the listener for the PWA install event, allowing to properly show the installation's banner in most of the case. Finally, it fixes the optional URL's language parsing by allowing custom language naming.
Helpdesk users who do not have Timesheet access will no longer see the timer start controls. This avoids a frustrating permission error when stopping a timer and keeps time tracking actions available only to users with the right permissions.
Original PR description
Before this commit, a user with "User" group for Helpdesk and no group for Timesheet was able to start timer if option "Timesheet Timer" was enable When he want to stop the timer, he got a permission error saying that he doesn't have permission to create an entry in Timesheet. This fix hide buttons to start a timer. More precisely, this commit check if the user is in groups helpdesk.group_helpdesk_user and hr_timesheet.group_hr_timesheet_user. I haven't found a way to check if user is in both groups with xml so I've created a new field called "display_timer" Task id: 2326300 X-original-commit: 1634025509f4e103aebd7ab6b2c6f3431204c31d
This fix resolves an issue that prevented users from creating bank statements when the Mexican electronic invoicing module was installed. It helps accounting teams continue normal bank reconciliation and statement entry without disruption.
Original PR description
Task ID: 2350513