Types of Actions in Odoo 18 - Odoo Slides

Types of Actions in Odoo 18
Enterprise

Enterprise
In Odoo, actions define the system's response to user
interactions, like logging in or clicking buttons. They can be
stored in the database or returned as dictionaries in methods.
Odoo offers various action types for different purposes.
Introduction

Enterprise
1. Window Actions
2. URL Actions
3. Server Actions
4. Client Actions
5. Report Actions
6. Scheduled Actions
Types of Actions in Odoo

Enterprise
Window actions are used to display views (list, form, kanban,
etc.) of models. Key parameters include:
● type: Always set to "ir.actions.act_window".
● res_model: The model the action operates on.
● views: List of views available for the action.
● domain: Filter conditions for records.
● context: Optional parameters or default values.
● name: Label for the action (optional).
● target: Where the action is displayed (current, new, or
inline).
Window Actions (ir.actions.act_window)

Enterprise
Example
{
"type": "ir.actions.act_window",
"res_model": "res.partner",
"views": [[False, "list"], [False, "form"]],
"domain": [["customer", "=", True]],
}

Enterprise
URL actions open a URL in a new window or current window.
They are useful for linking to external sites or files. Key
parameters:
● url: The address to open.
● target (default: new): Specifies how the URL is opened
(new, self, or download).
URL Actions (ir.actions.act_url)

Enterprise
Example
{
"type": "ir.actions.act_url",
"url": "https://odoo.com",
"target": "self",
}

Enterprise
Server actions execute Python code or create records on the
server side. Key parameters:
● name: Identifies the action in logs.
● model_id: The model on which the action runs.
● state: Set to "code" for executing Python code.
● code: Contains the action's logic, typically Python code.
Server Actions (ir.actions.server)

Enterprise
Example
<record model="ir.actions.server" id="print_instance">
<field name="name">Res Partner Server Action</field>
<field name="model_id" ref="model_res_partner"/>
<field name="state">code</field>
<field name="code">
raise Warning(record.name)
</field>
</record>

Enterprise
Client actions trigger functionality on the client side, such as UI actions
or launching applications like POS. Key parameters:
● type: Set to "ir.actions.client".
● tag: The client-side identifier for the action.
● params (optional): Additional data sent with the action.
● target (optional): Determines display location (current, fullscreen,
or new).
Client Actions (ir.actions.client)

Enterprise
Example
{
"type": "ir.actions.client",
"tag": "pos.ui"
}

Enterprise
Report actions generate reports in formats like PDF or HTML,
typically accessed under the "Print" menu. Key parameters:
● name: Name of the report
● model: Model the report is based on.
● report_type: Format of the report (e.g., "qweb-pdf").
● report_name: External ID of the QWeb template used.
● report_file: Filename for the report.
● paperformat_id: Custom paper format for the report (e.g.,
"hr_skills.paperformat_resume").
● print_report_name: Dynamic report name (e.g., 'CV - %s' %
(object.name)).
● binding_model_id: Prevents display under "Print" menu (eval="False").
Report Actions (ir.actions.report)

Enterprise
Example
<record id="action_report_project" model="ir.actions.report">
<field name="name">Project Report</field>
<field name="model">project.project</field>
<field name="report_type">qweb-pdf</field>
<field name="report_name">
Module_name.project_report_template
</field>
<field name="binding_model_id" ref="model_project_project"/>
</record>

Enterprise
Scheduled actions, or automated actions, run at set intervals to
perform tasks like sending reports or updating records. They
automate repetitive processes, reducing manual work. Key
parameters:
● name: Name of the scheduled action.
● interval_number: Number of interval units between
executions.
● interval_type: Unit of measure (e.g., minutes, hours, days).
● model_id: The model on which the action is executed.
● code: The action's logic, typically a method call
Scheduled Actions (ir.cron)

Enterprise
Example
<record id="ir_cron_send_report" model="ir.cron">
<field name="name">Send Monthly Sales Report</field>
<field name="model_id" ref="model_sale_order"/>
<field name="state">code</field>
<field name="code">
model.send_monthly_sales_report()
</field>
<field name="interval_number">1</field>
<field name="interval_type">months</field>
<field name="user_id" ref="base.user_root"/>
<field name="active" eval="True"/>
</record>

Enterprise
In brief, Actions are used to define specific operations or
behaviors that can be triggered by users or the system. These
actions help in navigating, performing tasks, or executing logic in
the Odoo interface.
Conclusion

For More Info.
Check our company website for related blogs
and Odoo book.
Check our YouTube channel for
functional and technical videos in Odoo.
Enterprise
www.cybrosys.com

Types of Actions in Odoo 18 - Odoo Slides

Recommended

More Related Content

Similar to Types of Actions in Odoo 18 - Odoo Slides (20)

More from Celine George (20)

Recently uploaded (20)

Types of Actions in Odoo 18 - Odoo Slides