Friday, September 27, 2024
4 changes · saas-17.4
Resolved issues and error corrections
Message subjects in the chatter are now visually separated from the message body when they differ from the current record name. This makes older messages easier to read and reduces confusion between the subject and the actual message content.
Original PR description
Before this commit, when a message has a subject different from chatter name e.g. by renaming the record while some messages have been posted prior to rename, the subject was visible in prefix of message text content. The showing of subject is good, but currently the style is almost the same as the text content, and this is put inline before the text content, so the subject looks like actual text content. This commit improves the style so the subject is clearly different from the text content of the message, when the subject is displayed on UI. Before <img width="999" alt="Screenshot 2024-09-27 at 13 39 23" src="https://github.com/user-attachments/assets/d8a299b6-6c3c-4605-aa36-6f6d8286fdbc"> After <img width="747" alt="Screenshot 2024-09-27 at 13 33 20" src="https://github.com/user-attachments/assets/a3919213-ba08-4662-8079-894183c68536">
Product cards will no longer show a generic placeholder image when no product image has been uploaded. This keeps product lists cleaner and avoids drawing attention to missing images.
Original PR description
Previously done in commit 683deecb51e240c5cbf1fd369e0eeefb0267530d but reverted in the refactor done in commit 0279c53930735b65e9342ca66fbb62ff61ac65f6 Objective: hide placeholder images if no image is provided on product --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Field Service guided tour now properly highlights and explains the customer selection field. This helps users follow onboarding instructions without seeing a blank or misplaced tooltip.
Original PR description
Before this PR: - The tour step for customer selection was skipped because the parent step triggered by `.o_field_widget[name=partner_id]` did not include a `run` action. - As a result, the child step executed, showing an empty tooltip with incorrect positioning since it was missing both `content` and `position`. - So, the customer selection step was not properly highlighted or explained. After this PR: - Added `content` and `position` attributes to the child step triggered by `.o_field_widget[name="partner_id"] input`, ensuring the tooltip appears with the correct message and placement. - The step now properly displays the tooltip when the customer selection field is focused. task-4159812
This fix ensures inter-company settings show the right warehouse and receipt options for the current company’s selected transaction flow. It helps businesses avoid incorrect purchase or sales order setup when companies trade with each other.
Original PR description
The meaning of inter-company transaction options (i.e. generate Purchase Order / Sale Order) changed in #55350, as they now indicate the opposite of what they used to (as they now take the PoV of the current company). But the conditions of warehouse/receipt type options weren't adapted to the new meaning: - `intercompany_receipt_type_id` is used to generate the purchase order triggered through `intercompany_generate_purchase_orders`. - `intercompany_warehouse_id` is used to know from which warehouse to generate the sale order triggered trhough `intercompany_generate_sale_orders`. Task-4206898