Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Navigation: Schema: mail > Tables

compose_message

Email composition wizard

Catalog: Odoo

Schema: mail

Documentation:

Generic message composition wizard. You may inherit from this wizard

at model and view levels to provide specific features.

 

The behavior of the wizard depends on the composition_mode field:

- 'comment': post on a record. The wizard is pre-populated via ``get_record_data``

- 'mass_mail': wizard in mass mailing mode where the mail details can

contain template placeholders that will be merged with actual data

before being sent to each recipient.

 

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 compose_message are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

active_domain

string

Active domain

 

attachment_ids

string

 

 

author_id_label

string

 

Author of the message. If not set, email_from may hold an email address that did not match any partner.

author_id

string

 

Author of the message. If not set, email_from may hold an email address that did not match any partner.

auto_delete_message

boolean

Delete Message Copy

Do not keep a copy of the email in the document communication history (mass mailing only)

auto_delete

boolean

Delete Emails

This option permanently removes any track of email after it's been sent, including from the Technical menu in the Settings, in order to preserve storage space of your Odoo database.

body

string

Contents

 

campaign_id_label

string

 

 

campaign_id

string

 

 

can_edit_body

boolean

Can Edit Body

 

composition_mode

string

Composition mode

 

create_date

datetime

Created on

 

create_uid_label

string

 

 

create_uid

string

 

 

display_name

string

Display Name

 

email_add_signature

boolean

Email Add Signature

 

email_from

string

From

Email address of the sender. This field is set when no matching partner is found and replaces the author_id field in the chatter.

email_layout_xmlid

string

Email Notification Layout

 

id

int32

ID

 

is_log

boolean

Log as Internal Note

 

is_mail_template_editor

boolean

Is Editor

 

lang

string

Language

Optional translation language (ISO code) to select when sending out an email. If not set, the english version will be used. This should usually be a placeholder expression that provides the appropriate language, e.g. {{ object.partner_id.lang }}.

mail_activity_type_id_label

string

 

 

mail_activity_type_id

string

 

 

mail_server_id_label

string

 

 

mail_server_id

string

 

 

mailing_list_ids

string

 

 

marketing_activity_id_label

string

 

 

marketing_activity_id

string

 

 

mass_mailing_id_label

string

 

 

mass_mailing_id

string

 

 

mass_mailing_name

string

Mass Mailing Name

If set, a mass mailing will be created so that you can track its results in the Email Marketing app.

message_type

string

Type

Message type: email for email message, notification for system message, comment for other messages such as user replies

model_is_thread

boolean

Model Is Thread

 

model

string

Related Document Model

 

notify

boolean

Notify followers

Notify followers of the document (mass post only)

parent_id_label

string

 

 

parent_id

string

 

 

partner_ids

string

 

 

record_name

string

Message Record Name

 

render_model

string

Rendering Model

 

reply_to_force_new

boolean

Considers answers as new thread

Manage answers as new incoming emails instead of replies going to the same thread.

reply_to_mode

string

Replies

Original Discussion: Answers go in the original document discussion thread. Another Email Address: Answers go to the email address mentioned in the tracking message-id instead of original document discussion thread. This has an impact on the generated message-id.

reply_to

string

Reply To

Reply email address. Setting the reply_to bypasses the automatic thread creation.

res_id

int32

Related Document ID

 

subject

string

Subject

 

subtype_id_label

string

 

 

subtype_id

string

 

 

template_id_label

string

 

 

template_id

string

 

 

use_active_domain

boolean

Use active domain

 

write_date

datetime

Last Updated on

 

write_uid_label

string

 

 

write_uid

string

 

 

 

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