Daily updates from Odoo
Wednesday, September 1, 2021
3 changes · master
New functionality added to Odoo
Task assignees can now manage their own personal stage for each assigned task, separate from the project's shared workflow. This helps individuals organize their work without changing the overall project pipeline used by the team.
Original PR description
WIP Add user personal stages on tasks, the goal is to allow any user to have their own 'pipeline', for each task they are assigned to they will be able to assign a personal stage which will be different from the one used in the project pipeline. See https://github.com/odoo/odoo/pull/74087 Task ID: 2398734
Enhancements to existing features
Quality checks can now be managed directly on individual stock move lines, including by lot or serial number. This helps warehouse and quality teams check the right quantities during picking and navigate required checks more easily.
Original PR description
This creates the possibility to use Quality Checks at the stock move line level. This can be done in the Control Point, configuring it to track QC at the Lot/SN level. It is also possible to set a percentage of a lot that has to be checked, indicating which quantity should be checked within a lot at picking. The Quality Check pop-up has been transformed into a wizard and adapted. It shows how many checks need to be done and to which Lot/SN the QC belongs. It also gives the possibility to go to the previous/next QC. QC icons have been added in the detailed operations tab, next to the stock move lines having a QC. Task-ID: 2566811 Migration-PR: https://github.com/odoo/upgrade/pull/2785 Community-PR: https://github.com/odoo/odoo/pull/75691
Internal users can now add missing signature, initials, or text fields while they are signing a document, instead of abandoning the process and starting over. The change keeps signing secure by only allowing edits before anyone has signed, recording who made the update, and using a copied template for the revised request.
Original PR description
Adds edit mode during sign procedure, allowing back-end users to add fields to a template while signing a document. The rationale behind this feature is: when you fill a whole document and see it…
Adds edit mode during sign procedure, allowing back-end users to add fields to a template while signing a document. The rationale behind this feature is: when you fill a whole document and see it miss a field, you have to quit the sign process, ask for edit, start from beginning again. The process is quite frustrating if you use sign often. This PR adds an extra flow to the sign application, allowing internal users to edit already sent requests while signing. By using ctrl+click, the user is now able to add new sign items (only signature, initials and text types) to a request if the request has not been signed by anyone yet. Technically, the user adds the new items to a new template that is a copy from the original one. This process adds an "Update" log to the sign request saving who edited the template and when it was done. Since the changes are done to a new template and with the guarantee that no one has signed the document yet, the security of sign is not changed by this feature. In order to guarantee this, automated tests were created to assure the feature is working correctly. Two options were available to allow this feature: First, a button could have been added on the control panel of the backend view. It would have redirected to the template edition view. This solution would be simplier to implement but it would have broken the flow and it may have been difficult to keep the item already filled when switching from the signing to editing views. The other option was to directly add items during the signing procedure and send all the items (old and new) to the sign controller to handle them properly. This solution has been kept as the flow is less perturbed. Furthermore, it was decided to keep an uncommon flow when one can send a template without item. In that case, the "Sign Document" button in the control panel allows to validate it without use of any item. To make it work, a default role was needed to allow the creation of item when no role was available. The default role is therefore mandatory for this use case. That's why new ir.rule are added in this commit to prevent deletion of them by regular or even admin users. task-2475732