Daily updates from Odoo
Monday, June 15, 2020
13 changes
Enhancements to existing features
The signature request screen now shows a contact's email address alongside their name. This helps users quickly confirm whether the selected signer has an email address before sending a document for signature.
Original PR description
Purpose: -Purpose of this commit is to know we have mail address of the contact. Specification: - Add mail address after the name of the contact on list when we send the signature request. Task- 2259539
Resolved issues and error corrections
The CRM interface now shows the list view before the kanban view in the relevant activity menu. This makes records easier to scan in table form first, matching the intended workflow and reducing extra navigation for users.
Original PR description
main changes are in the crm (community) module. I just inverted list and kanban views in order to display the tree view first.
Disabling Snailmail for customer invoices now also disables the related follow-up report postal sending feature. This prevents users from seeing a “Send by Post” option that should no longer be available after Snailmail is turned off.
Original PR description
Issue - Install "Accounting" module - Go to Accounting->Settings - Disable "Snailmail" checkbox in "Customer Invoices" section - Go to Accounting->Customer->Follow-up Reports The button "SEND BY POST" is still available. Cause The "Snailmail" checkbox is related to the field "module_snailmail_account", and by disabling it, it will uninstall the module "snailmail_account" and his dependencies. Since "snailmail_account_followup" module depends only on ['snailmail', 'account_followup'], it will not be uninstalled. Solution Replacing 'snailmail' by 'snailmail_account' in dependencies of 'snailmail_account_followup'. opw-2252999
The Timesheet reporting grids by employee and by task now show the Today button and navigation arrows again. This restores quick date navigation, making it easier for users to review timesheet information without manual workarounds.
Original PR description
Purpose: - Purpose of this commit is to display lost 'Today' button and arrows on timesheet by employee and by task grid view. Task- 2267581
Miscellaneous changes
Purpose ======= They are not needed anymore as the property paid_amount returns the wage if there is not work entries (new in 13.0). TaskID: 2256705 Forward-Port-Of: odoo/enterprise#10741 Forward-Port-Of: odoo/enterprise#10735
Original PR description
Purpose ======= They are not needed anymore as the property paid_amount returns the wage if there is not work entries (new in 13.0). TaskID: 2256705 Forward-Port-Of: odoo/enterprise#10741 Forward-Port-Of: odoo/enterprise#10735
- added selection for invoice type - created Consumidor Final partner for end customer - update tags for end customer - added NTI for exempt tax - added xml encoding - update of l10n_co module needed for Bienes Cubiertos tax group Task: https://www.odoo.com/web#id=2204998&action=327&model=project.task&view_type=form&cids=2&menu_id=4720 Forward-Port-Of: odoo/enterprise#11117
Original PR description
- added selection for invoice type - created Consumidor Final partner for end customer - update tags for end customer - added NTI for exempt tax - added xml encoding - update of l10n_co module needed for Bienes Cubiertos tax group Task: https://www.odoo.com/web#id=2204998&action=327&model=project.task&view_type=form&cids=2&menu_id=4720 Forward-Port-Of: odoo/enterprise#11117
### Issue - Stock, enable Studio - Reports - Click on ZPL reports Infinite loading ### Cause Studio do not support this type of report ### Solution Do not display them in studio I made a list so that we can add other type easily if needed **OPW-2271761** Forward-Port-Of: odoo/enterprise#11116
Original PR description
### Issue - Stock, enable Studio - Reports - Click on ZPL reports Infinite loading ### Cause Studio do not support this type of report ### Solution Do not display them in studio I made a list so that we can add other type easily if needed **OPW-2271761** Forward-Port-Of: odoo/enterprise#11116
This commit is a fine tuning of 82a281483771fb1d1bfacb. It fixes: - The CSS change "pre-wrap" which was applied to all sign_item - The difference between the textarea font-size in the sign session and the preview (it caused wrong line wrapping) OPW-2274648 OPW-2274225 Forward-Port-Of: odoo/enterprise#11113
Original PR description
This commit is a fine tuning of 82a281483771fb1d1bfacb. It fixes: - The CSS change "pre-wrap" which was applied to all sign_item - The difference between the textarea font-size in the sign session and the preview (it caused wrong line wrapping) OPW-2274648 OPW-2274225 Forward-Port-Of: odoo/enterprise#11113
The method _compute_display_time_buttons do not return any value anymore Use the value set on the record. Use of write is not a good practice in compute method Forward-Port-Of: odoo/enterprise#11092
Original PR description
The method _compute_display_time_buttons do not return any value anymore Use the value set on the record. Use of write is not a good practice in compute method Forward-Port-Of: odoo/enterprise#11092
Before this PR, it was throwing error from the payment portal, when try to load planning in the portal with debug=assets the payment portal is adding payment option in jquery object, but then from the planning it loads the common assets again. hance, jquery will also be loaded again and it will not find jquery.payment from the payment portal as payment portal will be loaded on dom ready after this PR, load the assets properly to make it work without any traceback Task: https://w
Original PR description
Before this PR, it was throwing error from the payment portal, when try to load planning in the portal with debug=assets the payment portal is adding payment option in jquery object, but then from the planning it loads the common assets again. hance, jquery will also be loaded again and it will not find jquery.payment from the payment portal as payment portal will be loaded on dom ready after this PR, load the assets properly to make it work without any traceback Task: https://www.odoo.com/web#id=2233896&action=327&model=project.task&view_type=form&cids=2&menu_id=4720 Pad: https://pad.odoo.com/p/r.9b757aec3865caa54e3b22a0f55cada7 Forward-Port-Of: odoo/enterprise#11006 Forward-Port-Of: odoo/enterprise#10971
Moduel l10n_se_reports: Removing comment from XML output. Added author and website. Forward-Port-Of: odoo/enterprise#11009
Original PR description
Moduel l10n_se_reports: Removing comment from XML output. Added author and website. Forward-Port-Of: odoo/enterprise#11009
Forward-Port-Of: odoo/enterprise#11143
Original PR description
Forward-Port-Of: odoo/enterprise#11143
Before this commit, modifying the attributes of a field that appears multiple times in a single view may not work. Whether or not it would work depended on whether it was the first element of the view or not. E.g.: If clicking on the second occurrence of the view and changing the name, the change would be applied to the first occurrence instead. This happens because the client sends the server the minimum amount of information possible whenever handling a field in studio, if the fie
Original PR description
Before this commit, modifying the attributes of a field that appears multiple times in a single view may not work. Whether or not it would work depended on whether it was the first element of the…
Before this commit, modifying the attributes of a field that appears
multiple times in a single view may not work.
Whether or not it would work depended on whether it was the first
element of the view or not.
E.g.: If clicking on the second occurrence of the view and changing the
name, the change would be applied to the first occurrence instead.
This happens because the client sends the server the minimum amount of
information possible whenever handling a field in studio, if the field
has an identifying attribute (such as name) we just send the tag and
the attribute and the server will have to "make do" with just that
information (relative xpath), if the target node does not have
identifying attributes then it will send an `xpath_info` object with
which the server can build an absolute xpath.
With this commit, changing the attributes of any field with multiple
occurrences within a view, whether they're first, last or in the middle,
modifies the attributes of the correct node and not the ones of the
first.
This is achieved by a modification in the client and in the server:
- The client will *always* send `xpath_info` to the server
- The server will *always* use the absolute xpath first and will
only use relative ones if there's no other choice
Basing view modifications on absolute xpaths as much as possible
guarantees that the target element is most likely the correct one
whether there's a single one or a hundred with the same attributes.
Task: 2227691
Forward-Port-Of: odoo/enterprise#11049
Forward-Port-Of: odoo/enterprise#10767