Please enable JavaScript to view this site.

Made in EU
Odoo Forums

Odoo API Data Model

Navigation: Schema: ir > Tables

cron

Scheduled Actions

Catalog: Odoo

Schema: ir

Documentation:

Model describing cron jobs (also called actions or tasks).

 

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

Name

Data Type

Label

Required

Documentation

active

boolean

Active

☐

 

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

 

☐

 

cron_name

string

Name

☐

 

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

☐

 

doall

boolean

Repeat Missed

☐

Specify if missed occurrences should be executed when the server restarts.

fields_lines

string

 

☐

 

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

☐

 

interval_number

int32

Interval Number

☐

Repeat every x.

interval_type

string

Interval Unit

☐

 

ir_actions_server_id_label

string

 

☐

 

ir_actions_server_id

string

 

☐

 

lastcall

datetime

Last Execution Date

☐

Previous time the cron ran successfully, provided to the job through the context on the `lastcall` key

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

☑

 

nextcall

datetime

Next Execution Date

☑

Next planned execution date for this job.

numbercall

int32

Number of Calls

☐

How many times the method is called,a negative number indicates no limit.

partner_ids

string

 

☐

 

priority

int32

Priority

☐

The priority of the job, as an integer: 0 means higher priority, 10 means lower priority.

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

 

☐

 

type

string

Action Type

☑

 

usage

string

Usage

☑

 

user_id_label

string

 

☐

 

user_id

string

 

☐

 

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

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