Skip to Content
Menu

162.71

v 17.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 19014
Technical Name generic_request_field_set
LicenseOPL-1
Websitehttps://crnd.pro
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Community Apps Dependencies
Lines of code 19014
Technical Name generic_request_field_set
LicenseOPL-1
Websitehttps://crnd.pro

Generic Request Field Set

ITSM | Helpdesk | Service Desk

License: OPL-1 CR&D

Generic Request Field Set allows users to associate custom field sets with requests, providing enhanced data collection capabilities tailored to specific request classifiers.

Key Features:

  • Link custom field sets to request classifiers
  • Configure field sets through model inheritance
  • Access field sets directly from request forms
  • Keep request data structured and organized

Understanding Field Sets:

Field sets allow you to associate additional structured data with your requests. Each field set represents a collection of custom fields that can be filled by users when creating or updating requests.

Associating Field Sets with Request Classifiers:

Field set types are defined in the Request Classifier module. They determine which models will be used to store additional data for specific request classifiers, allowing different types, service, category (classifiers) of requests to collect different sets of additional data.

Request Classifier Configuration

User Experience:

Users can access and fill field sets directly from the request form by clicking the 'Fields' button or create/edit from page "Field Set".

Field Set Form Field Set Page Field Set Form

Example Field Set Included:

The module includes an example Field Set Type called "Test Incident Field Set" (model: test.incident.field.set.value), which demonstrates how field sets can be created and used. This example field set contains the following fields:

  • char_1 - Character field (text)
  • integer_1 - Integer field (whole numbers)
  • float_1 - Float field (decimal numbers)
  • date_1 - Date field
  • datetime_1 - Datetime field (date with time)
  • many2one_1_id - Many2one relation to Partners (single selection)
  • many2many_1_ids - Many2many relation to Partners (multiple selections)

This example demonstrates the various field types that can be used in your own custom field sets.

Creating Custom Field Sets:

There are two ways to create custom field sets:

  1. Programmatically through a custom module:
    • Create a new Python module with a model that inherits from generic.request.field.set.mixin
    • Define your custom fields in the model
    • Create views for your model
    • Register your model as a field set type in data files

    Example of model definition:

    from odoo import models, fields
    
    class MyCustomFieldSet(models.Model):
        _name = 'my.custom.field.set'
        _description = 'My Custom Field Set'
        _inherit = ['generic.request.field.set.mixin']
        
        my_char_field = fields.Char(string="Text Field")
        my_boolean_field = fields.Boolean(string="Yes/No Field")
        my_selection_field = fields.Selection([
            ('option1', 'Option 1'),
            ('option2', 'Option 2'),
        ], string="Selection Field")
                

    Example of XML data file to register your model as a field set type:

    <?xml version="1.0" encoding="utf-8"?>
    <odoo noupdate="1">
        <record id="field_set_type_my_custom" model="field.set.type">
            <field name="name">My Custom Field Set</field>
            <field name="field_set_model_id" ref="model_my_custom_field_set"/>
        </record>
    </odoo>
                

    Then include this XML file in your module's __manifest__.py:

    'data': [
        'data/my_custom_field_set_type.xml',
    ],
                
  2. Through the user interface (recommended):

    For easier creation and management of field sets, you can use the generic_request_field_set_builder module, which provides a user-friendly interface for:

    • Creating new field set models without programming
    • Adding custom fields with different types
    • Generating views automatically
    • Managing field set configurations directly from the UI

    This is the recommended approach for most users who don't want to write custom code.

Launch Your Own ITSM System in 60 Seconds

Create your own Bureaucrat ITSM database.
yodoo.systems

Maintainer

CR&D
Website Contact Us Report Bug Requests

This module is maintained by Center of Research & Development.

We offer Odoo support, implementation, customization, third-party development, integration, and consulting services.

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.