Saturday, January 13, 2024
5 changes · 17.0
Enhancements to existing features
This improvement enhances the subscription payment reminder email template by ensuring the customer reference (subscription code) is properly included in the email context. This allows the email template to correctly display the subscription code when notifying customers about upcoming suspension, providing better clarity and personalization in payment reminder communications.
Original PR description
client_order_ref
The customer reference is needed to fill this value in "email_payment_reminder" template.
```xml
Your subscription <t t-out="ctx.get('code') or ''">CODE</t> is still valid but will be <strong>suspended</strong>
```
Forward-Port-Of: odoo/enterprise#54124
Forward-Port-Of: odoo/enterprise#53319This update improves the error messaging when users enter incorrect login credentials for the Indian E-Way Bill system. Instead of showing just an error code "108", users will now see a clear, descriptive message "[108] Invalid login credentials." This makes it easier for users to understand what went wrong and take corrective action.
Original PR description
Before This PR: -------------------- If the username and password are wrong, then it only displays the error "108". After This PR: ------------------ If the username and password are wrong, then it displays the error. "[108] Invalid login credentials." task - 3304862 Forward-Port-Of: odoo/odoo#149305 Forward-Port-Of: odoo/odoo#120901
Resolved issues and error corrections
This update corrects how cancelled invoices are reported in Peru's sales tax reports (SIRE). The system now properly identifies cancelled invoices using EDI status instead of a field that gets cleared during cancellation, and ensures all amounts are set to zero for cancelled invoices as required by SUNAT regulations. This ensures accurate tax compliance reporting for Peruvian businesses.
Original PR description
The `l10n_pe_edi_cancel_cdr_number` field undergoes cleaning during the cancellation process, making it inappropriate to rely on it as a confirmation of invoice cancellation. The recent update involves utilizing the EDI state to validate both the cancellation status and the prior signature of an invoice. Additionally, SUNAT requires all amounts to be set to 0 for canceled invoices in *SIRE* reports. Extra: Considering the Odoo option to show all entries, now the draft entries are added on the preview, but ignored on the TXT file X-original-commit: 10f9d60f5ba8394b1a121b828f940518fca70ce9
This fix resolves a conflict that occurred when switching between demo and production modes when both Italian EDI and Peppol features are enabled. The issue was that both systems use proxy users, and the system was incorrectly checking all proxy users instead of just Italian ones, causing production Peppol connections to interfere. The fix ensures only Italian proxy users are checked during demo mode switching and prevents accidental deletion of Peppol demo connections.
Original PR description
Peppol and Italian edi both uses a proxy user. We should only use Italian proxy users when checking demo mode otherwise Peppol production proxy users can interfere and trigger an error like 'Company already have prod connection'. Also we don't want to delete demo Peppol connections. opw-3675908 Forward-Port-Of: odoo/odoo#149173
This fix resolves an issue where loyalty points were not being earned and gift card codes were not being generated when sales orders were created through the Sales app for loyalty programs configured with a specific website. The solution allows these features to work correctly regardless of whether orders are placed through the website or the Sales application.
Original PR description
...for orders made through Sales with loyalty programs that uses websites Problem: For loyalty & gift card programs that has sales and website enabled along with a specified website, the loyalty…
...for orders made through Sales with loyalty programs that uses websites Problem: For loyalty & gift card programs that has sales and website enabled along with a specified website, the loyalty points will not accrue and gift card codes will generates for products if the SO was created with the Sales app. Solution: The SO ordered through the website should filter based on the website_id. SOs created through Sales will not have a website_id, thus, no need to add an extra filter for website_id. Gift card codes will generate and loyalty points will accrue for orders made through Sales even if the program has a website specified. Steps to Reproduce on Runbot 16: Create a new product of the type consumable Go to Sales > Products > Gift cards & eWallet and click on NEW For the Gift Card Products field add the previously created product For the website field specify a specific website (e.g. My Website) Create a new sale order for the originally created product Confirm the sale order Click on the Customer Preview smart button You won’t see a gift card code anywhere when it should have been generated & Loyalty points are not accrued opw-3550278 opw-3587226 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#149112 Forward-Port-Of: odoo/odoo#146753