[15.0][ADD] dms_field_auto_classification: New module

[victoralmau]

New module

Locked by:

• dms_field: [15.0][ADD] hr_dms_field: New module #279
• dms_auto_classification: [15.0][ADD] dms_auto_classification: New module #287

Please @pedrobaeza and @chienandalu can you review it?

@Tecnativa TT46805

[victoralmau]

Ready to review.

[pedrobaeza]

I think this will fail with non admin permissions, as models are restricted (and the same for any model access in whole module).

[victoralmau]

This field is compute sudo.
Template must be created by a user with ir.model permissions.

I have added to tests a user with permissions in Documents: Manager to confirm that that user can do the whole process (without having permissions to ir.model).

[pedrobaeza]

Template must be created by a user with ir.model permissions.

Only maximum admins have this permission, so this should be avoided (mis_builder for example had similar problems).

[victoralmau]

I understand the problem of high permissions, but what suggestion do you propose?
Another option is not to select a model (ir.model) and write the name (res.partner for example) directly.

[chienandalu]

Maybe I'm doing something wrong, but I couldn't make it work in demo:

• I'm using your test zip
• I set the VAT numbers to two customers.
• I try to classify them

But no classification is make or folder linked to the partners...

[victoralmau]

Maybe I'm doing something wrong, but I couldn't make it work in demo:

* I'm using your test zip

* I set the VAT numbers to two customers.

* I try to classify them

But no classification is make or folder linked to the partners...

Sorry, you need to create an Embedded DMS templates for partners (https://github.com/OCA/dms/pull/288/files#diff-d37451b07c0c0fd8b55c34a39c8ac57c604748a580057a00fc24ccdbb3525ddeR23) and then (with the corresponding button) in the form view of each partner you must create the linked folder (this is how dms_field works).

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[pedrobaeza]

/ocabot merge nobump

[OCA-git-bot]

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 15.0-ocabot-merge-pr-288-by-pedrobaeza-bump-nobump, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at 92e517c. Thanks a lot for contributing to OCA. ❤️