automation |
Automated Action
Catalog: Odoo
Schema: base
Documentation:
Mixin that overrides the create and write methods to properly generate
ir.model.data entries flagged with Studio for the corresponding resources.
Doesn't create an ir.model.data if the record is part of a module being
currently installed as the ir.model.data will be created automatically
afterwards.
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 automation 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 |
|
☐ |
|
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_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. |
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. |
create_date |
datetime |
Created on |
☐ |
|
create_uid_label |
string |
|
☐ |
|
create_uid |
string |
|
☐ |
|
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 |
☐ |
|
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 |
|
☐ |
|
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 |
☐ |
|
name |
string |
Action Name |
☑ |
|
on_change_field_ids |
string |
|
☐ |
Fields that trigger the onchange. |
partner_ids |
string |
|
☐ |
|
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 |
|
☐ |
|
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) |
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_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