Monday, May 12, 2025
3 changes · saas-18.3
Resolved issues and error corrections
The VoIP call screen no longer shows a transfer button for a feature that is not yet available. This prevents users from clicking an action that would not work and reduces confusion during calls.
Original PR description
The feature is not implemented yet. Don't show buttons that aren't mapped to anything.
This fix restores required planning information on the sales order form so the planned hours button can open correctly. Users can now confirm quotations and access related planning details without encountering an error.
Original PR description
Before this commit, due to a cleaning of sale order views, the `planning_first_sale_line_id` and `planning_initial_date` has been removed from the sale order form view but those fields have to be…
Before this commit, due to a cleaning of sale order views, the `planning_first_sale_line_id` and `planning_initial_date` has been removed from the sale order form view but those fields have to be loaded in the form view to be used as default values when the user clicks on `Planned\n x Hours` stat button, otherwise a traceback will be occurred. This commit introduces again those fields in the sale order form view to be sure those fields are defined and used as default value for the `Planned\n x Hours` stat button. Steps to reproduce ------------------ 0. Install sale_planning module 1. Go to Sales app 2. Create a quotation with a product in which slots will be generated 3. Confirm the quotation 4. Click on `Planned\n x Hours` stat button Current behavior ---------------- A traceback is occurred because `planning_first_sale_line_id` and `planning_initial_date` fields are not defined in the form view. Expected behavior ----------------- The action of the stat button should be executed without any issue. task-4781696
The Documents app now updates the favorite icon as soon as a user marks or unmarks a document. This removes a confusing delay where the action seemed not to work, making document organization feel more reliable.
Original PR description
Steps to reproduce: 1. Go to documents 2. Try to mark your favourite document 3. It will ghost you. Technical Reason: Used record.load() as value was not updating instantly in the UI. 'this.props.record.data[this.props.name] = result' fetched correct value, but didn’t trigger re-render. After this commit: favorite icon state updates instantly. Task-4766725