Skip to main content

Apply domain filters to activity plans and their templates

Project description

Odoo Community Association

Mail Activity Plan Domain

Beta License: AGPL-3 OCA/mail Translate me on Weblate Try me on Runboat

This module extends Odoo’s activity plan feature with domain-based filtering at two levels:

Plan domain

Each activity plan gains a Domain field. Only records matching this domain will have the plan available in the scheduling wizard (mail.activity.schedule). This lets you restrict plans to, for example, company-type partners or records in a specific stage.

Template domain

Each line of an activity plan (template) gains its own Domain field. When executing a plan, activities whose template domain does not match the target record are silently skipped. This allows a single plan to cover heterogeneous records while still generating only the relevant activities per record.

Notes

  • The error preview shown in the scheduling wizard (missing responsible, etc.) deliberately ignores template domains so that all potential configuration issues remain visible.

  • When scheduling a plan on multiple records, execution is serialized record by record so that each record is evaluated independently against both plan and template domains.

  • Domain syntax follows the standard Odoo domain format, e.g. [('is_company', '=', True)].

Table of contents

Usage

To use this module:

  1. Go to Discuss > Configuration > Activity Plans.

  2. Open or create an activity plan.

  3. In the Domain field, set the domain that records must match for this plan to appear in the scheduling wizard (e.g. [('is_company', '=', True)] to restrict the plan to company-type partners). Leave empty or use [] to apply to all records.

  4. In the plan lines, each activity template also has its own Domain field. Set it to skip that activity for records that do not match (e.g. [('is_company', '=', False)] to schedule an activity only for individual contacts). Leave empty or use [] to always schedule the activity.

When scheduling a plan from a record, only plans whose Domain matches that record will be listed. During execution, activities whose template domain does not match the record are silently skipped.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Tecnativa

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/mail project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_mail_activity_plan_domain-17.0.1.0.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_mail_activity_plan_domain-17.0.1.0.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 cb82b8e9128f65cc10b1c2adbc2a0cc73ad004c606daa57aceee7de9b51cdc22
MD5 a1b9d43ad488842f6fbdaf412c0522e2
BLAKE2b-256 635063b987e1d16f8e036dff363b44fca41942d0aa448e3057c61168a559afae

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page