Friday, September 1, 2023
5 changes · master
Enhancements to existing features
Studio approval rules are easier to configure and understand, with clearer screens, tooltips, labels, and editable notification messages. Businesses can now notify selected users and control approval sequencing so requests happen in the right order.
Original PR description
This commit improves the approvals feature by adding multiple behaviors. Firstly, the UI of the form and list views corresponding to the approval rules has been revamped and improved with new tooltips, new options and better labels. Those new options are the following: - users_to_notify: list of users to notify by a note in the chatter by mentionning users in the message body. - notification_order: when approvals have a higher notification_order, activities and message to ask for approval is postponed until all approval entries from rules with lower notification order are approved. Secondly, the notification can now display a message that is editable, instead of a generic list of missing approvals. Finally, the Studio sidebar has been updated with the newest additions, that are fully editable. The code has been reworked to use the Record component, as well as fields components. task-3444754
Payroll employee declarations can now be generated and published to employee portals through a shared process that runs in the background. This helps reduce failures from large batches, improves the declaration workflow, and supports Belgian and Swiss payroll document needs more consistently.
Resolved issues and error corrections
Forms now update client-side visibility and requirement rules immediately when users add related records that have not yet been saved. Server-facing filters and defaults continue to ignore those temporary records, reducing the risk of errors while keeping the interface responsive.
Code cleanup and technical improvements
The shop floor manufacturing app now uses one shared data model instead of several separate ones, reducing repeated data loading and making screens more reliable. The update also removes an unused tablet view and fixes demo data and small workflow issues, such as undoing a completed stock move.
Original PR description
Currently the shop floor app is working with 4 differents relationalModel. It's an issue for the following points: - It requires 4 rpc to load the server's data. Now with the unity read, other views only require one for all differents model - Inside the app we have to do the match between x2m objects. We created multiple function to get the sub records base on a lot of array browsing. With the new related key in the params, it could be done automaticaly. - There are reload everywhere in the code and sometimes, they forgot to load a related object (e.g. following a public method) This PR create a single model and clean all the reload. Using only a single one on mrp.display (and propagate it by the env) It also aim to have all the information on the model in a single function. (relation, domain, order) Minor fix on demo data, the operation are activated while the workorders settings has been removed by default
Knowledge macros are now more reliable when interacting with form views, chatter, attachments, and rich-text fields. This reduces stalled or incorrect automation and makes Knowledge actions work across more business records that include editable note or description fields.
Original PR description
Keep only one form controller patch in Knowledge. Refine the way the chatter and html form fields are detected for Knowledge macros: - Instead of updating the `commandsRecordInfo` at every patch if…
Keep only one form controller patch in Knowledge. Refine the way the chatter and html form fields are detected for Knowledge macros: - Instead of updating the `commandsRecordInfo` at every patch if the record's id changed, it can be done as an `onWillUnMount` hook, since we only care about the last visited record of the form view. - Use a `CallbackRecorder` to accurately ask the `Chatter` whether the current user is able to send messages or attach files, instead of relying only on the presence of the chatter in the `xmlDoc`. - Add/Move some functions related to registering/discarding/validating a `commandsRecordInfo` in the `KnowledgeCommandsService` to limit the amount of functions added in the `FormController`. Use action service to restore the form view instead of clicking on the breadcrumbs in the DOM. Breadcrumbs are only checked to ensure that the current view has a breadcrumbs history. This is more robust against future designs of the breadcrumbs (where not every element of the breadcrumbs list is displayed directly as a link (some of them can be hidden in a popper). Add comments to better explain the macro processes and the `KnowledgeCommandsService`. Remove usage of `interval` macro property as it is obsolete since [1]. Add a timeout of 10 seconds for macros, to give back control to the user if a macro is stalled. Knowledge macros rely on the name attribute of a notebook page to switch between tabs in a Form notebook. That attribute is not mandatory, so some views with a valid html_field did not have one. This commit add the name attribute so those fields can now be manipulated by Knowledge macros. [1]: https://github.com/odoo/odoo/commit/3a798039d6f200f8e28448ddb6a2d3c46654a203 task-3410128