Daily updates from Odoo
Navigate
Branch
Monday, October 29, 2018
7 changes
Enhancements to existing features
This update reorganizes the campaign tracking and marketing link tools to make them easier to maintain and use. It also improves related views and navigation in mass mailing, helping users access link statistics and campaign information more clearly.
Original PR description
Purpose of this merge is to clean a bit link_tracker and utm as well as their
use in mass mailing. Main things done in this merge are
* reorganize link_tracker and utm according to guidelines. Purpose is
to ease code understanding and prepare future improvements in those
modules;
* clean views, add missing fields in views;
* better integration of link menus and views in mass mailing;
This commit is related to task ID 1896681.Leave types now have stable codes that can be used in payroll salary rules, instead of relying on translated leave names. This helps prevent payroll rule issues when users switch languages or rename leave types.
Original PR description
Before this commit, it was not straightforward to use leave records in salary rules programatically. This commit implements the standard and python-code compatible way of defining leave codes which…
Before this commit, it was not straightforward to use leave records in salary rules programatically. This commit implements the standard and python-code compatible way of defining leave codes which then can be used in the salary rules in the used way. This way, the naming of leaves will not be restricted to python-attribute compatible naming, when one wants to use this feature. **Description of the issue/feature this PR addresses:** - Leave names (translatable) are an unreliable identification in python code salary rules **Current behavior before PR:** - A language switch would break python salary rules that use a leave type as input **Desired behavior after PR is merged:** - Leave types can be referenced in python salary rules in a stable way. **Note:** Please do not close, even if not immediately accepted (`wishlist` tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
Leave types can now have stable codes that payroll rules can use instead of relying on translated leave names. This makes salary calculations more reliable across different languages and allows leave names to remain flexible without breaking payroll logic.
Original PR description
Purpose ======= Before this commit, it was not straightforward to use leave records in salary rules programatically. This commit implements the standard and python-code compatible way of defining leave codes which then can be used in the salary rules in the used way. This way, the naming of leaves will not be restricted to python-attribute compatible naming, when one wants to use this feature. Leave names (translatable) are an unreliable identification in python code salary rules. A language switch would break python salary rules that use a leave type as input 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
Payroll calculations and contract lookup logic were reorganized to use more efficient internal data handling. This should improve performance and maintainability without changing the day-to-day payroll workflow for users.
Original PR description
Purpose ======= Some parts of the code are quite old-api-style and could be modified to use recordsets and thus improve performances.
Resolved issues and error corrections
This fixes a setup issue that could cause the weekly digest email process to crash in a new database when accounting was installed. The digest feature now has the dependency it needs, so scheduled digest emails can run reliably.
Original PR description
Steps:
- Create DB without demo data
- Install account
- Enable debug
- Go to Technical, Email, Digest emails
- Open Weekly Digest, set Next Send Date to today
- Go to Scheduled Actions, open Digest Emails
- Click Run Manually
Get
```
digest/models/digest.py", line 161, in _compute_timeframes
tz_name = company.resource_calendar_id.tz
AttributeError: 'res.company' object has no attribute 'resource_calendar_id'
```
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCode cleanup and technical improvements
This change reorganizes styling variables so they follow Odoo’s standard asset structure. It should not change day-to-day behavior, but it helps keep the Accounting and HR Org Chart areas easier to maintain and less prone to future styling issues.
Original PR description
Some variables were placed at the beginning of the backend helper. While it was working, the normal convention is to place them at the end of the variables helper.
Marketing Automation now uses the correct asset bundles for its styling and interface resources. This internal cleanup helps keep the module aligned with the platform’s asset structure and reduces the risk of loading or maintenance issues.
Original PR description
See https://github.com/odoo/odoo/pull/28203