- The `agreement` model now features mail and activities from its base module.
- The `agreement_legal` module doesn't need to add mail support now.
- Add activities to form views.
@Tecnativa TT22477
[UPD] Update agreement_legal.pot
agreement_legal 12.0.1.4.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: contract-12.0/contract-12.0-agreement_legal
Translate-URL: https://translation.odoo-community.org/projects/contract-12-0/contract-12-0-agreement_legal/
[UPD] Update agreement_legal.pot
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: contract-12.0/contract-12.0-agreement_legal
Translate-URL: https://translation.odoo-community.org/projects/contract-12-0/contract-12-0-agreement_legal/
Previous this commit users can't select a vendor in the agreement
form, this is not the behaviour described in the help. This
commit changes the domain to allow select a vendor.
we move the is_template field definition and the agreement.type model from
the agreement_legal module to the agreement module.
The fields are not displayed by default, unless the feature is enabled through a
technical feature group, this is configurable in the agreement_sale module (because agreement
in itself has no UI, and agreement_legal enables the feature by default)
- Add stage_type to agreement.stage
- Track stage of service profile
- Add Kanban view for service profiles to the dashboard
- Add product_id field to service profile
[UPD] Update agreement_legal.pot
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: contract-12.0/contract-12.0-agreement_legal
Translate-URL: https://translation.odoo-community.org/projects/contract-12-0/contract-12-0-agreement_legal/
