[IMP] core: make author field mandatory in manifests

External contributors (and namely Odoo PS) forget to set the author field in their manifest file. The result is that the module is wrongly registered with `'author': 'Odoo S.A.'`. This work makes the field mandatory, with a warning when not set. It also offers an upgrade-code script to mass-rewrite all the manifests in order to set the author. task-4485983
[MOV] accounting: invoice sequence section on a separate page
2025-02-23 13:42:59 +01:00 · 2025-02-22 06:15:03 +00:00 · 2025-02-22 06:14:58 +00:00 · 2025-02-21 18:05:14 +00:00 · 2025-02-21 16:38:11 +00:00 · 2025-02-21 16:38:04 +00:00
290 changed files with 11654 additions and 8096 deletions
@@ -23,7 +23,7 @@ Edit Security Settings --> Delete Account`. It can also be accessed by going to
 Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting
 confirmation for the account deletion.

-.. image:: odoo_account/delete-account.png
+.. image:: odoo_accounts/delete-account.png
   :align: center
   :alt: Clicking on the Delete Account button will populate a window verifying the change.

@@ -21,25 +21,23 @@ Import transactions

 Odoo supports multiple file formats to import transactions:

- SEPA recommended Cash Management format (CAMT.053);
- Comma-separated values (.CSV);
- Open Financial Exchange (.OFX);
- Quicken Interchange Format (.QIF);
- Belgium: Coded Statement of Account (.CODA).
+- SEPA recommended Cash Management format (CAMT.053)
+- Comma-separated values (CSV)
+- Open Financial Exchange (OFX)
+- Quicken Interchange Format (QIF)
+- Belgium: Coded Statement of Account (CODA)

-To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
+To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
 click on :guilabel:`Import File`.

 .. tip::
   Alternatively, you can also:

-   - click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;
-   - or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and
-     selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select
-     :guilabel:`Import records`.
-
-     .. image:: transactions/import-transactions.png
-        :alt: Import bank transactions from the bank journal
+   - click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon on the :guilabel:`Bank`
+     journal and select :guilabel:`Import file`;
+   - or access the transaction list by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)`
+     icon on the :guilabel:`Bank` journal and selecting :guilabel:`Transactions`, then click
+     the :icon:`fa-cog` :guilabel:`(gear)` icon and select :guilabel:`Import records`.

 Next, select the file and upload it.

@@ -75,22 +73,28 @@ on your business flow, you may want to record them for control purposes.
   account balance as of the date you begin synchronizing or importing transactions. This is
   necessary to ensure the accuracy of your accounting.

-To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical
-ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on
-:guilabel:`Statements`
+To access a list of existing statements, go to the :guilabel:`Accounting Dashboard`, click the
+:icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon next to the bank or cash journal you want to
+check, then click :guilabel:`Statements`.
+
+.. _transactions/statement-kanban:

 Statement creation from the kanban view
 ---------------------------------------

-Open the bank reconciliation view by clicking on the name of the bank journal, and identify the
-transaction corresponding to the last transaction of your bank statement. Click on the
-:guilabel:`STATEMENT` button when hovering on the upper separator line.
+Open the bank reconciliation (kanban) view from the :guilabel:`Accounting Dashboard` by clicking on
+the name of the bank journal and identify the transaction corresponding to the last (most recent)
+transaction of your bank statement. Click on the :guilabel:`Statement` button when hovering on the
+upper separator line to create a statement from that transaction down to the oldest transaction that
+is not yet part of a statement.

 .. image:: transactions/statements-kanban.png
-   :alt: A "STATEMENT" button is visible when hovering on the line separating two transactions.
+   :alt: A "Statement" button is visible when hovering on the line separating two transactions.

-Fill out the statement's details and save. The newly created statement includes the previous
-transactions following the last statement.
+In the :guilabel:`Create Statement` window, fill out the statement's :guilabel:`Reference`, verify
+its :guilabel:`Starting Balance` and :guilabel:`Ending Balance`, and click :guilabel:`Save`.
+
+.. _transactions/statement-list:

 Statement creation from the list view
 -------------------------------------
@@ -100,3 +104,35 @@ view. Select all the transactions corresponding to the bank statement, and, in t
 :guilabel:`Statement` column, select an existing statement or create a new one by typing its
 reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and
 saving.
+
+.. _transactions/view-edit-print:
+
+Statement viewing, editing, and printing
+----------------------------------------
+
+To view an existing statement, click on the statement amount in the reconciliation (kanban) view or
+click on the statement name in the bank transaction list view. From here, you can edit the
+:guilabel:`Reference`, :guilabel:`Starting Balance`, or :guilabel:`Ending Balance`.
+
+.. note::
+   Manually updating the :guilabel:`Starting Balance` automatically updates the :guilabel:`Ending
+   Balance` based on the new value of the :guilabel:`Starting Balance` and the value of the
+   statement's transactions.
+
+.. warning::
+   If the :guilabel:`Starting Balance` doesn't equal the previous statement's :guilabel:`Ending
+   Balance`, or if the :guilabel:`Ending Balance` doesn't equal the running balance
+   (:guilabel:`Starting Balance` plus the statement's transactions), a warning appears explaining
+   the issue. To maintain flexibility, it is still possible to save without first resolving the
+   issue.
+
+To attach a digital copy (i.e., JPEG, PNG, or PDF) of the bank statement for enhanced recordkeeping,
+click the :icon:`fa-paperclip` :guilabel:`Attachments` button and select the file to attach.
+
+To generate and print a PDF of the bank statement, click the :guilabel:`Print` button (if accessed
+via the reconciliation view) or click on the :icon:`fa-cog`:guilabel:`(gear)` icon and click
+:icon:`fa-print`:guilabel:`Statement` (if accessed via the list view).
+
+.. note::
+   When a bank statement is generated to be printed, it is automatically added to the
+   :guilabel:`Attachments`.
@@ -7,8 +7,7 @@ Customer invoices
 A customer invoice is a document issued by a company for products and/or services sold to a
 customer. It records receivables as they are sent to customers. Customer invoices can include
 amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
-fees, and other charges.
-Odoo supports multiple invoicing and payment workflows.
+fees, and other charges. Odoo supports multiple invoicing and payment workflows.

 .. seealso::
   :doc:`/applications/finance/accounting/customer_invoices/overview`
@@ -84,14 +83,14 @@ Invoice confirmation

 Click :guilabel:`Confirm` when the invoice is completed. The invoice's status changes to
 :guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
-confirmation, Odoo assigns each invoice a unique number from a defined
-:ref:`sequence <accounting/invoice/sequence>`.
+confirmation, Odoo assigns each invoice a unique number from a defined :doc:`sequence
+<customer_invoices/sequence>`.

 .. note::
   - Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
     changes are needed.
-   - If required, invoices and other journal entries can be locked once posted
-     using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
+   - If required, invoices and other journal entries can be locked once posted using the
+     :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.

 .. _accounting/invoice/sending:

@@ -172,81 +171,6 @@ how much the customer is overdue. These actions are bundled into follow-up level
 an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
 same customer, the actions are performed on the most overdue invoice.

-.. _accounting/invoice/sequence:
-
-Sequence
-========
-
-Odoo assigns each document a unique sequence made up of a prefix and a number. The prefix combines
-the journal code and the entry date and groups entries by period. The number is unique for each
-period and is used to identify the entry. The default sequence on customer invoices is
-INV/YYYY/number. In some specific cases, :ref:`resequencing <accounting/invoice/resequencing>`
-invoices might be necessary.
-
-.. _accounting/invoice/resequencing:
-
-Resequencing
------------
-
-Resequencing is not possible:
-
- When entries are before a lock date.
- When the sequence leads to a duplicate.
- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
-  e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
-  of 2024.
-
-To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
-the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
-the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
-example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
-
-In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
-:guilabel:`Validation Error` message appears.
-
-.. note::
-
-   - All sequence changes are logged in the chatter to keep the information.
-   - Sequence changes also affect the format of future invoices' sequences.
-
-.. _accounting/invoice/resequencing-one-invoice:
-
-Resequencing a single invoice
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
-sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
-
-.. _accounting/invoice/mass-resequencing:
-
-Mass-resequencing invoices
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
-another invoicing or accounting system and the reference originates from the previous software,
-continuity for the current year must be maintained without restarting from the beginning.
-
-.. note::
-   This feature is only available to users with administrator or advisor access.
-
-Follow these steps to resequence invoice numbers:
-
-#. Activate the :ref:`developer mode <developer-mode>`.
-#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
-#. Select the invoices that need a new sequence.
-#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
-#. In the :guilabel:`Ordering` field, choose to
-
-   - :guilabel:`Keep current order`: The order of the numbers remains the same.
-   - :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
-#. Set the :guilabel:`First New Sequence`.
-#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
-
-The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
-
-.. image:: customer_invoices/invoice-sequencing.png
-   :alt: Resequence options window
-
 .. _accounting/invoice/reporting:

 Reporting
@@ -270,18 +194,18 @@ go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
 Aged Receivable
 ~~~~~~~~~~~~~~~

-To review outstanding customer invoices and their related due dates, use the
-:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Receivable`.
+To review outstanding customer invoices and their related due dates, use the :ref:`Aged Receivable
+<accounting/reporting/aged-receivable>` report. To access it, go to :menuselection:`Accounting -->
+Reporting --> Aged Receivable`.

 .. _accounting/invoices/aged-payable:

 Aged Payable
 ~~~~~~~~~~~~

-To review outstanding vendor bills and their related due dates, use the
-:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
-:menuselection:`Accounting --> Reporting --> Aged Payable`.
+To review outstanding vendor bills and their related due dates, use the :ref:`Aged Payable
+<accounting/reporting/aged-payable>` report. To access it, go to :menuselection:`Accounting -->
+Reporting --> Aged Payable`.

 .. _accounting/invoices/profit-and-loss:

@@ -311,6 +235,7 @@ liabilities, and equity at a specific time.
   customer_invoices/cash_rounding
   customer_invoices/deferred_revenues
   customer_invoices/electronic_invoicing
+   customer_invoices/sequence
   customer_invoices/snailmail
   customer_invoices/epc_qr_code
   customer_invoices/incoterms
@@ -0,0 +1,66 @@
+================
+Invoice sequence
+================
+
+When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
+the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
+restarts from `00001` each year.
+
+However, it is possible to :ref:`change the sequence format <accounting/invoice/resequencing>` and
+its periodicity, and to :ref:`mass-resequence invoices <accounting/invoice/mass-resequencing>`.
+
+.. note::
+   Changes made to reference numbers are logged in the chatter.
+
+.. _accounting/invoice/resequencing:
+
+Changing the default sequence
+=============================
+
+To customize the default sequence, open the last confirmed invoice, click :guilabel:`Reset to
+Draft`, and edit the invoice's reference number.
+
+.. image:: sequence/reference-number.png
+   :alt: Editing the reference number of an invoice.
+
+Odoo then explains how the detected format will be applied to all future invoices. For example, if
+the current invoice's month is added, the sequence's periodicity will change to every month instead
+of every year.
+
+.. image:: sequence/sequence-dialog.png
+   :alt: Editing the reference number of an invoice.
+
+.. tip::
+   The sequence format can be edited directly when creating the first invoice of a given sequence
+   period.
+
+.. _accounting/invoice/mass-resequencing:
+
+Mass-resequencing invoices
+==========================
+
+It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
+another invoicing or accounting system and the reference originates from the previous software,
+continuity for the current year must be maintained without restarting from the beginning.
+
+.. note::
+   This feature is only available to users with administrator or advisor access.
+
+Follow these steps to resequence invoice numbers:
+
+#. Activate the :ref:`developer mode <developer-mode>`.
+#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
+#. Select the invoices that need a new sequence.
+#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
+#. In the :guilabel:`Ordering` field, choose to
+
+   - :guilabel:`Keep current order`: The order of the numbers remains the same.
+   - :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
+
+#. Set the :guilabel:`First New Sequence`.
+#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
+
+The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
+
+.. image:: sequence/invoice-sequencing.png
+   :alt: Resequence options window
@@ -173,7 +173,8 @@ expression's **label** (ex. **code.label**).
 `CUR` is the currency code in capital letters, and `amount` is the amount of the bound expressed in
 that currency.

-You can also use the `cross_report` subformula to match an expression found in another report.
+`cross_report(xml_id | report_id)`
+   Used to match an expression from another report targeted by the xml_id or the report ID itself.

 'Prefix of Account Codes' engine
 --------------------------------
@@ -705,3 +705,60 @@ Then, to ensure :doc:`Odoo Point of Sale </applications/sales/point_of_sale>` is
 fiscal printer, go to :menuselection:`Point of Sale --> Configuration --> Settings`. In the
 :guilabel:`Connected Devices` section, add the IP address in the :guilabel:`Italian Fiscal Printer
 IP address` and enable :guilabel:`Use HTTPS`.
+
+Ri.Ba. (Ricevuta Bancaria)
+==========================
+
+:abbr:`Ri.Ba. (Ricevuta Bancaria)` is a payment method widely used in Italy where vendors request
+payments through their bank, which forwards the request to the customer's own bank and takes
+responsibility for the collection. This enables payment automation and reduces risks for the vendor.
+
+The vendor generally uploads a fixed-format text file with the list of payments to the bank's web
+portal.
+
+.. note::
+   - Ri.Ba. are exclusively for **domestic payments** in Italy. For recurring international
+     payments, please use `SEPA Direct Debt (SDD) <../accounting/payments/batch_sdd>`_
+
+Configuration
+-------------
+
+#. Check that the `l10n_it_riba` module is :ref:`installed <general/install>`.
+#. Go to :menuselection:`Settings --> Users & Companies --> Companies` and select the company that
+   will use Ri.Ba.
+#. Fill out the required :guilabel:`SIA Code`.
+
+   .. image:: italy/sia-code.png
+      :alt: The company's SIA code
+
+   .. note::
+      The :guilabel:`SIA Code` identifies businesses within the Italian banking network and is used
+      to receive money through specific payment methods. It consists of one letter and four digits
+      (e.g., T1234) and can usually be found on the bank's portal or obtained by contacting the bank.
+
+#. Ensure the Company's bank account has an Italian IBAN.
+
+   .. seealso::
+      How to configure :doc:`Bank Accounts <../accounting/bank>`
+
+Accept Ri.Ba. for your invoices
+-------------------------------
+
+Payments of type :abbr:`Ri.Ba. (Ricevuta Bancaria)` can be registered from the :guilabel:`Invoices`
+(:menuselection:`Accounting --> Customers --> Invoices`).
+
+.. important::
+   Make sure that your invoice involves a Partner that has a bank account with an Italian IBAN.
+
+Then, all Payments must be grouped in a **Batch Payment**.
+
+.. seealso::
+   - :doc:`Batch Payments <../accounting/payments>`
+   - :doc:`Create a Batch Payment <../accounting/payments/batch>`
+
+Once you press the :guilabel:`Validate` button for the Batch Payment, the :abbr:`Ri.Ba. (Ricevuta
+Bancaria)` file is generated and attached to the Batch Payment, so you can download it and upload it
+through your bank's web portal.
+
+.. image:: italy/riba-attachment.png
+   :alt: The Ri.Ba. file attached
@@ -10,6 +10,7 @@ Daily operations

   operations/adjustments
   operations/receipts_deliveries
+   operations/process_transfers
   operations/transfers_scratch
   operations/barcode_nomenclature
   operations/gs1_nomenclature
@@ -0,0 +1,55 @@
+=======================
+Process batch transfers
+=======================
+
+The Odoo **Barcode** app can be used to process *Batch*, *Wave*, and *Cluster* transfers that are
+created in the **Inventory** app.
+
+.. seealso::
+   This document covers the steps to process transfers in the **Barcode** app. Instructions on
+   creating transfers can be found below:
+
+   - :doc:`../../inventory/shipping_receiving/picking_methods/batch`
+   - :doc:`../../inventory/shipping_receiving/picking_methods/wave`
+   - :doc:`../../inventory/shipping_receiving/picking_methods/cluster`
+
+Process the batch
+-----------------
+
+First, navigate to :menuselection:`Barcode app --> Operations` and select an operation type (like
+delivery orders) grouped into batches. From here, select the card for the appropriate batch
+transfer, and click the :guilabel:`BATCH` smart button.
+
+.. image:: process_transfers/batch-transfer.png
+   :alt: The Delivery Orders page.
+
+On the batch transfer screen, the products in the picking are grouped by location, and each line is
+color-coded to associate products in the same picking together.
+
+Then, follow the prompt to :guilabel:`Scan the source location` barcode for the storage location of
+the first product. Scan the barcode for the product and package to process the transfer. To record
+multiple quantities, click the :icon:`fa-pencil` :guilabel:`(edit)` icon, and enter the required
+quantities for the picking.
+
+Repeat this for all products, and click the :guilabel:`Validate` button to mark the transfer as
+:guilabel:`Done`.
+
+.. note::
+   After creating a batch transfer and assigning a package to a picking, Odoo suggests the specified
+   package by displaying the name *in italics* under the product name, ensuring pickers place
+   products into the correct boxes.
+
+   Products from the same order are labeled with the same color on the left. Completed pickings are
+   highlighted in green.
+
+.. example::
+   In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person
+   Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are
+   complete.
+
+   `1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product
+   barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the
+   unique serial number for :ref:`product tracking <inventory/product_management/enable-lots>`.
+
+   .. image:: process_transfers/batch-products.png
+      :alt: Products to be picked in barcode view.
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Julien Castiaux	ec4ce88953	[IMP] core: make author field mandatory in manifests External contributors (and namely Odoo PS) forget to set the author field in their manifest file. The result is that the module is wrongly registered with `'author': 'Odoo S.A.'`. This work makes the field mandatory, with a warning when not set. It also offers an upgrade-code script to mass-rewrite all the manifests in order to set the author. task-4485983	2025-02-23 13:42:59 +01:00
xpl-odoo	e9269e8128	[MOV] accounting: invoice sequence section on a separate page closes odoo/documentation#12142 X-original-commit: `009dd70bd3` Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2025-02-22 06:15:03 +00:00
samueljlieber	b86296750e	[IMP] contributing: documentation macOS make install closes odoo/documentation#12149 X-original-commit: `d4ed263fa2` Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-22 06:14:58 +00:00
jero-odoo	c968e3814a	[IMP] Purchase: Reordering Rules Update closes odoo/documentation#12138 X-original-commit: `035e0ec1e8` Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: Dina Klarisse Dugar <dikd@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2025-02-21 18:05:14 +00:00
LoredanaLrpz	03defbfc60	[IMP] pos: resize & scale content (table and screenshots) task-4521596 closes odoo/documentation#11900 X-original-commit: `989f2faf9a` Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com>	2025-02-21 16:38:11 +00:00
jero-odoo	e55ae1cbf4	[IMP] inventory: view empty locations closes odoo/documentation#12132 X-original-commit: `1262245b53` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com>	2025-02-21 16:38:04 +00:00
Tiffany Chang (tic)	5f9b6e4825	[I18N] *: re-export pot files As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English) closes odoo/documentation#12131 X-original-commit: `aad8aa1314` Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>	2025-02-21 13:39:15 +00:00
dikd-odoo	8c685239b4	[IMP] sales: gelato feedback Apply suggestions from JERO review edits closes odoo/documentation#12123 X-original-commit: `e32f4ec766` Signed-off-by: Zachary Straub (zst) <zst@odoo.com> Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com>	2025-02-21 08:16:00 +00:00
Logan Staelens	224e1f5982	[IMP] account_reports: Unambiguous cross_report aggregations Before this commit, when using cross_report subformula it would search for a report that has an line with this code. We had to ensure there was no duplicate codes and so it was difficult to maintain. Now, when we use a cross_report subformula, we need to explicitly target the report from where the code is from. task-4457667 closes odoo/documentation#11747 Related: odoo/odoo#193106 Related: odoo/enterprise#76845 Signed-off-by: Logan Staelens (lost) <lost@odoo.com>	2025-02-20 18:06:43 +00:00
Charles Mutabazi	606b56ccda	[FIX] Use <chatter> instead of <div class="oe_chatter"> closes odoo/documentation#12110 X-original-commit: `0ae856bcf6` Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>	2025-02-20 01:32:49 +00:00
jero-odoo	c1154c0c5d	[ADD] Purchase: Templates closes odoo/documentation#12103 X-original-commit: `5bb043bd3b` Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: dikd-odoo <dikd@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2025-02-19 08:13:54 +00:00
dikd-odoo	cd3086cea4	[ADD] sales: gelato integration edit image sizes edits Apply suggestions from FEKU review edits Apply suggestions from FEKU review edits Apply suggestions from FEKU review edits Update content/applications/sales/sales/gelato.rst edits Apply suggestions from ZST review edits edits sales file Apply suggestions from SALI review Apply suggestions from SALI review2 images Edits closes odoo/documentation#12090 X-original-commit: `c0dd6b7d1c` Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com> Signed-off-by: Zachary Straub (zst) <zst@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Zachary Straub <zst@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2025-02-19 08:13:50 +00:00
xpl-odoo	cc4e3a87f6	[IMP] accounting: clarify invoice sequence format task-4564980 closes odoo/documentation#12100 X-original-commit: `d2c610179a` Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2025-02-19 05:31:02 +00:00
“Dallas”	d15c4205be	[IMP] accounting/transactions: view/edit/print statements Explains how to view, edit, and print statements from both kanban and list views of transactions. task-4320158 closes odoo/documentation#12031 X-original-commit: `f1f547ca58` Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> Signed-off-by: Dallas Dean (dade) <dade@odoo.com>	2025-02-17 11:58:18 +00:00
samueljlieber	30619559c6	[IMP] data cleaning: content improvements closes odoo/documentation#12094 X-original-commit: `a762cabbb3` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Co-authored-by: dikd-odoo <dikd@odoo.com>	2025-02-16 00:37:11 +00:00
maad-odoo	689fdc428b	[FW][FIX] developer/mixins: chatter integration instructions in form view Previously, the chatter integration instructions described an outdated method using fields and widgets. However, the integration approach has changed, requiring only the `<chatter/ >` element in the form view with configurable options. This commit updates the instructions accordingly. See odoo/odoo@351b047c37 closes odoo/documentation#12088 Forward-port-of: odoo/documentation#12057 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> Signed-off-by: Aditya Maurya (maad) <maad@odoo.com>	2025-02-15 14:20:39 +00:00
dikd-odoo	e48614edb5	[IMP] sales: subscription products in ecommerce closes odoo/documentation#12045 X-original-commit: `710854226d` Signed-off-by: Zachary Straub (zst) <zst@odoo.com> Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com>	2025-02-14 23:38:30 +00:00
jero-odoo	1d7bb7f261	[IMP] inventory: notifs for expiration dates closes odoo/documentation#12083 X-original-commit: `01cf1d3dd7` Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2025-02-14 23:38:25 +00:00
jero-odoo	2311d07abe	[IMP] inventory: add a delivery closes odoo/documentation#12081 X-original-commit: `5fbab9eba4` Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: dikd-odoo <dikd@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>	2025-02-14 23:38:24 +00:00
jbelloc2	10c0c4b5bf	[ADD] sale_shopee: Shopee Connector Documentation on the benefits of the new shopee connector and guidelines for odoo users. tasks-3623720 closes odoo/documentation#12086 X-original-commit: `84051ad9de` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-14 23:38:23 +00:00
samueljlieber	85cd521464	[FIX] resource folder match closes odoo/documentation#12082 X-original-commit: `a55fdb6313` Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-14 21:59:10 +00:00
samueljlieber	194ed8085a	[FIX] clean unused resource files X-original-commit: `a4b841afce` Part-of: odoo/documentation#12082 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-14 21:59:10 +00:00
samueljlieber	9b8723e544	[IMP] tests: check resource file referenced X-original-commit: `3f1f02200b` Part-of: odoo/documentation#12082 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-14 21:59:09 +00:00
Aaron Bohy	ace11b6980	[IMP] developer/../view_architectures: add `overflow` option This commit documents the new `overflow` option of the calendar view. Associated PR: odoo/odoo#197274 Task-4564270 closes odoo/documentation#12024 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>	2025-02-14 13:53:38 +00:00
jero-odoo	30e6d651bf	[ADD] Barcode: Processing a transfer closes odoo/documentation#12072 X-original-commit: `c9fca6c3b6` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com>	2025-02-13 19:13:41 +00:00
dikd-odoo	cde28f2792	[IMP] sales: down payment intro edits from FEKU SALI edits remove image closes odoo/documentation#11970 X-original-commit: `a94c8ed498` Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-13 16:25:49 +00:00
mcsi-odoo	7f3591a3c1	[IMP] studio: automation rules correction Task-3761784 closes odoo/documentation#12067 X-original-commit: `4b6e34efc5` Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>	2025-02-13 16:25:42 +00:00
samueljlieber	6bc849d0c2	[IMP] marketing automation: content improvements closes odoo/documentation#12062 X-original-commit: `8f1d5d428c` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-13 14:53:50 +00:00
xpl-odoo	3e3aa95d4f	[IMP] website: remove slash in redirect rule expression task-4113085 closes odoo/documentation#12051 X-original-commit: `a00b6cf990` Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>	2025-02-12 17:48:22 +00:00
Sam Lieber (sali)	c95440234b	[IMP] data cleaning: field cleaning closes odoo/documentation#12041 X-original-commit: `98b765babe` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>	2025-02-12 17:48:20 +00:00
jero-odoo	d985407217	[IMP] Inventory: Adjustments edit closes odoo/documentation#12036 X-original-commit: `aa5d9911b3` Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Signed-off-by: Jessica Rogers (jero) <jero@odoo.com>	2025-02-12 13:15:23 +00:00
Paolo Gatti	629e769654	[IMP] fiscal_localizations: Documentation for l10n_it_riba Since the feature was released, lots of partners ask for information/documentation about the RIBA feature. Add a concise documentation explaining what users should know. Ref: odoo/enterprise#74097 task-4497749 closes odoo/documentation#12026 X-original-commit: `8495357d6e` Related: odoo/enterprise#79079 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com> Signed-off-by: Paolo Gatti (pgi) <pgi@odoo.com>	2025-02-12 11:36:40 +00:00
mcsi-odoo	c599d94588	[IMP] studio: adding link about accessing studio Task-3761784 closes odoo/documentation#12032 X-original-commit: `5c72ee6f63` Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com> Signed-off-by: Siobhan McGonigle (mcsi) <mcsi@odoo.com>	2025-02-12 08:47:23 +00:00
Meet Jivani [MEJI]	f3c3c31787	[IMP] pos_urban_piper: clarify combo product handling In this commit: - Added a note explaining that UrbanPiper does not support combo products. - Users need to create a new product and add combo items as variants to use them with UrbanPiper. task-4546712 closes odoo/documentation#12014 X-original-commit: `bb69f01e71` Signed-off-by: Loredana Perazzo (lrpz) <lrpz@odoo.com> Signed-off-by: Meet Jivani (meji) <meji@odoo.com>	2025-02-11 11:57:30 +00:00