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>
78 lines
4.9 KiB
XML
78 lines
4.9 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<record id="res_config_settings_view_form" model="ir.ui.view">
|
|
<field name="name">res.config.settings.view.form.inherit.hr</field>
|
|
<field name="model">res.config.settings</field>
|
|
<field name="priority" eval="70"/>
|
|
<field name="inherit_id" ref="base.res_config_settings_view_form"/>
|
|
<field name="arch" type="xml">
|
|
<xpath expr="//form" position="inside">
|
|
<app data-string="Employees" string="Employees" name="hr" groups="hr.group_hr_manager">
|
|
<block title="Employees" name="employees_setting_container">
|
|
<setting id="presence_control_setting" title="Presence of employees" string="Presence Control">
|
|
<div class="content-group" name="hr_presence_options">
|
|
<div class="d-flex">
|
|
<field name="module_hr_attendance" class="ml16"/>
|
|
<label for="module_hr_attendance" class="o_light_label"/>
|
|
</div>
|
|
<div class="d-flex">
|
|
<field name="hr_presence_control_login" class="ml16"/>
|
|
<label for="hr_presence_control_login" class="o_light_label"/>
|
|
</div>
|
|
</div>
|
|
</setting>
|
|
<setting id="presence_reporting_setting" help="Presence reporting screen, email and IP address control." title="Advanced presence of employees">
|
|
<field name="module_hr_presence"/>
|
|
<div class="d-flex mt-1" attrs="{'invisible': [('module_hr_presence', '=', False)]}">
|
|
<field name="hr_presence_control_email" class="ml16"/>
|
|
<label for="hr_presence_control_email" class="o_light_label"/>
|
|
</div>
|
|
<div class="d-flex ml32" attrs="{'invisible': ['|', ('module_hr_presence', '=', False), ('hr_presence_control_email', '=', False)]}">
|
|
<span class="flex-shrink-0 ml8 me-2">Minimum number of emails to send</span>
|
|
<field name="hr_presence_control_email_amount" class="ms-2 oe_inline"/>
|
|
</div>
|
|
<div class="d-flex" attrs="{'invisible': [('module_hr_presence', '=', False)]}">
|
|
<field name="hr_presence_control_ip" class="ml16"/>
|
|
<label for="hr_presence_control_ip" class="o_light_label"/>
|
|
</div>
|
|
<div class="d-flex ml32" attrs="{'invisible': ['|', ('module_hr_presence', '=', False), ('hr_presence_control_ip', '=', False)]}">
|
|
<span class="flex-shrink-0 ml8 me-2">IP Addresses (comma-separated)</span>
|
|
<field name="hr_presence_control_ip_list" class="ms-2 oe_inline"/>
|
|
</div>
|
|
</setting>
|
|
<setting help="Enrich employee profiles with skills and resumes" id="enrich_employee_setting">
|
|
<field name="module_hr_skills"/>
|
|
</setting>
|
|
</block>
|
|
<block title="Work Organization" name="work_organization_setting_container">
|
|
<setting company_dependent="1" help="Set default company schedule to manage your employees working time" id="default_company_schedule_setting">
|
|
<field name="resource_calendar_id" required="1" class="o_light_label" domain="[('company_id', '=', company_id)]" context="{'default_company_id': company_id}"/>
|
|
</setting>
|
|
</block>
|
|
<block title="Employee Update Rights" name="employee_rights_setting_container">
|
|
<setting help="Allow employees to update their own data" title="Allow employees to update their own data.">
|
|
<field name="hr_employee_self_edit"/>
|
|
</setting>
|
|
</block>
|
|
</app>
|
|
</xpath>
|
|
</field>
|
|
</record>
|
|
|
|
<record id="hr_config_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' : 'hr', 'bin_size': False}</field>
|
|
</record>
|
|
|
|
<menuitem id="hr_menu_configuration"
|
|
name="Settings"
|
|
parent="menu_human_resources_configuration"
|
|
sequence="0"
|
|
action="hr_config_settings_action"
|
|
groups="base.group_system"/>
|
|
</odoo>
|