---
title: "activity_mixin (Odoo)"
description: "itgen_odoo_activity_mixin"
language: it
source_language: en
translation_state: pending
canonical: https://documentation.invantive.eu/it/datamodels/odoo/Odoo.mail.activity_mixin
original: https://documentation.invantive.eu/en/datamodels/odoo/Odoo.mail.activity_mixin
updated: 2026-11-18T01:04:28Z
license: https://documentation.invantive.eu/it/
---

# activity_mixin: Odoo itgen_odoo_activity_mixin

`read only` `per partition`

- Catalogo: `Odoo`
- Schema: `mail`
- Etichetta: itgen_odoo_activity_mixin

Activity Mixin

È possibile solo recuperare i dati.

## Riepilogo

Mail Activity Mixin is a mixin class to use if you want to add activities
    management on a model. It works like the mail.thread mixin. It defines
    an activity_ids one2many field toward activities using res_id and res_model_id.
    Various related / computed fields are also added to have a global status of
    activities on documents.

    Activities come with a new JS widget for the form view. It is integrated in the
    Chatter widget although it is a separate widget. It displays activities linked
    to the current record and allow to schedule, edit and mark done activities.
    Just include field activity_ids in the div.oe-chatter to use it.

    There is also a kanban widget defined. It defines a small widget to integrate
    in kanban vignettes. It allow to manage activities directly from the kanban
    view. Use widget="kanban_activity" on activitiy_ids field in kanban view to
    use it.

    Some context keys allow to control the mixin behavior. Use those in some
    specific cases like import

     * ``mail_activity_automation_skip``: skip activities automation; it means
       no automated activities will be generated, updated or unlinked, allowing
       to save computation and avoid generating unwanted activities;

## Colonne della tabella

Di seguito sono riportate le colonne della tabella `activity_mixin`. Ogni colonna ha un tipo di dati SQL. Un nuovo valore non nullo deve essere fornito per ogni colonna richiesta in ogni momento durante l'inserimento e l'aggiornamento.

| Name | Tipo di dati | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `activity_calendar_event_id` | `varchar2` |  | [ ] |  |  |
| `activity_calendar_event_id_label` | `varchar2` |  | [ ] |  |  |
| `activity_date_deadline` | `datetime` | Next Activity Deadline | [ ] |  |  |
| `activity_exception_decoration` | `varchar2` | Activity Exception Decoration | [ ] |  | Type of the exception activity on record. |
| `activity_exception_icon` | `varchar2` | Icon | [ ] |  | Icon to indicate an exception activity. |
| `activity_ids` | `varchar2` |  | [ ] |  |  |
| `activity_state` | `varchar2` | Activity State | [ ] |  | Status based on activities Overdue: Due date is already passed Today: Activity date is today Planned: Future activities. |
| `activity_summary` | `varchar2` | Next Activity Summary | [ ] |  |  |
| `activity_type_icon` | `varchar2` | Activity Type Icon | [ ] |  | Font awesome icon e.g. fa-tasks |
| `activity_type_id` | `varchar2` |  | [ ] |  |  |
| `activity_type_id_label` | `varchar2` |  | [ ] |  |  |
| `activity_user_id` | `varchar2` |  | [ ] |  |  |
| `activity_user_id_label` | `varchar2` |  | [ ] |  |  |
| `my_activity_date_deadline` | `datetime` | My Activity Deadline | [ ] |  |  |


## Note di rilascio

Cosa è cambiato, versione per versione, nelle tabelle, nelle colonne, negli attributi e nelle funzionalità del driver:

- [Odoo](/it/release-notes/drivers?driver=odoo)
