Jorge Pinna PuissantandMichael Mattiello (mcm)
c7c2959449
The aim of this commit is to simplify and standardize the settings archs.
To do this, a small DSL exclusively for the settings was created. This
new DSL introduces 3 tags: `app`, `block` and `setting`.
The `app` tag is used to declare the application on the settings view.
It creates an entry with its logo on the sidebar of the view. It also
acts as delimiter when searching.
```xml
<app string="CRM" name="crm">
...
</app>
```
- `string` : The "display" name of the application.
- `name` : The technical name of the application (the name of the module).
- `logo` *optional* : The relative path to the logo. If not set, the
logo is created using the `name` parameter :
`/{name}/static/description/icon.png`.
The `block` tag is used to declare a group of settings. This group can
have a title and a description/help.
```xml
<block title="Title of group Bar">
...
</block>
```
- `title` *optional* : The title of the block of settings (the old h2),
you can perform research on its text.
- `help` *optional* : The description/help of the block of settings
(the old h3), you can perform research on its text.
The `setting` tag is used to declare the setting itself. The first field
in the setting is used as the main field (optional). This field is
placed on the left panel (if it's a boolean field) or on the top of the
right panel (otherwise). The field is also used to create the setting
label if a `string` is not defined. The `setting` tag can also contain
more elements (e.g. html), all of these elements are rendered in the
right panel.
```xml
<setting string="this is bar">
<field name="bar"/>
...More elements
</setting>
```
- `type` *optional* : By default, a setting is visually separated on two
panels (left and right), and is used to edit a given field. By
defining `type='header'`, a special kind of setting is rendered
instead. This setting is used to modify the scope of the other
settings. For example, on the website application, this setting
is used to indicate to which website the other settings apply.
The header setting is visually represented as a yellow banner on
the top of the screen.
- `string` *optional* : The text used as label of the setting. If it's
not defined, the first field is used as label.
- `title` *optional* : The text used as tooltip.
- `help` *optional* : The help/description of the setting. This text is
displayed just below the setting label (with classname
`text-muted`).
- `company_dependent` *optional* : If this attribute is set to "1" an
icon is displayed next to the setting label to explicit that
this setting is company-specific.
- `documentation` *optional* : If this attribute is set, an icon is
added next to the setting label, this icon is a link to the
documentation. Note that you can use relative or absolute path.
The relative path is relative to
`https://www.odoo.com/documentation/server_version`, so it's not
necessary to hard-code the server version on the arch anymore.
closes odoo/odoo#106425
Task-id: 3081367
Related: odoo/enterprise#34337
Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
Co-authored-by: "Michael Mattiello (mcm)" <mcm@odoo.com>
89 lines
6.7 KiB
XML
89 lines
6.7 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data>
|
|
<record id="res_config_settings_view_form" model="ir.ui.view">
|
|
<field name="name">res.config.settings.view.form.inherit.mrp</field>
|
|
<field name="model">res.config.settings</field>
|
|
<field name="priority" eval="35"/>
|
|
<field name="inherit_id" ref="base.res_config_settings_view_form" />
|
|
<field name="arch" type="xml">
|
|
<xpath expr="//form" position="inside">
|
|
<app data-string="Manufacturing" string="Manufacturing" name="mrp" groups="mrp.group_mrp_manager">
|
|
<block title="Operations" name="process_operations_setting_container">
|
|
<setting id="work_order" string="Work Orders" help="Process operations at specific work centers" documentation="/applications/inventory_and_mrp/manufacturing/management/bill_configuration.html#adding-a-routing" title="Work Order Operations allow you to create and manage the manufacturing operations that should be followed within your work centers in order to produce a product. They are attached to bills of materials that will define the required components.">
|
|
<field name="group_mrp_routings"/>
|
|
<field name="module_mrp_workorder" invisible="1"/>
|
|
<div id="workorder_settings_workcenters" class="content-group" attrs="{'invisible': [('group_mrp_routings','=',False)]}">
|
|
<div class="mt8">
|
|
<div>
|
|
<button name="%(mrp.mrp_workcenter_action)d" icon="fa-arrow-right" type="action" string="Work Centers" class="btn-link"/>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div id="workorder_settings_dependencies" class="row mt-2" attrs="{'invisible': [('group_mrp_routings','=',False)]}">
|
|
<field name="group_mrp_workorder_dependencies" class="col-lg-1 mr0"/>
|
|
<div class="col ps-0">
|
|
<label for="group_mrp_workorder_dependencies"/>
|
|
<div class="text-muted">
|
|
Set the order that work orders should be processed in. Activate the feature within each BoM's Miscellaneous tab
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</setting>
|
|
<setting help="Subcontract the production of some products" documentation="/applications/inventory_and_mrp/manufacturing/management/subcontracting.html">
|
|
<field name="module_mrp_subcontracting"/>
|
|
</setting>
|
|
<setting id="quality_control_mrp" help="Add quality checks to your work orders">
|
|
<field name="module_quality_control" widget="upgrade_boolean"/>
|
|
<div class="row mt-2" attrs="{'invisible': [('module_quality_control','=',False)]}">
|
|
<field name="module_quality_control_worksheet" widget="upgrade_boolean" class="col-lg-1 ml16 mr0"/>
|
|
<div class="col ps-0">
|
|
<label for="module_quality_control_worksheet"/>
|
|
<div class="text-muted">
|
|
Create customizable worksheets for your quality checks
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</setting>
|
|
<setting help="Allow manufacturing users to modify quantities to consume, without the need for prior approval" id="mrp_lock">
|
|
<field name="group_unlocked_by_default"/>
|
|
</setting>
|
|
<setting id="mrp_byproduct" help="Produce residual products (A + B -> C + D)" title="Add by-products to bills of materials. This can be used to get several finished products as well. Without this option you only do: A + B = C. With the option: A + B = C + D.">
|
|
<field name="group_mrp_byproducts"/>
|
|
</setting>
|
|
<setting id="mrp_reception_report" help="View and allocate manufactured quantities">
|
|
<field name="group_mrp_reception_report"/>
|
|
</setting>
|
|
</block>
|
|
<block title="Planning">
|
|
<setting id="mrp_mps" help="Plan manufacturing or purchase orders based on forecasts" documentation="/applications/inventory_and_mrp/manufacturing/management/use_mps.html" title="Using a MPS report to schedule your reordering and manufacturing operations is useful if you have long lead time and if you produce based on sales forecasts.">
|
|
<field name="module_mrp_mps" widget="upgrade_boolean"/>
|
|
</setting>
|
|
<setting id="security_lead_time" string="Security Lead Time" company_dependent="1" help="Schedule manufacturing orders earlier to avoid delays" documentation="/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.html">
|
|
<field name="use_manufacturing_lead"/>
|
|
<div class="content-group" attrs="{'invisible': [('use_manufacturing_lead','=',False)]}">
|
|
<div class="mt16" >
|
|
<field name="manufacturing_lead" class="oe_inline"/> days
|
|
</div>
|
|
</div>
|
|
</setting>
|
|
</block>
|
|
</app>
|
|
</xpath>
|
|
</field>
|
|
</record>
|
|
|
|
<record id="action_mrp_configuration" 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' : 'mrp', 'bin_size': False}</field>
|
|
</record>
|
|
|
|
<menuitem id="menu_mrp_config" name="Settings" parent="menu_mrp_configuration"
|
|
sequence="0" action="action_mrp_configuration" groups="base.group_system"/>
|
|
</data>
|
|
</odoo>
|