Daily updates from Odoo
Wednesday, August 10, 2016
5 changes · master
Enhancements to existing features
Delivery slips now include product expiry dates when expiry tracking is enabled. This helps warehouse and customer-facing teams verify time-sensitive goods during deliveries and improves traceability.
Original PR description
Description of the issue/feature this PR addresses: Task :https://www.odoo.com/web?#id=27075&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.1c18d01808f49339d45228052b810671 Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Products are no longer automatically marked as available in Point of Sale outside the Point of Sale app. This keeps product setup clearer for businesses using multiple apps while preserving the expected default behavior within Point of Sale.
Original PR description
Description of the issue/feature this PR addresses: - Remove Default value of 'available_in_pos' field Task:https://www.odoo.com/web#id=26777&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad:https://pad.odoo.com/p/r.276b60e834ab43b4c7edfb8ca4a78ca7 Current behavior before PR: - By default 'available_in_pos' field is true in pos and other apps. Desired behavior after PR is merged: - By default 'available_in_pos' field is true in pos and in other apps its false. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update clarifies that customer satisfaction ratings apply to project tasks by renaming related settings and labels. It also stops issue rating from being enabled automatically when task rating is installed, giving businesses more control over which feedback options they use.
Original PR description
Description of the issue/feature this PR addresses: <strong>Task: </strong> https://www.odoo.com/web#id=27242&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 <strong>Pad:…
Description of the issue/feature this PR addresses: <strong>Task: </strong> https://www.odoo.com/web#id=27242&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 <strong>Pad: </strong> https://pad.odoo.com/p/r.b76e02e6d65cf293c5478936479e3435 Current behavior before PR: we have two options for rating issues. In project management, when we select "Allow customer ratings on tasks or issues" then it will apply rating for task and issue both. Desired behavior after PR is merged: "Allow customer ratings on tasks or issues" string changed into "Track customer satisfaction on tasks". rating_project_issue shouldn't be automatically installed when installing rating_project (remove the auto install). ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr …nged into 'Track customer satisfaction on tasks'. ``` and also change the string of 'Rating' to 'Rating on task'. ``` - Issue rating shouldn't be automatically installed when installing project_rating (remove the auto install).
Resolved issues and error corrections
This fix ensures reports receive the correct selected records when generating HTML output, preventing reports from using the wrong document IDs. It improves reliability for several accounting, payroll, manufacturing, point of sale, product, and HR reports, especially when users print reports from standard actions or wizards.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at…
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
##
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
In the 'get_html' method, the report is using a custom model to render its html,
we should use its own 'render_html' method to generate the report. During the
module migration, we replaced
'report_model.render_html(cr, uid, ids, data=data, context=context)'
by
'report_model.render_html(data=data)'
As get_html has become an api.model method, the docids are not passed anymore, and
the call to render_html should be replaced by
```
if report_model is not None:
return report_model.render_html(docids, data=data)
```
As render_html is an api.multi method, this is all wrong too, because we'll send a
browse record with the custom report model to the render_html method, to use the
ids with 'self.ids' that are absolutely not corresponding to the report model but to
to the record model we want to print (an invoice for example).
In old API style we were sending a list of ids, but it's not correct to keep the same
behavior by sending a browse record with only the ids relevant. We have also to
change render_html method decorator to @api.model with a new signature
```
@api.model
def render_html(self, docids, data=None):
```
In the case the report is printed from a wizard, this is sufficient because the ids
are taken from the active_ids in context, or in data.
In the case the report is printed from a simple action, we should replace the occurence
of 'self.ids' (which doesn't mean anything) to 'docids'
This fix doesn't solve the printing issues for the custom accounting reports, because
the method get_pdf has been reimplemented in the module account_reports.Code cleanup and technical improvements
The Sales module has been reorganized and migrated to Odoo's newer application structure, covering models, views, reports, demo data, and configuration screens. This primarily improves maintainability and consistency for future enhancements, with limited direct day-to-day impact for business users.
Original PR description
Task: https://www.odoo.com/web?#id=24266&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720