Development on Janik von Rotz

Odoo Development: Settings fields for your module

Wed, 28 Aug 2024 16:41:29 +0200

Odoo modules store their settings on the settings page. The fields definitions for the settings are different from the module. These fields can be mapped with system parameters. I would like to show how you can add settings field for your Odoo module.

In this case we have a module meilisearch_base that connects to the Meilisearch API. We store the API url and key in the settings page.

Lets get started by adding new fields to the res.config.settings model.

res_config_settings.py

from odoo import fields, models


class ResConfigSettings(models.TransientModel):
    _inherit = "res.config.settings"

    module_meilisearch_base = fields.Boolean("Integrate with Meilisearch")
    meilisearch_api_url = fields.Char(
        "Meilisearch API Url", config_parameter="meilisearch.api_url"
    )
    meilisearch_api_key = fields.Char(
        "Meilisearch API Key", config_parameter="meilisearch.api_key"
    )

When the module meilisearch_base is installed the field module_meilisearch_base is true. Setting the field value to false will uninstall the module.

The settings field have config_parameter attribute. Setting a field value will automatically create a key/value entry in the ir.config_parameter table.

To display the the settings field we will extend the base_setup.res_config_settings_view_form.

res_config_settings_view.xml

<?xml version="1.0" encoding="utf-8"?>
<odoo>
    <record id="res_config_settings_view_form" model="ir.ui.view">
        <field name="name">meilisearch_base.res_config_settings_view_form</field>
        <field name="model">res.config.settings</field>
        <field name="inherit_id" ref="base_setup.res_config_settings_view_form" />
        <field name="arch" type="xml">
            <div name="integration" position="inside">

                <div
                    class="col-12 col-lg-6 o_setting_box"
                    id="meilisearch_base_setting"
                >
                    <div class="o_setting_left_pane">
                        <field name="module_meilisearch_base" />
                    </div>
                    <div class="o_setting_right_pane">
                        <label string="Meilisearch" for="module_meilisearch_base" />
                        <div class="text-muted">
                            Integrate with Meilisearch.
                        </div>
                        <div
                            attrs="{'invisible': [('module_meilisearch_base', '=', False)]}"
                        >
                            <div class="content-group mt16">
                                <label
                                    for="meilisearch_api_url"
                                    class="o_light_label"
                                />
                                <field name="meilisearch_api_url" />
                            </div>
                            <div class="content-group">
                                <label
                                    for="meilisearch_api_key"
                                    class="o_light_label"
                                />
                                <field name="meilisearch_api_key" />
                            </div>
                        </div>
                    </div>
                </div>

            </div>
        </field>
    </record>
</odoo>

The settings box is inserted in the integration section. To do so the module must depend on base_setup. This edit will produce this result:

The values can be loaded from a demo data file.

meilisearch_index_demo.xml

<odoo>

    <record id="demo_config_meilisearch_api_url" model="ir.config_parameter">
        <field name="key">meilisearch.api_url</field>
        <field name="value">http://meili01:7700</field>
    </record>

    <record id="demo_config_meilisearch_api_key" model="ir.config_parameter">
        <field name="key">meilisearch.api_key</field>
        <field name="value">test</field>
    </record>

    <record id="demo_index0" model="meilisearch.index">
        <field name="name">Countries</field>
        <field name="index_name">countries</field>
        <field name="model_id" ref="base.model_res_country" />
    </record>

</odoo>

The values are defined in the settings model but defined in the system parameter model. When opening the the system parameter you’ll find the entries.

Now using the config values in your code is simple. You call the system parameter model with sudo and retrive value by its key: self.env["ir.config_parameter"].sudo().get_param("meilisearch.api_url")

Here is an example:

meilisearch_index.py

import json
import logging

import meilisearch

from odoo import _, api, fields, models
from odoo.exceptions import UserError

_logger = logging.getLogger(__name__)


class MeilisearchIndex(models.Model):
    _name = "meilisearch.index"
    _description = "Meilisearch Index"

	...

    def get_meilisearch_client(self):
        icp = self.env["ir.config_parameter"].sudo()
        url = icp.get_param("meilisearch.api_url")
        api_key = icp.get_param("meilisearch.api_key")

        if not url or not api_key:
            raise UserError(
                _(
                    "Meilisearch URL and API key need to be configured in the system parameters."
                )
            )

        return meilisearch.Client(
            url=url,
            api_key=api_key,
            timeout=10,
        )

You can view the full code of this example here: https://github.com/Mint-System/Odoo-Apps-Connector/tree/16.0/meilisearch_base

Odoo Development: Tree view with custom styles

Mon, 26 Sep 2022 09:13:47 +0200

The Odoo UI cannot be customized as easy as reports and websites. Using modules we can easily inject custom CSS styles.

Here is an example where we set the width of an unlink button in a custom tree view.

views/bom.xml

<field name="part_ids" context="{'default_certificate_planer_bom_id': id}">
  <tree limit="200" class="button_width" delete="0">
	<field name="sequence" widget="handle"/>
	<field name="certificate_planer_part_id"/>
	<field name="designation"/>
	<button name="unlink" class="oe_edit_only oe_link" icon="fa-times" type="object" string="Remove"/>
  </tree>
</field>

The button has the name unlink and its parent tree elemnt has the CSS class button_width. The name and class are used as selectors in our custom CSS:

static/src/css/style.css

.button_width [data-name="unlink"] {
    width: 32px;
}

Make sure that the style.css file is added to the module manifest using the web.assets_backend as reference.

Odoo Development: Show last updated date above list view

Wed, 08 Jun 2022 10:01:06 +0200

Odoo runs various reports in the background. Some of these report take a while to finish and therefore seeing the last updated date is important. In a few steps I will show how you can add the last updated date to a list view.

First we need a placeholder for the date that is updated once the list view is loaded. Add the following list view button element to the Odoo module.

static/src/xml/listview_last_updated_date.xml

<?xml version="1.0" encoding="UTF-8"?>
<template xml:space="preserve">
  <t t-extend="ListView.buttons">
    <t t-jquery="div.o_list_buttons" t-operation="append">
      <div class="o_list_selection_box container_last_updated_on" t-if="widget.modelName == 'critical.forecast'">
        <i><strong>Last Updated On: <span class="container_last_updated_date"/></strong></i>
      </div>
    </t>
  </t>
</template>

Included the file in the __manifest__.py.

Next extend the JavaScript List Controller with the following file:

static/src/js/show_last_updated_date.js

odoo.define('$MODULE_NAME.show_last_updated_date', function (require) {
    "use strict"

    var ListController = require('web.ListController')
    var session = require('web.session')
    var ulang = session.user_context['lang'].replace('_','-')
    
    ListController.include({
        renderButtons: function($node) {
            this._super(...arguments)
            if(this.$buttons.find('.container_last_updated_on').length) {
                this.set_last_update_date()
            }
         },
         updateButtons() {
            this._super(...arguments)
            if(this.$buttons.find('.container_last_updated_on').length) {
                this.set_last_update_date()
            }
        },
        set_last_update_date: function () {
            return this._rpc({
                model: this.modelName,
                method: 'search_read',
                args: [[], ['write_date']],
                kwargs: {
                    limit: 1,
                },
            }).then((result) => {
				if (result.length > 0) {
                    var write_date = new Date(result[0].write_date)
                    write_date = new Date(write_date.setMinutes(write_date.getMinutes() - write_date.getTimezoneOffset()))
                    if (result.length) {
                        this.$buttons.find('.container_last_updated_on').removeClass('d-none')
                        this.$buttons.find('.container_last_updated_date').text(write_date.toLocaleString(ulang))
                    } else {
                        this.$buttons.find('.container_last_updated_on').addClass('d-none')
                    }
                }
            })
        },
    })
})

This extension will retrieve the last write date of the current model, convert it to the users timezone and locale and then display it in the placeholder.

The JavaScript file must be included in the assets backend template.

<template id="button_render_js" inherit_id="web.assets_backend">
	<xpath expr="." position="inside">
		<script src="$MODULE_NAME/static/src/js/show_last_updated_date.js" type="text/javascript"/>
	</xpath>
</template>

Once these files are in place, the last write of the model records should be set automatically.

Odoo Development: Show message dialog

Tue, 01 Feb 2022 09:21:25 +0100

Some things are easily done in the Odoo framework, others are more difficult. An easy thing such as opening a dialog window with a custom message is more difficult than expected.

This example is based on the Odoo App Certificate Planner.

In this scenario there is a method store_tpi_report that generates two pdf reports. Once the reports is generated a message as showed below is displayed:

The first thing that is required is the dialog window definition.

views/document.xml

  ...

  <record id="document_message" model="ir.ui.view">
      <field name="name">Document Message</field>
      <field name="model">certificate_planer.document.message</field>
      <field name="arch" type="xml">
          <form>
              <field name="message" readonly="True"/>
              <footer>
                  <button name="action_close" string="Ok" type="object" default_focus="1" class="oe_highlight"/>
              </footer>
          </form>
      </field>
  </record>

</odoo>

There is a message field and a close button.

The method returns an action that shows the dialog.

models/document.py

...

class Document(models.Model):

    ...
    
    def store_tpi_report(self):
        self.ensure_one()

        # Render report
        pdf_content, content_type = self.env.ref('certificate_planer.tpi_report').render_qweb_pdf(self.id)
        pdf_content, content_type = self.env.ref('certificate_planer.mdl_report').render_qweb_pdf(self.id)

        # Return message
        message_id = self.env['certificate_planer.document.message'].create({'message': 'The reports have been generated. See attachments of this documents.'})
        return {
            'name': 'Message',
            'type': 'ir.actions.act_window',
            'view_mode': 'form',
            'res_model': 'certificate_planer.document.message',
            'res_id': message_id.id,
            'target': 'new'
        }
...

The Document Message requires a class definition.

models/document.py

...

class DocumentMessage(models.TransientModel):
    _name = 'certificate_planer.document.message'
    _description = "Show Message"

    message = fields.Text(required=True)

    def action_close(self):
        return {'type': 'ir.actions.act_window_close'}

The action_close method returns another action. To reload the page us this definition:

    def action_close(self):
        return {   
            'type': 'ir.actions.client',
            'tag': 'reload'
        }

Of course the Document Message form can be reused. Simply create the message object and return the action to call the form.

Odoo Development: Set attributes conditionally

Wed, 24 Nov 2021 14:06:11 +0100

Attributes such as invisible can be set on fields, widgets and buttons based on a condition. By using the attrs attribute the field and condition can be passed to the element. Here is an example: attrs="{'invisible': [('active', '=', True)]}".

But how do we achive this for tree elements where attrs is not available?

The solution is simple, we are adding a inherited view that sets the property conditionally. In our scenario we want to enable the delete action only if a user is member of a specific group.

This example is based on the Odoo App Certificate Planner.

First set the delete property of tree element to false.

views/specification.xml

<odoo>
	
  <record model="ir.ui.view" id="specification_list">
    <field name="name">Specification List</field>
    <field name="model">certificate_planer.specification</field>
    <field name="arch" type="xml">
      <tree limit="200" delete="false">
        <field name="name"/>
      </tree>
    </field>
  </record>

  ...

Then add an inherited record.

  ...

  <record id="specification_delete_rule" model="ir.ui.view">
    <field name="name">specification_delete_rule</field>
    <field name="groups_id" eval="[(4,ref('group_certificate_planer_administrator'))]"/>
    <field name="model">certificate_planer.specification</field>
    <field name="inherit_id" ref="specification_list"/>
    <field name="arch" type="xml">
      <xpath expr="//tree" position='attributes'>
        <attribute name='delete'>true</attribute>
      </xpath>
    </field>
  </record>

</odoo>

With this strategy an condition can be applied to any view element.

Odoo Development: Group by related field

Wed, 29 Sep 2021 08:24:59 +0200

The Odoo ORM provides a read_group method. Calling this method and passing a domain definition, fieldnames and a groupby fieldname will return a domain recordset grouped by the fieldname. A big drawback is that you cannot pass a relation to a subfield. Importing the itertools library gives us new options to do so.

The examples are based on the Odoo App Certificate Planner.

In our scenario we have these models and relations:

change 1:n> document revision n:1> document n:1> document type n:1> document class

For each change we want to get all document revisions grouped by the document class.

The data aggregation happens inside a report. We assume that we already have a list of changes. In the code snippet below the document revisions are group by the related field .document_id.type_id.class_id.name using the itertools.groupby method and a lambda function.

_logger = logging.getLogger(__name__)
import itertools
...

class MDLReport(models.AbstractModel):
	_name = 'report.certificate_planer.mdl_report'
	_description = 'Certificate Planner MDL Report'
		...
		
        # Get documents by change
        change_revisions = {}
        for change in changes:
            change_revisions[change.id] = {}
            # Group document revisions by document > document type > document class
            for key, items in itertools.groupby(change.revision_ids, lambda r: r.document_id.type_id.class_id.name):
                change_revisions[change.id][key] = list(items)
				
		_logger.info(change_revisions[change.id])
		
		...

The groupby method returns the a list of keys and its grouped items. Use list() to have ORM access on the list objects.

The change_revisions contains a key for each change id with a key of the group name as value. The group name key has the grouped items as value.

See the logger output for details:

odoo.addons.certificate_planer.report.mdl_report: {'Certification Document': [certificate_planer.document_revision(32676,), certificate_planer.document_revision(32882,), certificate_planer.document_revision(32515,), certificate_planer.document_revision(32684,), certificate_planer.document_revision(32685,)]}
odoo.addons.certificate_planer.report.mdl_report: {'Certification Document': [certificate_planer.document_revision(34451,), certificate_planer.document_revision(34453,), certificate_planer.document_revision(29489,), certificate_planer.document_revision(30137,), certificate_planer.document_revision(34454,)]}
odoo.addons.certificate_planer.report.mdl_report: {'Certification Document': [certificate_planer.document_revision(34592,), certificate_planer.document_revision(30049,), certificate_planer.document_revision(30051,), certificate_planer.document_revision(30055,)]}
odoo.addons.certificate_planer.report.mdl_report: {'Compliance Document': [certificate_planer.document_revision(32111,)], False: [certificate_planer.document_revision(31306,)]}
odoo.addons.certificate_planer.report.mdl_report: {'Certification Document': [certificate_planer.document_revision(30669,), certificate_planer.document_revision(30840,), certificate_planer.document_revision(30682,), certificate_planer.document_revision(31251,), certificate_planer.document_revision(31252,)]}

Iterate over data structure is easy in qweb:

<t t-foreach="changes" t-as="change">
	<t t-foreach="change_revisions[change.id]" t-as="document_class">
		<span t-esc="document_class"/>
		<t t-foreach="document_class_value" t-as="revision">
			<span t-field="revision.document_id"/>
		</t>
	</t>
</t>

Note that using the foreach clause on a dictionary will set a $as variable with the key and a $as_value with its value.

Odoo Development: Create a settings page

Tue, 14 Sep 2021 16:36:23 +0200

Odoo stores all module settings in the res.config.settings model. This model is based on the models.TransientModel class, which means that the settings data is not persisted with this model.

This is just nice to know. I will show how you can create a settings page for your Odoo module and let you know about its limitations.

The examples are based on the Odoo App Certificate Planner.

We are going to complete four actions:

Inherit the settings model
Add settings view
Add settings menu and action
Get the settings param

Inherit the settings model

Creating new settings fields is simple. Inherit the res.config.settings model and add new fields.

models/res_config_settings.py

from odoo import fields, models


class ResConfigSettings(models.TransientModel):
    _inherit = 'res.config.settings'

    title_page_text = fields.Char(string='Title Page Text',
        config_parameter='certificate_planer.title_page_text',
        default="This document contains confidential information and is proprietary to Example.")
    
    footer_text = fields.Char(string='Footer Text',
        config_parameter='certificate_planer.footer_text',
        default="Copyright by Example")

Not the config_parameter attributes. This will ensure that the fields value is also stored in the ir.config_parameter model.

In our example we have two configurable text fields. The usage of field types are limited to boolean, integer, float, char, selection or many2one.

Add settings view

Next we create the settings view.

views/res_config_settings.xml

<?xml version="1.0" encoding="utf-8" ?>
<odoo>

    <record id="res_config_settings_view_form" model="ir.ui.view">
        <field name="name">certificate_planer.res.config.settings.form</field>
        <field name="model">res.config.settings</field>
        <field name="inherit_id" ref="base.res_config_settings_view_form" />
        <field name="arch" type="xml">
            <xpath expr="//div[hasclass('settings')]" position="inside">
                <div class="app_settings_block" data-string="Certificate Planner" string="Certificate Planner" data-key="certificate_planer">
                    
                    <h2>Demand Planner</h2>
                    <div class="row mt16 o_settings_container" id="certificate_planer_setting_container">
                        <div class="col-12 col-lg-12 o_setting_box" id="certificate_planer_text_block">
                            
                            <div class="o_setting_right_pane">
                                <div class="text-muted">
                                    Text blocks for MDL report.
                                </div>
                                <div class="content-group">

                                    <div class="row mt16">
                                        <label class="col-lg-3 o_light_label" string="Title Page Text" for="title_page_text"/>
                                        <field name="title_page_text" class="oe_inline" style="width: 70% !important;"/>
                                    </div>

                                    <div class="row mt16">
                                        <label class="col-lg-3 o_light_label" string="Footer Text" for="footer_text"/>
                                        <field name="footer_text" class="oe_inline" style="width: 70% !important;"/>
                                    </div>

                                </div>
                            </div>

                        </div>
                    </div>

                </div>
            </xpath>
        </field>
    </record>

</odoo>

Wow, that’s very bloated. This view definition describes the settings menu on the left side and the parameters on the right side of the settings page. Orient yourself by having a look at the rendered page:

We have the setting fields and the view, now we can add an action that opens the settings view and a menu entry to call the action.

views/menu.xml

<odoo>
  ...

  <record id="settings_action" model="ir.actions.act_window">
    <field name="name">Settings</field>
    <field name="type">ir.actions.act_window</field>
    <field name="res_model">res.config.settings</field>
    <field name="view_mode">form</field>
    <field name="target">inline</field>
    <field name="context">{'module': 'certificate_planer'}</field>
  </record>
  ...

  <menuitem name="Settings"
    id="settings_menu"
    sequence="0"
    parent="certificate_planer.configuration_menu"
    action="certificate_planer.settings_action"/>
  ...

</odoo>

Get the settings param

Finally, I’ll give you an example on how to retrieve a stored settings value.

report/document_report.py

return {
	...
	'title_page_text': self.env['ir.config_parameter'].sudo().get_param('certificate_planer.title_page_text'),
	'footer_text': self.env['ir.config_parameter'].sudo().get_param('certificate_planer.footer_text')
}

The settings values are stored in the ir.config_parameter model. Access permission checks must be skipped by using sudo(). The get param name is equal to config_parameter attribute of the field definition.

Odoo Development: Enable multi edit

Tue, 14 Sep 2021 13:19:22 +0200

With Odoo 13 an new attribute was introduced to the tree view that enables editing multiple rows at once.

Enable mutli edit is very simple. Simply add multi_edit="1" to the <tree> tag. Here is an example:

  ...
  <record model="ir.ui.view" id="document_class_list">
    <field name="name">Document Class List</field>
    <field name="model">certificate_planer.document_class</field>
    <field name="arch" type="xml">
      <tree limit="200" multi_edit="1">
        <field name="sequence" widget="handle"/>
        <field name="name"/>
        <field name="description"/>
        <field name="show_reason"/>
      </tree>
    </field>
  </record>
  ...

This tree viewwill provide multi edit for all fields. Check the records you want to update, set the value for one record and hit enter. A confirmation prompt will show up and asks wether you want to perform this action.

Note: Allowing mass editing can have side effects. Multiple records can be updated at will and if not tracked such a change will go unnoticed.

Odoo Development: Create a smart button with a counter

Thu, 26 Aug 2021 08:29:56 +0200

Smart buttons help navigating between linked models in Odoo. Creating a smart button requires three components: counter field, compute function, view action and a button box on the view.

The examples are based on the Odoo App Certificate Planner.

We are going to add a smart button to the form view of the change model. This requires a counter field on the model. We assume that the required relational fields already exists.

models/change.py

from odoo import models, fields

class Change(models.Model):
    ...
	
    revision_count = fields.Integer(compute='_compute_revision_count')
	...
	
	revision_ids = fields.One2many("certificate_planer.document_revision", "change_id", string="Document Revisions")
	...
	
	def _compute_revision_count(self):
        for record in self:
            record.revision_count = len(self.revision_ids)
	...
	
	def view_revision_ids(self):
        self.ensure_one()
        return {
            "type": "ir.actions.act_window",
            "name": "Document Revisions",
            "view_mode": "tree,form",
            "res_model": "certificate_planer.document_revision",
            "domain": [("change_id", "=", self.id)],
            "context": "{'create': False}",
        }

So in order to have a smart button four things are required:

counter field
relation field to count
count compute function
view action for the smart button

The change on the form view simple.

views/change.xml

<odoo>
  ...

  <record model="ir.ui.view" id="change_form">
    <field name="name">Change Form</field>
    <field name="model">certificate_planer.change</field>
    <field name="arch" type="xml">
      <form string="Change Form">
        ...
        <sheet>
          <div class="oe_button_box" name="button_box">
            <button name="view_revision_ids" type="object" class="oe_stat_button" icon="fa-files-o">
              <field string="Document Revisions" name="revision_count" widget="statinfo"/>
            </button>
          </div>
          ...
        </sheet>
      </form>
    </field>
  </record>

</odoo>

Simply add the button box div after <sheet> tag. The result in this case is:

Odoo Development: Prevent deletion with custom constraint

Mon, 26 Jul 2021 10:09:50 +0200

By default Odoo asks for confirmation if a record is being deleted. Making validations before deletion is up to the developer. I will show how you can add a custom constraint that prevents a record being deleted.

The examples are based on the Odoo App Certificate Planner.

In our scenario a record from model post_certification_item can only be deleted if the field change_id is not set.

Extend the default unlink (aka delete) method.

models/post_certification_item.py

from odoo import models, fields
from odoo.exceptions import UserError

class PostCertificationItem(models.Model):
    ...
	
    def unlink(self):
        if self.change_id:
            raise UserError(_('You cannot delete a Post Certification Item that links to a Change.'))
        return super(PostCertificationItem, self).unlink()

If you try to delete a record that links to a change and confirm the prompt, this message will pop up:

Odoo Development: Add archiving functionality

Mon, 26 Jul 2021 09:58:30 +0200

Odoo has a builtin archiving function for any model. Once a record is archived it will not be displayed in any views and selections, but can is easily be unarchived. This functionality ensures that relations must not be removed if linked records is obsolete.

The examples are based on the Odoo App Certificate Planner.

We are going to add the archiving function to our model change_status. First simply add the well-known field active to the model class.

models/change_status.py

from odoo import models, fields, api, _

class ChangeStatus(models.Model):
    ...
	
    active = fields.Boolean(default=True)

This will enable the archive functionality.

If you have a custom search and form view, ensure that the archive filter is displayed.

views/change_status.xml

<odoo>

  <record model="ir.ui.view" id="change_status_search">
    <field name="name">Change Status Search</field>
    <field name="model">certificate_planer.change_status</field>
    <field name="arch" type="xml">
      <search>
        <field name="designation"/>
        <filter string="Archived" name="inactive" domain="[('active', '=', False)]"/>
      </search>
    </field>
  </record>
	
  ...

And show a ribbon if the record shown is archived.

  ...

  <record model="ir.ui.view" id="change_status_form">
    <field name="name">Change Status Form</field>
    <field name="model">certificate_planer.change_status</field>
    <field name="arch" type="xml">
      <form string="Change Status Form">
        <sheet>
          <widget name="web_ribbon" title="Archived" bg_color="bg-danger" attrs="{'invisible': [('active', '=', True)]}"/>
          <field name="active" invisible="1"/>
	      ...

The form and list actions to archive and unarchive the records will be generated automatically.

Odoo Development: Configurable Kanban state

Wed, 14 Jul 2021 13:32:44 +0200

With the Odoo framework it is pretty easy to create a kanban view that groups and sorts an item by a state field. I’ll show how a kanban view can be added in a few steps.

The examples are based on the Odoo App Certificate Planner.

We are going to create a configurable state for our model change. First create a model that defines the state.

models/change_status.py

from odoo import models, fields, api, _

class ChangeStatus(models.Model):
    _name = 'requirement.change_status'
    _description = 'Requirement Change Status'
    _rec_name = 'designation'
    _order = 'sequence'

    # fields
    designation = fields.Char()
    sequence = fields.Integer()

And add views for the new model.

views/change_status.xml

<odoo>

  <record model="ir.ui.view" id="change_status_search">
    <field name="name">Change Status Search</field>
    <field name="model">Requirement.change_status</field>
    <field name="arch" type="xml">
      <search>
        <field name="designation"/>
      </search>
    </field>
  </record>

  <record model="ir.ui.view" id="change_status_list">
    <field name="name">Change Status List</field>
    <field name="model">Requirement.change_status</field>
    <field name="arch" type="xml">
      <tree limit="200">
        <field name="sequence" widget="handle"/>
        <field name="designation"/>
      </tree>
    </field>
  </record>

  <record model="ir.ui.view" id="change_status_form">
    <field name="name">Change Status Form</field>
    <field name="model">requirement.change_status</field>
    <field name="arch" type="xml">
      <form string="Change Status Form">
        <sheet>
          <p>Change Status</p>
          <div class="oe_title">
            <div class="oe_edit_only">
              <label for="designation"/>
            </div>
            <h1>
              <field name="designation"/>
            </h1>
          </div>
          <p>Last edit by <field name="write_uid"/> on <field name="write_date"/>.<br/>
          Created by <field name="create_uid"/> on <field name="create_date"/>.</p>
        </sheet>
      </form>
    </field>
  </record>

</odoo>

Ensure that security groups and menu entries exist for the model.

Next we add a reference to the change model.

models/change.py

class Change(models.Model):
	status_id = fields.Many2one("requirement.change_status", track_visibility="always", ondelete='restrict')

This field should be tracked and also creates a constraint that prevents the referenced status from being deleted.

Create a kanban view and display the statusbar in the form view.

views/change.xml

  <record model="ir.ui.view" id="change_kanban" >
    <field name="name">Change Kanban</field>
    <field name="model">requirement.change</field>
    <field name="arch" type="xml">
      <kanban default_group_by="status_id" class="o_kanban_small_column">
        <field name="change_id_id"/>
        <field name="certificate_id"/>
        <templates>
        <t t-name="kanban-box">
          <div class="oe_kanban_card oe_kanban_global_click">
            <div class="oe_kanban_content">
              <strong>
                <field name="change_id_id"/>
              </strong>
              <field name="certificate_id"/>
            </div>
          </div>
        </t>
        </templates>
      </kanban>
    </field>
  </record>

  <record model="ir.ui.view" id="change_form">
    <field name="name">Change Form</field>
    <field name="model">requirement.change</field>
    <field name="arch" type="xml">
      <form string="Change Form">
        <header>
          <field name="status_id" widget="statusbar" options="{'clickable': '1'}"/>
        </header>
        <sheet>

This wil result in the following UI.

New states can be added and removed. The statusbar to set the state appears on the top right of the form.

Odoo Development: Add activity button

Wed, 14 Jul 2021 10:07:47 +0200

The activity button is part of the chatter. Every model form can have activities. I will show how you can enable the activity button for your model form using the mixin class.

The examples are based on the Odoo App Certificate Planner.

First inherit the classes in your model.

models/change.py

class Change(models.Model):
	_inherit = ['mail.thread', 'mail.activity.mixin']

Next update the form.

views/change.xml

        </sheet>
        <div class="oe_chatter">
          <field name="message_follower_ids" widget="mail_followers"/>
          <field name="message_ids" widget="mail_thread"/>
          <field name="activity_ids" widget="mail_activity"/>
        </div>
      </form>
    </field>
  </record>

</odoo>

And you will see the message and activity buttons on your form.

Develop business applications with Odoo

Mon, 07 Dec 2020 15:59:44 +0100

In Odoo, various applications are packaged, which work together, but also standalone. For example, the Contact app stores all address data of the company. The Human Resources application for managing employees or the CRM access this address data.

Technical features such as access management, report generation, data management or analyses are also packaged under a uniform Odoo interface. These features can be used by software developers without development effort. New applications or extensions to existing apps can be developed in a flash.

So Odoo not only is an ERP system, but also a development framework. With Odoo, customized applications can be developed based on a robust framework.

Example

My company Mint System accompanied a customer who has been using a Microsoft Access application for several years. The application has become outdated and is no longer supported by the latest Microsoft Office version.

Within the frame of an development project the existing application has been replaced by a new one. This procedure has been applied:

Analysis of the existing data structure
Document existing work processes
Design of a new data model based on Odoo
Development of data migration scripts
Requirements engineering for the new app
Iterative development of the new Odoo app
Replacement of the existing application and project completion

In just a few steps, we can migrate a legacy application to a state-of-the-art browser app.

Advantages

Development frameworks are a dime a dozen. What are the advantages of developing with the Odoo framework?

User and access management through Odoo

Solutions for user and group management are already provided by Odoo. Integrating the application into the ActiveDirectory or an authentication solution with OAuth is possible without any challenges.

Association with existing Odoo entities

Odoo manages several hundreds of business objects like project, tasks, working hours, employees, invoices, cost centers or messages. Each of these objects can be linked to the cusotm development.

Predefined elements for the user interface

Odoo offers different views for the data to be displayed: Lists, Graphs, Kanban, Pivot, Grid, Gantt or Map. These views can be adopted for your own data.

Mobile Support

All Odoo apps work on mobile devices. The developer does not have to develop a responsive design.

Security and robustness

Odoo is used by thousands of companies. From SMEs to large companies. Correspondingly many security bugs have been closed, experiences in productive environment gathered and internal company data collected. Odoo is a secure and proven framework for business applications.

Install Ubuntu development libraries

Tue, 25 Mar 2014 11:42:14 +0000

This post is part of my Your own Virtual Private Server hosting solution project.
Get the latest version of this article here: https://gist.github.com/9758712.

Introduction

This is a list of essential tools for developing with Ubuntu.

Requirements

Ubuntu server

Installation

build-essential

This package contains an informational list of packages which are considered essential for building Debian packages.

sudp apg-get install build-essential

libcurl4-gnutls-dev

These files (ie. includes, static library, manual pages) allow to build software which uses libcurl.

sudo apt-get install libcurl4-gnutls-dev

libgeoip-dev

GeoIP is a C library that enables the user to find the country that any IP address or hostname originates from. It uses a file based database.

sudo apt-get install libgeoip-dev

libopenssl-ruby

This package makes Ruby to be able to use OpenSSL.

sudo apt-get install libopenssl-ruby

libxml2

This package provides a library providing an extensive API to handle XML data files.

sudo apt-get install libxml2

libxml2-dev

Install this package if you wish to develop your own programs using the GNOME XML library.

sudo apt-get install libxml2-dev

libxslt1-dev

This package contains the development files libxslt.

sudo apt-get install libxslt1-dev

ruby-dev

This package provides the header files, necessary to make extension library for Ruby.

sudo apt-get install ruby-dev

Update Hostfile with Chrome/Firefox Plugin

Mon, 10 Mar 2014 10:56:12 +0000

Domain-ip mapping is essential in developing new websites as you have to test URLs without changing DNS entries.

Yet I’ve always update the local host file which requires in most cases a restart of the browser. This is a busy an troublesome issue.

Luckily there’s for everything a plugin, tool or script, this also goes for host file updates via Chrome/Firefox plugin.

The HostAdmin plugin enables you to update the local host file in you browser in real time without the need to restart the browser. This plugins saves a lot of time when switching domain-ip mappings for different environments.

Here’s a screenshot of the Chrome extension which shows how easy it is to switch on/off an domain-ip mapping.

Development on Janik von Rotz

Odoo Development: Settings fields for your module

Odoo Development: Tree view with custom styles

Odoo Development: Show last updated date above list view

Odoo Development: Show message dialog

Odoo Development: Set attributes conditionally

Odoo Development: Group by related field

Odoo Development: Create a settings page

Inherit the settings model

Add settings view

Add settings menu and action

Get the settings param

Odoo Development: Enable multi edit

Odoo Development: Create a smart button with a counter

Odoo Development: Prevent deletion with custom constraint

Odoo Development: Add archiving functionality

Odoo Development: Configurable Kanban state

Odoo Development: Add activity button

Develop business applications with Odoo

Example

Advantages

Install Ubuntu development libraries

Introduction

Requirements

Installation

build-essential

libcurl4-gnutls-dev

libgeoip-dev

libopenssl-ruby

libxml2

libxml2-dev

libxslt1-dev

ruby-dev

Update Hostfile with Chrome/Firefox Plugin