Monday, May 18, 2020
3 changes · master
Code cleanup and technical improvements
The eLearning module now handles invitation-related field values through a single automatic calculation approach instead of separate default and change-time rules. This keeps behavior consistent while reducing maintenance complexity, with no intended change for end users.
Original PR description
… computed field PURPOSE Try to move from onchange / default_get to stored editable computed fields. Behavior should be the same (computed or set by user), with support of create / write / onchange field update without additional code. SPECIFICATIONS Update classic fields updated in some cases by onchange and/or default methods by fields with store=True, readonly=False. It means their value comes either from manual user input, either from trigger based computation. Remove onchange and default_get when possible, leading to an unique computation method and clearing fields definition. Also clean some fields definition inconsistencies, notably required fields that should instead be correctly computed or default that have no real meaning. LINKS Task ID : 2229048 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event ticket registrations are now created together at key points such as checkout, sales order confirmation, and registration editing. This makes the process more reliable and easier to extend for future CRM and event synchronization automation.
Original PR description
PURPOSE
Create event registrations in batch. It will allow to customize group-creation of
registrations, notably with automated rules for crm / event synchronization.
SPECIFICATIONS
Find where registrations are created, and
* either remove registration creation (cart update)
* either make it in batch (buying tickets in front-end, using the registration
editor)
LINKS
Task ID 2258685
Prepare Task ID 2166679 (create leads from registrations)
PR #51341The system now records when automatically generated export references are created. This helps administrators identify and clean up old entries in a potentially large internal table, improving long-term database maintenance.
Original PR description
This table could be huge and we need a way to identify old records in order to vacuum them