---
title: "order_alert (Odoo)"
description: "itgen_odoo_order_alert"
language: it
source_language: en
translation_state: pending
canonical: https://documentation.invantive.eu/it/datamodels/odoo/Odoo.sale.order_alert
original: https://documentation.invantive.eu/en/datamodels/odoo/Odoo.sale.order_alert
updated: 2026-11-18T01:06:37Z
license: https://documentation.invantive.eu/it/
---

# order_alert: Odoo itgen_odoo_order_alert

`read only` `per partition`

- Catalogo: `Odoo`
- Schema: `sale`
- Etichetta: itgen_odoo_order_alert

Sale Order Alert

È possibile solo recuperare i dati.

## Colonne della tabella

Di seguito sono riportate le colonne della tabella `order_alert`. 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 |
|---|---|---|:---:|---|---|
| `action` | `varchar2` | Action | [x] |  |  |
| `action_server_id` | `varchar2` |  | [ ] |  |  |
| `action_server_id_label` | `varchar2` |  | [ ] |  |  |
| `active` | `boolean` | Active | [ ] |  | When unchecked, the rule is hidden and will not be executed. |
| `activity_date_deadline_range` | `int32` | Due Date In | [ ] |  |  |
| `activity_date_deadline_range_type` | `varchar2` | Due type | [ ] |  |  |
| `activity_note` | `varchar2` | Note | [ ] |  |  |
| `activity_summary` | `varchar2` | Summary | [ ] |  |  |
| `activity_type_id` | `varchar2` |  | [ ] |  |  |
| `activity_type_id_label` | `varchar2` |  | [ ] |  |  |
| `activity_user` | `varchar2` | Assign To | [ ] |  |  |
| `activity_user_field_name` | `varchar2` | User field name | [ ] |  |  |
| `activity_user_id` | `varchar2` |  | [ ] |  |  |
| `activity_user_id_label` | `varchar2` |  | [ ] |  |  |
| `activity_user_ids` | `varchar2` |  | [ ] |  |  |
| `activity_user_type` | `varchar2` | Activity User Type | [ ] |  | Use 'Specific User' to always assign the same user on the next activity.Use 'Generic User From Record' to specify the field name of the user to choose on the record. |
| `automation_id` | `varchar2` |  | [ ] |  |  |
| `automation_id_label` | `varchar2` |  | [ ] |  |  |
| `binding_model_id` | `varchar2` |  | [ ] |  | Setting a value makes this action available in the sidebar for the given model. |
| `binding_model_id_label` | `varchar2` |  | [ ] |  | Setting a value makes this action available in the sidebar for the given model. |
| `binding_type` | `varchar2` | Binding Type | [x] |  |  |
| `binding_view_types` | `varchar2` | Binding View Types | [ ] |  |  |
| `child_ids` | `varchar2` |  | [ ] |  | Child server actions that will be executed.Note that the last return returned action value will be used as global return value. |
| `code` | `varchar2` | Python Code | [ ] |  | Write Python code that the action will execute.Some variables are available for use; help about python expression is given in the help tab. |
| `company_id` | `varchar2` |  | [ ] |  |  |
| `company_id_label` | `varchar2` |  | [ ] |  |  |
| `create_date` | `datetime` | Creato il | [ ] |  |  |
| `create_uid` | `varchar2` |  | [ ] |  |  |
| `create_uid_label` | `varchar2` |  | [ ] |  |  |
| `cron_nextcall` | `datetime` | Cron Nextcall | [ ] |  |  |
| `crud_model_id` | `varchar2` |  | [ ] |  | Model for record creation / update.Set this field only to specify a different model than the base model. |
| `crud_model_id_label` | `varchar2` |  | [ ] |  | Model for record creation / update.Set this field only to specify a different model than the base model. |
| `crud_model_name` | `varchar2` | Target Model Name | [ ] |  |  |
| `currency_id` | `varchar2` |  | [ ] |  |  |
| `currency_id_label` | `varchar2` |  | [ ] |  |  |
| `customer_ids` | `varchar2` |  | [ ] |  |  |
| `display_name` | `varchar2` | Nome visualizzato | [ ] |  |  |
| `fields_lines` | `varchar2` |  | [ ] |  |  |
| `filter_domain` | `varchar2` | Applicare su | [ ] |  | If present, this condition must be satisfied before executing the action rule. |
| `filter_pre_domain` | `varchar2` | Before Update Domain | [ ] |  | If present, this condition must be satisfied before the update of the record. |
| `groups_id` | `varchar2` |  | [ ] |  |  |
| `health` | `varchar2` | Health | [ ] |  | Show the health status |
| `help` | `varchar2` | Descrizione dell'azione | [ ] |  | Optional help text for the users with a description of the target view, such as its usage and purpose. |
| `id` | `int32` | ID | [ ] |  |  |
| `last_run` | `datetime` | Last Run | [ ] |  |  |
| `least_delay_msg` | `varchar2` | Least Delay Msg | [ ] |  |  |
| `link_field_id` | `varchar2` |  | [ ] |  | Provide the field used to link the newly created record on the record used by the server action. |
| `link_field_id_label` | `varchar2` |  | [ ] |  | Provide the field used to link the newly created record on the record used by the server action. |
| `mail_post_autofollow` | `boolean` | Subscribe Recipients | [ ] |  |  |
| `mail_post_method` | `varchar2` | Send as | [ ] |  | Choose method for email sending: EMail: send directly emails Post as Message: post on document and notify followers Post as Note: log a note on document |
| `model_id` | `varchar2` |  | [ ] |  | Model on which the server action runs. |
| `model_id_label` | `varchar2` |  | [ ] |  | Model on which the server action runs. |
| `model_name` | `varchar2` | Nome del modello | [ ] |  |  |
| `mrr_change_amount` | `numeric` | MRR Change Amount | [ ] |  |  |
| `mrr_change_period` | `varchar2` | MRR Change Period | [ ] |  | Period over which the KPI is calculated |
| `mrr_change_unit` | `varchar2` | MRR Change Unit | [ ] |  |  |
| `mrr_max` | `numeric` | MRR Range Max | [ ] |  |  |
| `mrr_min` | `numeric` | MRR Range Min | [ ] |  |  |
| `name` | `varchar2` | Nome dell'azione | [x] |  |  |
| `on_change_field_ids` | `varchar2` |  | [ ] |  | Fields that trigger the onchange. |
| `order_state` | `varchar2` | Status | [ ] |  |  |
| `partner_ids` | `varchar2` |  | [ ] |  |  |
| `product_ids` | `varchar2` |  | [ ] |  |  |
| `rating_operator` | `varchar2` | Rating Operator | [ ] |  |  |
| `rating_percentage` | `int32` | Rating Percentage | [ ] |  | Rating Satisfaction is the ratio of positive rating to total number of rating. |
| `sequence` | `int32` | Sequence | [ ] |  | When dealing with multiple actions, the execution order is based on the sequence.Low number means high priority. |
| `sms_method` | `varchar2` | Send as (SMS) | [ ] |  | Choose method for SMS sending: SMS: mass SMS Post as Message: log on document Post as Note: mass SMS with archives |
| `sms_template_id` | `varchar2` |  | [ ] |  |  |
| `sms_template_id_label` | `varchar2` |  | [ ] |  |  |
| `stage_category` | `varchar2` | Stage Category | [ ] |  |  |
| `stage_from_id` | `varchar2` |  | [ ] |  | Trigger on changes of stage.Trigger over all stages if not set |
| `stage_from_id_label` | `varchar2` |  | [ ] |  | Trigger on changes of stage.Trigger over all stages if not set |
| `stage_id` | `varchar2` |  | [ ] |  |  |
| `stage_id_label` | `varchar2` |  | [ ] |  |  |
| `stage_to_id` | `varchar2` |  | [ ] |  |  |
| `stage_to_id_label` | `varchar2` |  | [ ] |  |  |
| `state` | `varchar2` | Action To Do | [x] |  | Type of server action.The following values are available: - 'Execute Python Code': a block of python code that will be executed - 'Create a new Record': create a new record with new values - 'Update a Record': update the values of a record - 'Execute several actions': define an action that triggers several other server actions - 'Send Email': post a message, a note or send an email (Discuss) - 'Add Followers': add followers to a record (Discuss) - 'Create Next Activity': create an activity (Discuss) - 'Send SMS Text Message': send SMS, log them on documents (SMS) |
| `subscription_count` | `int32` | Subscription Count | [ ] |  |  |
| `subscription_template_ids` | `varchar2` |  | [ ] |  |  |
| `team_ids` | `varchar2` |  | [ ] |  |  |
| `template_id` | `varchar2` |  | [ ] |  |  |
| `template_id_label` | `varchar2` |  | [ ] |  |  |
| `trg_date_calendar_id` | `varchar2` |  | [ ] |  | When calculating a day-based timed condition, it is possible to use a calendar to compute the date based on working days. |
| `trg_date_calendar_id_label` | `varchar2` |  | [ ] |  | When calculating a day-based timed condition, it is possible to use a calendar to compute the date based on working days. |
| `trg_date_id` | `varchar2` |  | [ ] |  | When should the condition be triggered.If present, will be checked by the scheduler.If empty, will be checked at creation and update. |
| `trg_date_id_label` | `varchar2` |  | [ ] |  | When should the condition be triggered.If present, will be checked by the scheduler.If empty, will be checked at creation and update. |
| `trg_date_range` | `int32` | Delay after trigger date | [ ] |  | Delay after the trigger date.You can put a negative number if you need a delay before the         trigger date, like sending a reminder 15 minutes before a meeting. |
| `trg_date_range_type` | `varchar2` | Delay type | [ ] |  |  |
| `trg_date_resource_field_id` | `varchar2` |  | [ ] |  | Use the user's working schedule. |
| `trg_date_resource_field_id_label` | `varchar2` |  | [ ] |  | Use the user's working schedule. |
| `trigger` | `varchar2` | Trigger | [x] |  |  |
| `trigger_condition` | `varchar2` | Trigger On | [x] |  |  |
| `trigger_field_ids` | `varchar2` |  | [ ] |  | The action will be triggered if and only if one of these fields is updated.If empty, all fields are watched. |
| `type` | `varchar2` | Tipo di azione | [x] |  |  |
| `usage` | `varchar2` | Usage | [x] |  |  |
| `website_path` | `varchar2` | Website Path | [ ] |  |  |
| `website_published` | `boolean` | Available on the Website | [ ] |  | A code server action can be executed from the website, using a dedicated controller.The address is <base>/website/action/<website_path>.Set this field as True to allow users to run this action.If it is set to False the action cannot be run through the website. |
| `website_url` | `varchar2` | Website Url | [ ] |  | The full URL to access the server action through the website. |
| `write_date` | `datetime` | Last Updated on | [ ] |  |  |
| `write_uid` | `varchar2` |  | [ ] |  |  |
| `write_uid_label` | `varchar2` |  | [ ] |  |  |
| `xml_id` | `varchar2` | ID esterno | [ ] |  | ID of the action if defined in a XML file |


## 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)
