Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: sale > Tables

order_alert

Sale Order Alert

Catalog: Odoo

Schema: sale

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table order_alert are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

action_server_id_label

string

 

 

action_server_id

string

 

 

action

string

Action

 

active

boolean

Active

When unchecked, the rule is hidden and will not be executed.

activity_date_deadline_range_type

string

Due type

 

activity_date_deadline_range

int32

Due Date In

 

activity_note

string

Note

 

activity_summary

string

Summary

 

activity_type_id_label

string

 

 

activity_type_id

string

 

 

activity_user_field_name

string

User field name

 

activity_user_id_label

string

 

 

activity_user_id

string

 

 

activity_user_ids

string

 

 

activity_user_type

string

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.

activity_user

string

Assign To

 

automation_id_label

string

 

 

automation_id

string

 

 

binding_model_id_label

string

 

Setting a value makes this action available in the sidebar for the given model.

binding_model_id

string

 

Setting a value makes this action available in the sidebar for the given model.

binding_type

string

Binding Type

 

binding_view_types

string

Binding View Types

 

child_ids

string

 

Child server actions that will be executed. Note that the last return returned action value will be used as global return value.

code

string

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_label

string

 

 

company_id

string

 

 

create_date

datetime

Created on

 

create_uid_label

string

 

 

create_uid

string

 

 

cron_nextcall

datetime

Cron Nextcall

 

crud_model_id_label

string

 

Model for record creation / update. Set this field only to specify a different model than the base model.

crud_model_id

string

 

Model for record creation / update. Set this field only to specify a different model than the base model.

crud_model_name

string

Target Model Name

 

currency_id_label

string

 

 

currency_id

string

 

 

customer_ids

string

 

 

display_name

string

Display Name

 

fields_lines

string

 

 

filter_domain

string

Apply on

If present, this condition must be satisfied before executing the action rule.

filter_pre_domain

string

Before Update Domain

If present, this condition must be satisfied before the update of the record.

groups_id

string

 

 

health

string

Health

Show the health status

help

string

Action Description

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

string

Least Delay Msg

 

link_field_id_label

string

 

Provide the field used to link the newly created record on the record used by the server action.

link_field_id

string

 

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

string

Send as

Choose method for email sending:EMail: send directly emailsPost as Message: post on document and notify followersPost as Note: log a note on document

model_id_label

string

 

Model on which the server action runs.

model_id

string

 

Model on which the server action runs.

model_name

string

Model Name

 

mrr_change_amount

decimal

MRR Change Amount

 

mrr_change_period

string

MRR Change Period

Period over which the KPI is calculated

mrr_change_unit

string

MRR Change Unit

 

mrr_max

decimal

MRR Range Max

 

mrr_min

decimal

MRR Range Min

 

name

string

Action Name

 

on_change_field_ids

string

 

Fields that trigger the onchange.

order_state

string

Status

 

partner_ids

string

 

 

product_ids

string

 

 

rating_operator

string

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

string

Send as (SMS)

Choose method for SMS sending:SMS: mass SMSPost as Message: log on documentPost as Note: mass SMS with archives

sms_template_id_label

string

 

 

sms_template_id

string

 

 

stage_category

string

Stage Category

 

stage_from_id_label

string

 

Trigger on changes of stage. Trigger over all stages if not set

stage_from_id

string

 

Trigger on changes of stage. Trigger over all stages if not set

stage_id_label

string

 

 

stage_id

string

 

 

stage_to_id_label

string

 

 

stage_to_id

string

 

 

state

string

Action To Do

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

string

 

 

team_ids

string

 

 

template_id_label

string

 

 

template_id

string

 

 

trg_date_calendar_id_label

string

 

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

string

 

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_label

string

 

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

string

 

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_type

string

Delay type

 

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 thetrigger date, like sending a reminder 15 minutes before a meeting.

trg_date_resource_field_id_label

string

 

Use the user's working schedule.

trg_date_resource_field_id

string

 

Use the user's working schedule.

trigger_condition

string

Trigger On

 

trigger_field_ids

string

 

The action will be triggered if and only if one of these fields is updated. If empty, all fields are watched.

trigger

string

Trigger

 

type

string

Action Type

 

usage

string

Usage

 

website_path

string

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

string

Website Url

The full URL to access the server action through the website.

write_date

datetime

Last Updated on

 

write_uid_label

string

 

 

write_uid

string

 

 

xml_id

string

External ID

ID of the action if defined in a XML file

 

01-03-2023 15:29 Version 22.1.135-BETA+3826

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer