OdooWiki OCA HUB

Base Warn Option

base_warn_option folder_open OCA/server-ux open_in_new
Tools License: LGPL-3

This module extends the functionality of blocking messages to support more consistency between messages and to allow you to set a blocking message quickly.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets administrators create and manage a library of predefined warning and blocking messages, so the same wording is reused consistently across Odoo.

This module adds a new screen called Warn Options where you can store ready-made warning or blocking messages. Each option has a text (the message itself), an active flag, a usage setting (currently only 'All'), and a type that can be Warning, Block, or left empty to be valid for both.

You reach the screen from Settings, in the Companies section, via the 'Manage Warning Options' button. The list is editable directly, and you can search or group options by their allowed usage or type.

Regular users can only read the options; only system administrators can create, edit, or delete them. Archived options are hidden from normal use but can be restored.

The module does not change any other Odoo screen or business rule by itself; it only provides the shared list of messages that other modules can use when they need to show a warning or block an action.

Depends on

basebase_setup
Models and fields (1)
  • warn.option · new modelname, active, allowed_warning_type, allowed_warning_usage

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/server-ux.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.