Search
Navigate
Branch
Friday, July 1, 2022
10 changes
New functionality added to Odoo
Loyalty programs can now be used in website eCommerce, not just in point of sale. This makes promotions and rewards more consistent across sales channels and gives customers a unified loyalty experience online and in-store.
Original PR description
This PR adds the support for loyalty programs in website ecommerce. Before this PR the loyalty program was tightly linked to POS. After this PR the loyalty program is made independent from POS and is reuses in a new website_sale_loyalty module. task-2319729 https://github.com/odoo/odoo/pull/63628/commits https://github.com/odoo/upgrade/pull/2038
Loyalty program features are being separated from Point of Sale so they can also support eCommerce experiences. The change also protects customers from losing loyalty points incorrectly during refunds, helping keep balances accurate.
Original PR description
Extract loyalty base concept from pos_loyalty
Enhancements to existing features
The VoIP system now uses a dedicated component to manage phone service registration with the underlying calling library. This makes the calling setup easier to maintain and helps support more reliable future improvements without changing the user workflow.
Original PR description
Introduce the Registerer model that wraps the Registerer class of the SIP.js library. Task-2896691.
Miscellaneous changes
**Before this commit:** When we split the pdf documents, rule buttons are not working from there. **After this commit:** Rule buttons will work properly from the pdf splitter. **Task**-2885866 Forward-Port-Of: odoo/enterprise#28676
Original PR description
**Before this commit:** When we split the pdf documents, rule buttons are not working from there. **After this commit:** Rule buttons will work properly from the pdf splitter. **Task**-2885866 Forward-Port-Of: odoo/enterprise#28676
This update simplifies the internal code behind the message attachment viewer and related form display areas. It reduces Enterprise-specific customizations and prepares the attachment preview experience to become easier to maintain and extend across more editions.
Original PR description
Part of task-2871070
This update reorganizes how message views are tracked inside Odoo's enterprise mail module. It reduces internal complexity, making future maintenance safer without introducing a visible change for everyday users.
Original PR description
This allows to remove the AND/OR mix from message view identifying fields. Part of task-2741982
Employees can now see daily and total overtime directly in the My Timesheets grid. This helps them quickly spot extra hours worked or missing timesheet entries, improving time tracking and reducing potential billing gaps.
Original PR description
…grid view This commit adds overtime information to the grid view in the "My Timesheet" page of the Timesheets app. Specifically it adds the daily and total overtime in the total row of the grid. The…
…grid view This commit adds overtime information to the grid view in the "My Timesheet" page of the Timesheets app. Specifically it adds the daily and total overtime in the total row of the grid. The overtime is calculated given the work hours specified in the employee record of each employee and the hours that have been timesheeted. The overtime can be positive (when the user has worked more hours or when the user has worked on a day not specified in their employee record) or negative (when the user has timesheeted less hours than what is specified in their employee record). When the overtime is zero, it is not printed. The overtime information is added on present or past dates and the total overtime information is computed for dates prior and including the present date. It is very important to the company and its employees that they encode all of their timesheets. They need to see at a glance the overtime that they have done (that might be paid by the company) or the time that is missing (missing time means the company might lose money on time it could have invoiced). The improvement that this task introduces ensures that all employees can easily keep track what they have yet to timesheet as well as whether they have been productive enough at a glance, from their defualt view in the Timesheet app. In order to implement this improvement, the "Float Time Grid" component needed to be extended in order to include the overtime information. This meant that we created a new component: the "Overtime" grid component. For that, overtime_grid_component.js file needed to be created for the new component as well as the overtimeGridComponent.xml file for the QWeb template. To get the work hours information (which is essential to the overtime computation) we made an rpc call to the hr_employee model inside of the timesheet_time_grid_model.js Additionally, for the (total) overtime computation, the timesheet_timer_grid_rendered.js file was modified to include the necessary methods. One to caclulate the daily overtime, one to calculate the total overtime, and one to check whether to overtime should be computed (used by the other two methods mentioned). For the sake of cohesion, we wanted the overtime to always be under the total time in the total grid row. For that, we created a new class in timesheet_grid.scss to accept the \n character when printing the overtime. We also modified the timesheet_grid.xml file, in order to change the grid table template to include the prop of our new component - the overtime value. Finally, we modified the hr_timesheet_view.xml to again include the new overtime grid component in the "My Timesheets" page's grid view and we modified the manifest file to include the new component. task-2878635
This update reorganizes how enterprise mail message views are connected internally. It supports cleaner message list handling and helps keep the messaging experience easier to maintain without changing the user-facing workflow.
Original PR description
…stView Part of task-2741982
Context ------- Since few line can trigger an upsell, support and maintenance team need to understand where those lines come from. It's not very easy on saas database to find out. Solution -------- This commit add a private method on "publisher_warranty.contract" that return the result of the cloc This will be helpfull to understand the origin of some lines on database where you cannot run odoo-bin cloc. Forward-Port-Of: odoo/enterprise#28956 Forward-Port-Of: odoo/enterprise#
Original PR description
Context ------- Since few line can trigger an upsell, support and maintenance team need to understand where those lines come from. It's not very easy on saas database to find out. Solution -------- This commit add a private method on "publisher_warranty.contract" that return the result of the cloc This will be helpfull to understand the origin of some lines on database where you cannot run odoo-bin cloc. Forward-Port-Of: odoo/enterprise#28956 Forward-Port-Of: odoo/enterprise#28811
The test `test_dashboard_batches` was failing due to a missing freeze_time and testing data related to time. We now use freeze_time in order to fix the test in time. Forward-Port-Of: odoo/enterprise#29017
Original PR description
The test `test_dashboard_batches` was failing due to a missing freeze_time and testing data related to time. We now use freeze_time in order to fix the test in time. Forward-Port-Of: odoo/enterprise#29017