Monday, August 12, 2024
3 changes · saas-17.4
Enhancements to existing features
The Xendit payment form now asks card users for their name, email address, and phone number before tokenizing a card. This keeps card payments aligned with new Xendit/Visa requirements and helps avoid failed tokenization during checkout.
Original PR description
Based on the latest email sent from Xendit support, card tokenization will require more mandatory arguments such as name, email address, and phone number per this [page](https://support.visaacceptance.com/knowledgebase/knowledgearticle/?code=KA-04583) In order to support this change, these inputs have been included in the card information form which later on will be included when tokenizing the card via Xendit.js library --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now add or remove passkeys without being signed out of their active sessions. This reduces disruption and makes passkey management smoother while preserving the existing authentication flow.
Original PR description
Invalidating sessions upon creating and deleting keys makes for an annoying user experience.
Shared Knowledge article links now send internal users straight to the newer, cleaner Knowledge page address. This avoids extra behind-the-scenes redirects, making link opening smoother and keeping the browser address more stable.
Original PR description
When the user accesses an article via a shared link (`/knowledge/article/42`), the internal users will be redirected to the backend view of Knowledge using the legacy route (i.e: `/web#id=...&model=...`). When loading the page, the router will transform that url to a more friendly one (i.e: `/odoo/knowledge/...`). To avoid updating the url many times, we will directly redirect the user to the new route. task-3975577