Regler för automatisering

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. Open Studio and click Automations, then New.

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. Klicka på Lägg till en åtgärd, välj sedan Typ av åtgärd och fyll i fälten som visas på skärmen baserat på den åtgärd du har valt.

5. Klicka på Save & Close eller Save & New.

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%.

Tips

• 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.

  

Utlösare

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:

• Värden uppdaterade

• E-post evenemang

• Villkor för tidsinställning

• Anpassad

• Extern

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.

Tips

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.

Observera

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

Värden uppdaterade

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.

E-post evenemang

Utlösa automatiska åtgärder när du tar emot eller skickar e-post.

Villkor för tidsinställning

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.

Du kan sedan definiera:

• 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.

  Observera

  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.

Anpassad

Utlösa automatiserade åtgärder:

• 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.

För utlösarna On save och On UI change måste du must sedan välja det eller de fält som ska användas för att utlösa automatiseringsregeln i fältet When updating.

Varning

Om inget fält har valts i fältet When updating kan den automatiska åtgärden utföras flera gånger per post.

Alternativt kan du också definiera ytterligare villkor som ska uppfyllas för att utlösa automatiseringsregeln i fältet Apply on.

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.

Observera

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.

Extern

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.

Varning

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.

Observera

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.

Se även

Webhook documentation

Åtgärder

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.

Tips

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.

Uppdatera rekord

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.

Tips

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:

Skapa aktivitet

Den här åtgärden används för att schemalägga en ny aktivitet som är kopplad till posten. Välj en Activity Type, ange en Title och en beskrivning, ange sedan när du vill att aktiviteten ska schemaläggas i fältet Due Date In och välj en User type:

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

• Om du vill rikta in dig på en användare som är dynamiskt kopplad till posten väljer du Dynamic User (based on record) och ändrar User Field om det behövs.

Example

När ett lead har omvandlats till en möjlighet vill du att den automatiska åtgärden ska ringa upp den användare som är ansvarig för leadet. Det gör du genom att ange Activity Type till Call och User Type till Dynamic User (based on record).

Skicka e-post och skicka SMS

Dessa åtgärder används för att skicka ett e-postmeddelande eller ett textmeddelande till en kontakt som är kopplad till en viss post. Det gör du genom att välja eller skapa en Email Template eller en SMS Template och sedan välja hur du vill skicka e-postmeddelandet eller textmeddelandet i fältet Send Email As eller Send SMS As:

• Email: för att skicka meddelandet som ett e-postmeddelande till mottagarna i Email Template.

• Message: för att lägga upp meddelandet på posten och meddela postens följare.

• Note: för att skicka meddelandet som en intern anteckning som är synlig för interna användare i chatten.

• SMS (utan anteckning): för att skicka meddelandet som ett textmeddelande till mottagarna av SMS-mallen.

• SMS (med anteckning): för att skicka meddelandet som ett textmeddelande till mottagarna av SMS-mallen och lägga upp det som en intern anteckning i chatten.

• Note only: för att endast lägga upp meddelandet som en intern anteckning i chatten.

Send WhatsApp

Viktigt

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.

Lägg till följare och ta bort följare

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

Skapa rekord

Denna åtgärd används för att skapa en ny post i en valfri modell.

Välj önskad modell i fältet Record to Create; som standard innehåller det den aktuella modellen. Ange ett Name för posten, och om du vill skapa posten i en annan modell väljer du ett fält i fältet Link Field för att länka den post som utlöste skapandet av den nya posten.

Observera

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.

Tips

You can create another automation rule with Uppdatera rekord 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.

Utför kod

Viktigt

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.

Denna åtgärd används för att exekvera Python-kod. Du kan skriva din kod i fliken Code med hjälp av följande variabler:

• env: miljö där åtgärden utlöses

• model: modell av den post där åtgärden utlöses; är en void recordset

• post: post där åtgärden utlöses; kan vara ogiltig

• records: postmängd av alla poster som åtgärden utlöses på i multiläge; detta kan lämnas tomt

• time, datetime, dateutil, timezone: användbara Python-bibliotek

• float_compare: verktygsfunktion för att jämföra flyttal baserat på specifik precision

• log(message, level='info'): loggningsfunktion för att registrera felsökningsinformation i ir.logging-tabellen

• _logger.info(message): logger för att skicka meddelanden i serverloggar

• UserError: undantagsklass för varningsmeddelanden riktade till användaren

• Command: x2many kommandon namnområde

• action = {...}: för att returnera en åtgärd

Tips

De tillgängliga variablerna beskrivs både i flikarna Code och Help.

Se även

Odoo’s ORM capabilities

Skicka Webhook-avisering

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.

Sample Payload ger en förhandsvisning av de data som ingår i begäran med hjälp av data från en slumpmässig post eller dummydata om ingen post finns tillgänglig.

Observera

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.

Utföra befintliga åtgärder

Åtgärden används för att utlösa flera åtgärder (kopplade till den aktuella modellen) samtidigt. För att göra detta klickar du på Add a line och sedan, i popup-fönstret Add: Child Actions”, välj en befintlig åtgärd eller klicka på :guilabel:`New för att skapa en ny.

• Webhooks