Tuesday, September 5, 2023
3 changes · master
New functionality added to Odoo
Odoo now lets businesses attach product documents to product templates or variants and show them on quotations, confirmed sales orders, and e-commerce product pages. This replaces the older digital files feature with a more unified document setup, though the prior option to release files only after invoice payment is removed.
Original PR description
Introduce new model of "Product Documents" to hold documents linked to a given product template/variant, displayed on: * quotations * confirmed sale orders * e-commerce product page This will also replace the previous "Digital Files" (website_sale_digital) logic & module, which allowed to specify product documents available to customers after the SO invoice was paid. This exact feature will be lost after upgrade, since we only keep the choice to link documents on quotations/orders, but: 1) on e-commerce, carts are supposed paid when confirmed 2) on portal, the "Online Payment" settings makes sure the users have to pay to confirm their quotation. therefore we consider new configuration sufficient, without needing a "paid order" choice as well. task-3249201 See also: * https://github.com/odoo/enterprise/pull/46106 * https://github.com/odoo/upgrade/pull/5069
Odoo now supports Italy's Split Payment rules for invoices involving public administration customers, automatically applying the correct VAT treatment and required legal invoice note. This helps Italian businesses issue compliant electronic invoices and reduces manual tax setup when billing eligible public entities.
Original PR description
Split Payment originally from: odoo/#117989 depends on: odoo/#122194 When an italian company bills a PA business (for example they're selling cleaning services for a public building) the PA business…
Split Payment originally from: odoo/#117989 depends on: odoo/#122194 When an italian company bills a PA business (for example they're selling cleaning services for a public building) the PA business will send the VAT to the Tax Agency themselves, while generally the VAT is collected and sent to the Tax Agency by the buyer (the PA business). This is done to avoid VAT fraud as the PA doesn't trust the business will actually pay the VAT, that's very common in Italy. - Split Payment account.taxes are Groups of Taxes with l10n_it_vat_due_date == 'S'. - The Group of Taxes includes normal VAT and a reversed VAT entry (both for sale and purchase) - New tax groups have been added to build the correct totals in the move form view - _l10n_it_get_tax_kind returns the new split_payment tax kind - account.taxes and account.fiscal.position has been added to change from VAT to VAT Split Payment automatically when you select a res.partner that features the fiscal position. - The Fiscal Position also has the law-required note that has to be featured on invoices that use Split Payment - A PA business demo partner is added to showcase the new fiscal position Task link: https://www.odoo.com/web#id=2823645&model=project.task task-2823645
Enhancements to existing features
This update makes Automated Actions more visible from kanban views and easier to configure with clearer screens, smarter trigger choices, and support for multiple actions in one automation. It also simplifies related Server Actions so users see only the fields and options relevant to what they are trying to automate.
Original PR description
This PR makes "Automated Actions" more discoverable and usable by: - Adding a menu in the kanban header config dropdown to add/edit them. - Creating a new custom kanban view for a clear understanding…
This PR makes "Automated Actions" more discoverable and usable by:
- Adding a menu in the kanban header config dropdown to add/edit them.
- Creating a new custom kanban view for a clear understanding of each
automated action record and its associated actions.
- Introducing new "smart" triggers that appear in the form view based on the
chosen model:
- Updated Values category:
- "Stage is set to" when a `stage_id` field exists in the model,
allowing users to select a specific stage value.
- "State is set to" when a `state` field exists in the model,
allowing users to select a specific state value.
- "Priority is set to" (`priority`) where users can select a specific priority.
- "User is set" (`user_id`, `user_ids` fields)
- "Tag is added" (`tag_ids` field) where users can select a specific tag.
- "On Archive"
- "On Unarchive"
- Timing Conditions:
- "After creation"
- "After last update"
- Deprecating previously known triggers "On Creation" (`on_create`) and "On
Update" (`on_write`) to simplify the user experience. "On Creation & Update"
(`on_create_or_write`) is retained and renamed to "On save".
- Changing the `ir.actions.server` Many2one relationship to a One2many
relationship. Automated actions can now directly contain multiple actions,
eliminating the need for an "Execute several actions" action in automation
rules.
- Introducing a widget for the new `ir.actions.server` One2many field for a
clearer understanding of multiple actions.
This commit also enhances the usability of "Server Actions" (`ir.actions`) by:
- Removing the `ir.server.object.lines` model and the associated `fields_lines`
One2Many field. The attributes of the removed model are now merged into
`ir.actions`. An action can now write to only one field, and the create action
is now a name_create action.
- Adapting the form view when creating an "Update the record" action. The value
field shown adapts itself based on the field to update; this field can be a
`reference` field for a `one2many` `update_field_id`, a `one2many` field for a
selection `update_field_id`, or a `text` field otherwise.
- Refactoring the form view to display only relevant details and other
miscellaneous improvements.
Taskid: 3085360
upgrade: https://github.com/odoo/upgrade/pull/4904
enterprise: https://github.com/odoo/enterprise/pull/37782