Thursday, November 8, 2018
2 changes · master
Enhancements to existing features
Users can now finish signing and generate final signed versions of encrypted PDF documents by entering the document password when needed. This removes a blocker that previously prevented downloading or emailing the final signed file while keeping it protected with the same password.
Original PR description
Now, if a user use a encrypted PDF, he can use it, sign it, send it,... but when he will generate the final (signed) document to download it (or send it by mail), he can't. Improvement done: When the document is sign by everyone and the document is encrypted, just before the thankyou dialog, a new dialog ask the password to generate the signed PDF. The new signed file is encrypted with the same password. A second page, managed by controller, is use is specific case: the last signatory bypass the password (close window for example) or for a document already generated. We have a very simple page asking for the password. id=1896130
Resolved issues and error corrections
This change reverts a recent internal logging field rename because it stopped build logs from appearing in Odoo's runbot system. Restoring the previous naming keeps cross-version build logging working and helps teams monitor master builds reliably.
Original PR description
This reverts commit c42a130a9892482ce72d2417f418931d2a7ecf49 and commit fb7ac56d65a0d4c634a4c9387bf25bbc229d5caa. The runbot is using cross db logging and those commit were breaking the mechanism. As a result, the master builds logs were empty. If we update the runbot to use logging_type instead, the other versions builds will be impacted hence this revert.