Thursday, December 14, 2023
3 changes · master
Resolved issues and error corrections
This change makes an automated business flow test wait for product details to fully update before continuing. It helps prevent false test failures and improves confidence that core product selection workflows remain reliable.
Original PR description
Before this commit, since changes made in odoo/odoo#131680, the step checking the name field correctly contains the name of the product selected in the `data-tooltip` has been replaced by a step checking the same tooltip but on `product_id` or `product_template_id` field because the tooltip data attribute has been removed on text field. Because of that changes, we no longer wait the onchange execution since the tooltip in `product_id` or `product_template_id` field is directly filled in when the user selects the product, compared to the one in the name field which is filled in when the oncahnge rpc is done. This commit adds an extra step to wait the execution of the onchange when it is needed. To do that, the step will check the `product_uom_id` field is correctly set. By doing that, we can be sure the next steps will be correctly executed and will not be altered when the Framework JS will get the result of the onchange to reload its components. runbot-52609
Resume line type names in the Skills app can now be shown in the user's language instead of always appearing in English. This improves localization for employees and HR teams using Odoo in non-English languages.
Original PR description
Without the translate=True, the names of these types cannot be translated so they will always appear in English regardless of the user's language. Because translation of Char fields requires a db change, we only add this fix into master. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Planning app no longer crashes when opened in a database without demo data. This ensures users can access scheduling features even when no working interval information is available yet.
Original PR description
Steps to reproduce: ------------------- - install planning without demo data - try to open planning module Issue: ------ When trying to open the planning module, a traceback occurs. Cause: ------ The issue arises when attempting to get a row from workIntervals, even when it is undefined. Solution: --------- Ensure workIntervals is available before attempting to retrieve rows from it.