OCA modules for Odoo

This addon allows you to use Pydantic objects as params and/or response with your REST API methods.

Making revision(s) of a document is a common need across many area. This module does not provide a functionality by itself but an abstract model to implement revision capality in other models (e.g. purchase orders, sales orders, budgets, expenses...). Note: To be able to use this module in a new model you will need some development. See sale_order_revision as an example of implementation. Example with sale_order_revision installed, On a cancelled orders, you can click on the…

This module lets you add "Excluded Groups" for Record Rules (ir.rule), when getting the record rules for Groups (res.groups) anywhere, if the user has the group for which a certain rule that should be applying has this group as one of it's Excluded Groups, this record rule won't appply.

This module allows to define custom filters in the search views for an specific field belonging to the document or any other related document. This nature makes the definition quite technical, but once done, it adds the element in the UI for regular user use.

This addon provides the ability to create GIN or GiST indexes of char and text fields and also to use the search operator % in search domains. Currently this module doesn't change the backend search or anything else. It provides only the possibility to perform the fuzzy search for external addons.

This module adds the capability to find on any object (e.g. project issues or helpdesk ticket) based on the conversation threads associated to them. This will be useful in models that make intense use of messages, like project issues or helpdesk tickets. A project issue or helpdesk ticket can contain tens of mails or notes associated, based on the feedback that the person responsible for the ticket maintains, including conversations with the person that raised the issue. A…

This module allows to search multi value on tree view at once. Normal Case, you can search value one-by-one on tree view We just add 'value1' -> enter -> add 'value2' -> enter -> add 'value3' -> enter ... BUT If there are many value to search, it take a lot of time many and you can copy value from excel to search value easily. Note In case there is spacebar in value, it will multi search mistake i.e. 3 value is 'value 1', 'value 2' and 'value 3', you will search with {value…

This module extends the use of sequences. It will allow you to use them in any text field. If configured correctly, new records will have a default incremental value in the field of your choice.

This module allow user to add optional sequences to some document model. On which sequence is used, is based on domain matching with document values (and original sequence will be bypassed). For example, it is now possible to, · Avoid using Odoo automatic sequence on invoice and vendor bill with old style sequence. · Customer payment and vendor payment to run on different sequence. · Assign different sales order sequence based on customer region. This is a base module and…

This module provides a wizard to generate company-specific sequences from reusable sequence templates. It is designed for multi-company environments where each company requires its own ir.sequence records but shares a common configuration pattern. The wizard allows defining sequence templates that include dynamic placeholders referencing company fields. During generation, placeholders of the form %(company_id.)s are automatically replaced with the corresponding values from…

This module allow to store list in Serialized. This is a technical module

This module provide abstract models to manage customizable substates to be applied on different models (sale order, purchase, ...). example: · for the quotation state of a sale order we can define 3 substates "In negotiation", "Won" and "Lost". · We can also send mail when the substate is reached. It is not useful by itself. You can see an example of implementation in the 'purchase_substate' module. (purchase-workflow repository).

This module was written to allow you to call code with some uid while being sure no security checks (ir.model.access and ir.rule) are done. In this way, it's the same as sudo(), but the crucial difference is that the code still runs with the original user id. This can be important for inherited code that calls workflow functions, subscribes the current user to some object, etc. Usually, you'll be in in the situation to want something like this if you inherit from a module…

This module provides persistent access to technical features based on user preferences, eliminating the need to activate debug mode.

This module extends the functionality of company management. It allows you to bind a technical user on the company in order to use it in batch processes. The technical user must - be inactive to avoid login - be in the required groups depending of what you need to do

This module is a technical module that does nothing by itself. This addon allows to create temporary actions that will be removed automatically after one hour (default transient age limit). Temporary actions are identified by a field 'is_temporary'.

This module allows you to define territories, branches, districts and regions to be used for Field Service operations or Sales.

Validating some operations is a common need across different areas in a company and sometimes it also involves several people and stages in the process. With this module you will be able to define your custom validation workflows for any Odoo document. This module does not provide a functionality by itself but an abstract model to implement a validation process based on tiers on other models (e.g. purchase orders, sales orders, budgets, expenses...). Note: To be able to use…

This module adds an tier review board with form, tree, kanban, calendar, pivot, graph and search views.

Allows to add an authentication check to tier validation, where the user must confirm his authentication in order to approve or reject the tier review.