automation: Odoo itgen_odoo_automation
read only per partition
- Catálogo:
Odoo - Esquema:
base - Etiqueta: itgen_odoo_automation
Automated Action
Solo puede recuperar datos.
Resumen
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.
Columnas de la Tabla
A continuación se muestran las columnas de la tabla automation. Cada columna tiene un tipo de datos SQL. Se debe proporcionar un nuevo valor no nulo para cada columna requerida en todo momento durante la inserción y la actualización.
| Name | Tipo de Datos | Label | Required | Marks | Documentation |
|---|---|---|---|---|---|
action_ |
varchar2 |
||||
action_ |
varchar2 |
||||
active |
boolean |
Active | When unchecked, the rule is hidden and will not be executed. | ||
activity_ |
int32 |
Due Date In | |||
activity_ |
varchar2 |
Due type | |||
activity_ |
varchar2 |
Note | |||
activity_ |
varchar2 |
Summary | |||
activity_ |
varchar2 |
||||
activity_ |
varchar2 |
||||
activity_ |
varchar2 |
User field name | |||
activity_ |
varchar2 |
||||
activity_ |
varchar2 |
||||
activity_ |
varchar2 |
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_ |
varchar2 |
Setting a value makes this action available in the sidebar for the given model. | |||
binding_ |
varchar2 |
Setting a value makes this action available in the sidebar for the given model. | |||
binding_ |
varchar2 |
Binding Type | |||
binding_ |
varchar2 |
Binding View Types | |||
child_ |
varchar2 |
Child server actions that will be executed.Note that the last return returned action value will be used as global return value. | |||
code |
varchar2 |
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_ |
datetime |
Creado en | |||
create_ |
varchar2 |
||||
create_ |
varchar2 |
||||
crud_ |
varchar2 |
Model for record creation / update.Set this field only to specify a different model than the base model. | |||
crud_ |
varchar2 |
Model for record creation / update.Set this field only to specify a different model than the base model. | |||
crud_ |
varchar2 |
Target Model Name | |||
display_ |
varchar2 |
Nombre para mostrar | |||
fields_ |
varchar2 |
||||
filter_ |
varchar2 |
Presentar la solicitud en | If present, this condition must be satisfied before executing the action rule. | ||
filter_ |
varchar2 |
Before Update Domain | If present, this condition must be satisfied before the update of the record. | ||
groups_ |
varchar2 |
||||
help |
varchar2 |
Descripción de la acción | Optional help text for the users with a description of the target view, such as its usage and purpose. | ||
id |
int32 |
ID | |||
last_ |
datetime |
Last Run | |||
least_ |
varchar2 |
Least Delay Msg | |||
link_ |
varchar2 |
Provide the field used to link the newly created record on the record used by the server action. | |||
link_ |
varchar2 |
Provide the field used to link the newly created record on the record used by the server action. | |||
mail_ |
boolean |
Subscribe Recipients | |||
mail_ |
varchar2 |
Send as | Choose method for email sending: EMail: send directly emails Post as Message: post on document and notify followers Post as Note: log a note on document | ||
model_ |
varchar2 |
Model on which the server action runs. | |||
model_ |
varchar2 |
Model on which the server action runs. | |||
model_ |
varchar2 |
Nombre Modelo | |||
name |
varchar2 |
Nombre de la acción | |||
on_ |
varchar2 |
Fields that trigger the onchange. | |||
partner_ |
varchar2 |
||||
sequence |
int32 |
Sequence | When dealing with multiple actions, the execution order is based on the sequence.Low number means high priority. | ||
sms_ |
varchar2 |
Send as (SMS) | Choose method for SMS sending: SMS: mass SMS Post as Message: log on document Post as Note: mass SMS with archives | ||
sms_ |
varchar2 |
||||
sms_ |
varchar2 |
||||
state |
varchar2 |
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_ |
varchar2 |
||||
template_ |
varchar2 |
||||
trg_ |
varchar2 |
When calculating a day-based timed condition, it is possible to use a calendar to compute the date based on working days. | |||
trg_ |
varchar2 |
When calculating a day-based timed condition, it is possible to use a calendar to compute the date based on working days. | |||
trg_ |
varchar2 |
When should the condition be triggered.If present, will be checked by the scheduler.If empty, will be checked at creation and update. | |||
trg_ |
varchar2 |
When should the condition be triggered.If present, will be checked by the scheduler.If empty, will be checked at creation and update. | |||
trg_ |
int32 |
Delay after trigger date | Delay after the trigger date.You can put a negative number if you need a delay before the trigger date, like sending a reminder 15 minutes before a meeting. | ||
trg_ |
varchar2 |
Delay type | |||
trg_ |
varchar2 |
Use the user's working schedule. | |||
trg_ |
varchar2 |
Use the user's working schedule. | |||
trigger |
varchar2 |
Trigger | |||
trigger_ |
varchar2 |
The action will be triggered if and only if one of these fields is updated.If empty, all fields are watched. | |||
type |
varchar2 |
Tipo de acción | |||
usage |
varchar2 |
Usage | |||
website_ |
varchar2 |
Website Path | |||
website_ |
boolean |
Available on the Website | A code server action can be executed from the website, using a dedicated controller.The address is /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_ |
varchar2 |
Website Url | The full URL to access the server action through the website. | ||
write_ |
datetime |
Last Updated on | |||
write_ |
varchar2 |
||||
write_ |
varchar2 |
||||
xml_id |
varchar2 |
ID Externo | ID of the action if defined in a XML file |
Notas de la Versión
Cambios introducidos en cada versión en las tablas, columnas, atributos y capacidades del controlador: