自動化規則

Automation rules allow the execution of one or more predefined actions in response to a specific trigger, e.g., create an activity when a field is set to a specific value, or archive a record 7 days after its last update.

When creating an automation rule, domain filters allow you to add conditions that must be met for the automation rule to run, e.g., the opportunity must be assigned to a specific salesperson, or the state of the record must not be Draft.

To create an automation rule with Odoo Studio, proceed as follows:

1. 开启 Studio 并点击 自动化，然后点击 新建。

2. Give the automation rule a clear, meaningful name that identifies its purpose.

3. Select the trigger and, if necessary, fill in the fields that appear on the screen based on the chosen trigger.

4. 点击 添加操作，然后选择 操作 的 类型，并根据所选操作，填写屏幕上出现的字段。

5. 点击 保存并关闭 或 保存并新建。

Example

To ensure follow-up on less satisfied clients, this automation rule creates an activity 3 months after a sales order is created for clients with a satisfaction percentage lower than 30%.

小訣竅

• Use the Notes tab to document the purpose and functioning of automation rules. This makes rules easier to maintain and facilitates collaboration between users.

• To modify the model targeted by the automation rule, switch models before clicking Automations in Studio, or activate developer mode, create or edit an automation rule, and select the Model in the Automation Rules form.

• Automation rules can be created from any kanban stage by clicking the (Settings) icon that appears when hovering over the kanban stage name, then selecting Automations. In this case, the Trigger is set to Stage is set to by default, but it can be changed if necessary.

  

觸發

The Trigger is used to define what kind of event needs to occur for the automation rule to run. The available triggers depend on the model. Five trigger categories are available overall:

• 數值已更新

• 電郵活動

• 時間條件

• 自訂

• 外部

Adding conditions

Domain filters allow you to determine the records an automation rule should target or exclude. Efficient filtering enhances overall performance as it avoids unnecessary processing on records that are not impacted by the rule.

小訣竅

Activate developer mode before creating an automation rule to have the most flexibility in adding domain filters.

Depending on the trigger chosen, it is possible to define one or more conditions a record must meet before and/or after a trigger occurs.

• The Before Update Domain defines the conditions a record must meet before the trigger event occurs, e.g., the record must have Type = Customer Invoice and Status = Posted.

  With developer mode activated, click Edit Domain, if available, then New Rule.

• Extra Conditions, or in some cases Apply on filters, define the conditions a record must meet after the trigger event occurs, e.g., the customer invoice must have Payment Status = Partially Paid.

  With developer mode activated if needed, click Add conditions or Edit Domain, as relevant, then New Rule.

When a trigger occurs, e.g., the payment status of a posted customer invoice is updated, the automation rule checks the defined conditions and only executes the action if the record matches those conditions.

Example

If the automated action should be executed when an email address is set for the first time (in contrast to modifying an email address) on an existing contact that is an individual rather than a company, use Email is not set and Is a Company is not set as the Before Update Domain and Email is set as the Apply on domain.

備註

The Before Update Domain is not checked upon the creation of a record.

數值已更新

Trigger automated actions when specific changes happen in the database. The triggers available in this category depend on the model and are based on common changes, such as adding a specific tag (e.g., to a task) or setting a field’s value (e.g., setting the User field).

Select the trigger, then select a value if required.

電郵活動

接收或发送电子邮件时触发自动操作。

時間條件

Trigger automated actions at a point in time relative to a date field or to the creation or update of a record. The following triggers are available:

• Based on date field: The action is triggered a defined period of time before or after the date of the selected date field.

• After creation: The action is triggered a defined period of time after a record is created and saved.

• After last update: The action is triggered a defined period of time after an existing record is edited and saved.

You can then define:

• a Delay: Specify the number of minutes, hours, days, or months. To have an action executed before the trigger date, specify a negative number. If you selected the Based on date field trigger, you must also select the date field to be used to determine the delay.

  備註

  By default, the scheduler checks for time-triggered automation rules every 240 minutes, or 4 hours. This frequency is generally sufficient for delays such as 3 months after the order date or 7 days after the last update.

  For delays of less than the equivalent of 2400 minutes, or 40 hours, the system recalculates the frequency of this check to ensure that more granular delays, e.g., 1 hour before the event start date and time, or 30 minutes after creation, can be respected as closely as possible.

  An on-screen message indicates the possible delay after the scheduled triggering of the rule.

  

  To view or manually edit the frequency of the scheduler, with developer mode activated, go to Settings ‣ Technical ‣ Scheduled Actions to see all scheduled actions for your database.

  Enter Automation in the search bar, then, in the list of results, click Automation Rules: check and execute. If desired, update the value of the Execute Every field. Click Run Manually at any time to manually trigger this scheduled action.

• Extra Conditions: Click Add condition, then specify the conditions to be met for the automation rule to run. Click New Rule to add another condition.

The action is executed when the delay is reached and the conditions are met.

Example

To send a reminder email 30 minutes before the start of a calendar event, select Start (Calendar Event) as the date field for the Trigger and set the Delay to -30 Minutes.

自訂

Trigger automated actions:

• On save: when a record is saved.

• On deletion: when a record is deleted.

• On UI change: when a field’s value is changed on the Form view, even before the record is saved.

For the On save and On UI change triggers, you must then select the field(s) to be used to trigger the automation rule in the When updating field.

警告

If no field is selected in the When updating field, the automated action may be executed multiple times per record.

Optionally, you can also define additional conditions to be met to trigger the automation rule in the Apply on field.

Example

To trigger an automated action upon the creation of a record, e.g., when a new contact is created, select the On save trigger and use ID is not set as the Before Update Domain and ID is set as the Apply on domain. Make sure the correct field is selected in the When updating field.

When a new contact is saved, it is automatically assigned a database ID, thereby triggering the automation rule.

備註

The On UI change trigger can only be used with the Execute Code action and only works when a modification is made manually. The action is not executed if the field is changed through another automation rule.

外部

Trigger automated actions based on a specific event in an external system or application using a webhook.

After the webhook is configured in Odoo, where the webhook’s URL is generated and the target record defined, it needs to be implemented in the external system.

警告

It is highly recommended to consult with a developer, solution architect, or another technical role when deciding to use webhooks and throughout the implementation process. If not properly configured, webhooks may disrupt the Odoo database and can take time to revert.

備註

It is also possible to set up an automated action that sends data to a external system’s webhook when an event occurs in your Odoo database.

也參考

Webhook documentation

動作

Once you have defined the automation rule’s trigger, click Add an action in the Actions To Do tab to define the action to be executed.

小訣竅

You can define multiple actions for the same automation rule. By default, actions are executed in the order in which they were defined.

This means, for example, that if you define an Update record action and then a Send email action where the email references the field that was updated, the email uses the updated values. However, if the Send email action is defined before the Update record action, the email uses the values set before the record is updated.

To change the order of defined actions, click the (drag handle) icon beside an action and drag it to the desired position.

更新記錄

This action updates one of the record’s (related) fields. Click the Update field and, in the list that opens, select or search for the field to be updated. If needed, click the (right arrow) next to the field name to access the list of related fields.

If you selected a many2many field, choose whether the field must be updated by Adding, Removing, or Setting it to the selected value or by Clearing it.

Example

If you want the automated action to remove a tag from the customer record, set the Update field to Customer > Tags, select by Removing, then select the tag.

小訣竅

Alternatively, you can also set a record’s field dynamically using Python code. To do so, select Compute instead of Update, then enter the code to be used for computing the field’s value. For example, if you want the automation rule to compute a custom datetime field when a task’s priority is set to High (by starring the task), you can define the trigger Priority is set to to High and define the Update Record action as follows:

創建活動

此操作用于安排与记录关联的新活动。选择 活动类型，输入 标题 和描述，然后在 到期日在 字段中指定要安排活动的时间，并选择 用户类型：

• To always assign the activity to the same user, select Specific User, then add the user in the Responsible field;

• 要针对动态链接到记录的用户，请选择 动态用户（基于记录），并根据需要更改 用户字段。

Example

将潜在客户转化为商机后，您希望自动操作为负责该潜在客户的用户发起呼叫。要执行此操作，请将 活动类型 设为 呼叫，并将 用户类型 设为 动态用户（基于记录）。

发送电子邮件和发送短信

这些操作用于向链接到特定记录的联系人发送电子邮件或短信。为此，请选择或创建 电子邮件模板 或 短信模板，然后在 发送电子邮件为 或 发送短信为 字段中选择发送电子邮件或短信的方式：

• 电子邮件：将信息作为电子邮件发送给 电子邮件模板 的收件人。

• 消息：在记录上发布消息，并通知记录的关注者。

• 备注：将消息作为内部备注发送，内部用户可在沟通栏中看到。

• 短信（无备注）：将信息作为文本信息发送给 :guilabel:`短信模板`的收件人。

• 短信（带备注）：将短信作为文本消息发送给 短信模板 的收件人，并作为内部备注发布在沟通栏中。

• 仅限备注：只将消息作为内部备注发布在沟通栏中。

傳送 WhatsApp

重要

To automate the sending of WhatsApp messages, one or more WhatsApp templates must be created.

This action is used to send a WhatsApp message to a contact linked to a specific record. To do so, select the appropriate WhatsApp Template from the dropdown menu.

Add Followers and Remove Followers

This action is used to subscribe/unsubscribe existing contacts to/from the record.

創建記錄

This action is used to create a new record on any model.

Select the required model in the Record to Create field; it contains the current model by default. Specify a Name for the record, and then, if you want to create the record on another model, select a field in the Link Field field to link the record that triggered the creation of the new record.

備註

The dropdown list related to the Link Field field only contains one2many fields existing on the current model that are linked to a many2one field on the target model.

小訣竅

You can create another automation rule with 更新記錄 actions to update the fields of the new record if necessary. For example, you can use a Create Record action to create a new project task and then assign it to a specific user using an Update Record action.

執行程式碼

重要

For automation rules that require the execution of custom code, note that maintenance of custom code is not included in the Standard or Custom pricing plans and incurs additional fees.

This action is used to execute Python code. You can write your code into the Code tab using the following variables:

• env: environment on which the action is triggered

• model: model of the record on which the action is triggered; is a void recordset

• record: record on which the action is triggered; may be void

• records: recordset of all records on which the action is triggered in multi-mode; this may be left empty

• time, datetime, dateutil, timezone: useful Python libraries

• float_compare: utility function to compare floats based on specific precision

• log(message, level='info'): logging function to record debug information in ir.logging table

• _logger.info(message): logger to emit messages in server logs

• UserError: exception class for raising user-facing warning messages

• Command: x2many commands namespace

• action = {...}: to return an action

小訣竅

The available variables are described both in the Code and Help tabs.

也參考

Odoo’s ORM capabilities

發送 Webhook 通知

This action is used to send a POST API request with the values of the selected Fields to the webhook URL specified in the URL field.

The Sample Payload provides a preview of the data included in the request using a random record’s data or dummy data if no record is available.

備註

It is also possible to set up an automated action that uses a webhook to receive data from an external system when a predefined event occurs in that system.

執行現有行動

The action is used to trigger multiple actions (linked to the current model) at the same time. To do so, click on Add a line, then, in the Add: Child Actions pop-up, select an existing action or click New to create a new one.

• 網絡鈎子