Odoo Changelog — 2019-08-23

Friday, August 23, 2019

3 changes

New Features(3)

New functionality added to Odoo

[ADD] iot: Load a true certificate on IoT Box

Coremasterhw_drivershw_posbox_homepagepoint_of_saleSECURITY

IoT Boxes can now store customer credentials and request an official certificate from Odoo when their current certificate is missing or outdated. This enables secure HTTPS access through a dedicated Odoo IoT domain, improving trust and reliability for connected devices.

Original PR description

With this commit we add the possibility to save the db_uuid and enterprise_code on the IoT Box.

We check the current SSL certificate and if it is not authenticated or not up to date
we send a request to `https://www.odoo.com/odoo-enterprise/iot/x509`
with the db_uuid and enterprise_code to get the certificate, key, and domain associated with the client.
The IoT Box will be accessible in HTTPS according to the following domain:

`https://<ip-with-dashes>.<sub-hash>.odoo-iot.com`

`<ip-with-dashes>` being the ip address with dashes
`<sub-hash>` being a subdomain assigned by Odoo to a customer

Task: 1931770

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#iot#https#certificate#device-security

[IMP] account_reports[_followup]: Add SMS support

PR #5240

Enterprisemasteraccount_reportsaccount_reports_followupMEDIUM

Users can now send SMS reminders directly from customer follow-up reports, with default messages pre-filled from company settings. Follow-up levels can also define when SMS should be used and customize the message, helping teams reach customers through another communication channel.

Original PR description

`account_reports`
======

Purpose
----------

In the follow-up reports, allow to send an SMS text
message to remind a partner he has some due payment.

Specification
--------------

Add a primary button "Send By SMS" in the follow-up report form view to send
and SMS. The button opens the sms composer to send the message.

The message should be pre-filled with a default value defined on
the user's company.

Once the SMS has been sent, the buttons becomes secondary
and the button "Done" appears.

The SMS should appear in the chatter.

`account_reports_followup`
======

Purpose
----

Allow to define a custom SMS to send to a partner according
to the followup level.

Specification
------------

On a followup level line:
- Add a Boolean field: set to True if an SMS should be sent

- Add a Char field for the SMS body. Allow to use pseudo-template
variable, similar to the email pseudo-template.

If SMS is selected on the followup report line, the
"Send By SMS" should be primary and secondary otherwise.

Some refactoring
========
To easily integrate SMS support and minimize the diff, some refactoring was done on the frontend side:
1. Event Bindings

Currently, buttons event handlers in the followup
view are attached using jQuery.
Instead, the Odoo style event binding should be
used instead. The syntax is shorter and declarative, hence
less error prone.

2. Template Redefined

The template `CustomerStatements.buttons` from `account_reports`
was not used in `account_reports_followup` and completely
redefined to add a button (template `CustomerStatements.buttonsWithLevels`).
Extending the first template is the correct way to add a button.
It is shorter, does not require to re-attach event handlers and
allows to remove the `renderButtons` override.

3. Button class

In `account_reports_followup`, buttons like "Send By Email",
"Print Letter", etc are set to primary if the current followup line
uses email, letter, etc, and secondary otherwise.
The logic to add or remove the classes was repeated several times
Now, it is factorised with a helper function.
This helper function will be reused in the future to send SMS
text messages.

#sms#follow-up#payments#customer reminders

[ADD] iot: Send credential to IoT Box with the token

PR #5192

EnterprisemasteriotMEDIUM

This update adds certificate credentials to the setup token sent to an IoT Box. It helps the device load a real certificate during onboarding, improving secure and reliable connection setup.

Original PR description

We add to the token the credential to use it to load real certificate on IoT Box

Task: 1931770

#iot#setup#certificates#credentials

With this commit we add the possibility to save the db_uuid and enterprise_code on the IoT Box. We check the current SSL certificate and if it is not authenticated or not up to date we send a request to `https://www.odoo.com/odoo-enterprise/iot/x509` with the db_uuid and enterprise_code to get the certificate, key, and domain associated with the client. The IoT Box will be accessible in HTTPS according to the following domain: `https://<ip-with-dashes>.<sub-hash>.odoo-iot.com` `<ip-with-dashes>` being the ip address with dashes `<sub-hash>` being a subdomain assigned by Odoo to a customer Task: 1931770 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

`account_reports` ====== Purpose ---------- In the follow-up reports, allow to send an SMS text message to remind a partner he has some due payment. Specification -------------- Add a primary button "Send By SMS" in the follow-up report form view to send and SMS. The button opens the sms composer to send the message. The message should be pre-filled with a default value defined on the user's company. Once the SMS has been sent, the buttons becomes secondary and the button "Done" appears. The SMS should appear in the chatter. `account_reports_followup` ====== Purpose ---- Allow to define a custom SMS to send to a partner according to the followup level. Specification ------------ On a followup level line: - Add a Boolean field: set to True if an SMS should be sent - Add a Char field for the SMS body. Allow to use pseudo-template variable, similar to the email pseudo-template. If SMS is selected on the followup report line, the "Send By SMS" should be primary and secondary otherwise. Some refactoring ======== To easily integrate SMS support and minimize the diff, some refactoring was done on the frontend side: 1. Event Bindings Currently, buttons event handlers in the followup view are attached using jQuery. Instead, the Odoo style event binding should be used instead. The syntax is shorter and declarative, hence less error prone. 2. Template Redefined The template `CustomerStatements.buttons` from `account_reports` was not used in `account_reports_followup` and completely redefined to add a button (template `CustomerStatements.buttonsWithLevels`). Extending the first template is the correct way to add a button. It is shorter, does not require to re-attach event handlers and allows to remove the `renderButtons` override. 3. Button class In `account_reports_followup`, buttons like "Send By Email", "Print Letter", etc are set to primary if the current followup line uses email, letter, etc, and secondary otherwise. The logic to add or remove the classes was repeated several times Now, it is factorised with a helper function. This helper function will be reused in the future to send SMS text messages.