[16.0][MIG] dms_field: Migration to 16.0 #339

… app

... so to speak. @Tecnativa TT29847

Co-authored-by: luismalta <luis.malta@kmee.com.br>

Approved Enric Tobella OCA#169

Currently translated at 100.0% (75 of 75 strings) Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/es/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/

Currently translated at 100.0% (75 of 75 strings) Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/it/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/

Currently translated at 100.0% (75 of 75 strings) Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/it/

The root directory can't be opened using the contextual action menu (`open`) Impacted versions: 12.0 and above Steps to reproduce: Go to "DMS directories" in the partner form view Create a new root directory Right-click and choose `Open` Current behavior: Odoo raises an error `TypeError: record is null` Expected behavior: Open the directory like if we click on the `Open` button in the right section (Document preview)

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/

- Create dms.field.template to set model, groups and directory structure. - Remove the wizard to create a directory from a record. - Directory structure is created when record is created (partner for example). - Change the information on the right side. - Have directory/file tree open when loading. TT46804 TT46804

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/

…cut several files and paste them into another directory) TT47482

…n view. TT48181

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/

…n as default state Before this change, when lauching the reload, the child directories of the reloaded one are opened too. By doing at this step and not setting the default state, the reloads are done just for the implied nodes. Furthermore, the code is improved to just reload the directories that have being changed.

Currently translated at 100.0% (75 of 75 strings) Translation: dms-15.0/dms-15.0-dms_field Translate-URL: https://translation.odoo-community.org/projects/dms-15-0/dms-15-0-dms_field/es/

With hr_dms_field The steps to reproduce the problem are: 1. Open Employee 2. Go to Documents Page 3. Drop a file on a directory 4. Go to another Employee 5. Try to drop a file The file can not be dropped.

In the migration, the view type is changed from dms_tree to dms_list. That's because in this point https://github.com/odoo/odoo/blob/16.0/addons/web/static/src/views/fields/field.js#L282 the 'tree' string is replaced by 'list' what is causing problems trying to set the view type as it was before.

A parent directory can be set in templates, if set, the directory that is created linked to a record will be a "child" of that directory. TT48650

…ors when creating directories from a template. Example of use case: - Create a partner. - Create a template linked to partners. - Create a directory through the template. - An access group linked to the partner is created. - Delete the partner directory. - Creates a new directory through the template. - No error will occur and the previous access group will be re-used.

…ring Now the process will be as follows: - The auto-generated access group will be created. - The user will be defined in explicit_user_ids of the group created in the previous step. In the directory created (from the corresponding record) the auto-generated group (for the user to have access) + the access groups that the template had will be used.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[16.0][MIG] dms_field: Migration to 16.0 #339

[16.0][MIG] dms_field: Migration to 16.0 #339

Commits on Jun 19, 2024