Odoo Changelog — 2019-08-22

Thursday, August 22, 2019

3 changes · master

Improvements(3)

Enhancements to existing features

[IMP] web_editor, *: refactore the whole editor options UI

Coremasterweb_editorwebsitemass_mailingpoint_of_saleHIGH

This change rolls back an unstable editor update and restores the older, more stable editing experience used in prior Odoo versions. It also adjusts email marketing and point of sale editor integrations so users can continue editing content with fewer maintenance risks and more predictable behavior.

#editor#stability#email marketing#website

[IMP] web_editor, mass_mailing, website: restore the 12.0 editor

PR #35677

Coremasterweb_editormass_mailingwebsiteHIGH

This change replaces an unstable interim editor with the earlier, more stable editor version while keeping the newer integration layer. It reduces maintenance risk for Odoo 13 and helps website and mass mailing editing share fixes with older supported versions.

Original PR description

This PR reverts the saas-12.2 editor by restoring the 12.0 editor. The saas-12.2 editor was an intermediate work between the previous editor of Odoo 12 and the new one slated for Odoo 13. It was…

This PR reverts the saas-12.2 editor by restoring the 12.0 editor.

The saas-12.2 editor was an intermediate work between the previous
editor of Odoo 12 and the new one slated for Odoo 13. It was unstable
but it was expected to be replaced by the new editor of version 13.

However, since the new editor has been postponed to Odoo 14, the
saas-12.2 one would have been staying in Odoo 13, which would have
been a nightmare to maintain. To avoid this outcome, we chose to
put back the 12.0 editor in its place.

This has the particular advantage that Odoo 13 will share the same
bugfixes as Odoo 12 and 11 as they all run under the same core
editor, while the saas-12.2 one would have been an entirely
different beast to maintain.

Despite its title, this PR is not a revert of PR 29775 per se, as
we are using the wysiwyg abstraction layer that was introduced in
that PR.

The goal of the wysiwyg abstraction layer is to provide an
interface for other modules that want to use the editor feature
such that the editor core itself can be changed without requiring
extensive changes in the other modules.

This PR uses the wysiwyg abstraction layer to restore the 12.0
editor with minimal changes to the modules that use the editor.

#editor#stability#website#email-marketing

[MERGE] sign: general UX improvements and traceability

PR #4668

Enterprisemastersignhr_contract_salaryHIGH

The Sign app now offers clearer signing and template-editing flows, better labels and messages, immediate email sending for smaller requests, and cleaner document naming. It also adds activity logs for access, signing, downloads, and request creation, improving traceability and confidence in signed documents.

Original PR description

This branch has 2 main goals:

1. Improve UX of the Sign application
2. Add traceability of sign requests

UX Improvements
==============
- improve ux when editing a template: items have a placeholder (by default the type of item)
- improve field labels, dialog messages, button strings, etc.
- send emails immediately if needed
- less shenanigans with file extensions
- update views for better interactions (moar buttons!!)
- improve redirection feature by adding a label, allowing users to redirect signers to a specific page after signing

Traceability
=========
- add logs when a sign item is accessed/signed
- allow printing a report of logs

#esignature#user-experience#traceability#audit-log

This PR reverts the saas-12.2 editor by restoring the 12.0 editor. The saas-12.2 editor was an intermediate work between the previous editor of Odoo 12 and the new one slated for Odoo 13. It was unstable but it was expected to be replaced by the new editor of version 13. However, since the new editor has been postponed to Odoo 14, the saas-12.2 one would have been staying in Odoo 13, which would have been a nightmare to maintain. To avoid this outcome, we chose to put back the 12.0 editor in its place. This has the particular advantage that Odoo 13 will share the same bugfixes as Odoo 12 and 11 as they all run under the same core editor, while the saas-12.2 one would have been an entirely different beast to maintain. Despite its title, this PR is not a revert of PR 29775 per se, as we are using the wysiwyg abstraction layer that was introduced in that PR. The goal of the wysiwyg abstraction layer is to provide an interface for other modules that want to use the editor feature such that the editor core itself can be changed without requiring extensive changes in the other modules. This PR uses the wysiwyg abstraction layer to restore the 12.0 editor with minimal changes to the modules that use the editor.

This branch has 2 main goals: 1. Improve UX of the Sign application 2. Add traceability of sign requests UX Improvements ============== - improve ux when editing a template: items have a placeholder (by default the type of item) - improve field labels, dialog messages, button strings, etc. - send emails immediately if needed - less shenanigans with file extensions - update views for better interactions (moar buttons!!) - improve redirection feature by adding a label, allowing users to redirect signers to a specific page after signing Traceability ========= - add logs when a sign item is accessed/signed - allow printing a report of logs