Kishan Gajjar
b2ebf59a11
Purpose ======= Improve readability on mobile Specification ============= Activate Kanban view on those so it could be displayed by default on mobile instead of view list List of impacted modules: - stock: kanban for incoming products - stock_picking_wave: kanban for picking waves - stock: kanban for reordering rules - stock: kanban for inventory adjustments - stock: kanban for stock moves - purchase_requisition: kanban for purchase agreement - purchase_requisition: kanban for purchase agreement types - procurement: kanban for procurement exceptions - mrp: kanban for unbuild orders - mrp: kanban for waiting availability mo - mrp: kanban for routing - mrp: kanban for bill of materials - mrp_repair: kanban for repair orders - mrp : kanban for work order messages - mrp : kanban for productivity losses - mrp : kanban for Orders to Plan(reuse Manufacturing Orders - mrp : kanban for work centers(reuse Work Centers Dashboard) - maintenance: kanban for equipment categories - barcode : kanban for barcode nomenclatures
85 lines
4.1 KiB
XML
85 lines
4.1 KiB
XML
<?xml version="1.0"?>
|
|
<odoo>
|
|
<!-- BARCODE NOMENCLATURES -->
|
|
<record model="ir.ui.view" id="view_barcode_nomenclature_form">
|
|
<field name="name">Barcode Nomenclatures</field>
|
|
<field name="model">barcode.nomenclature</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Barcode Nomenclature">
|
|
<sheet>
|
|
<group col="4">
|
|
<field name="name" />
|
|
<field name="upc_ean_conv"/>
|
|
</group>
|
|
<div>
|
|
<p>
|
|
<i>Barcodes Nomenclatures</i> define how barcodes are recognized and categorized.
|
|
When a barcode is scanned it is associated to the <i>first</i> rule with a matching
|
|
pattern. The pattern syntax is that of regular expression, and a barcode is matched
|
|
if the regular expression matches a prefix of the barcode.
|
|
</p><p>
|
|
Patterns can also define how numerical values, such as weight or price, can be
|
|
encoded into the barcode. They are indicated by <code>{NNN}</code> where the N's
|
|
define where the number's digits are encoded. Floats are also supported with the
|
|
decimals indicated with D's, such as <code>{NNNDD}</code>. In these cases,
|
|
the barcode field on the associated records <i>must</i> show these digits as
|
|
zeroes.
|
|
</p>
|
|
</div>
|
|
<field name="rule_ids">
|
|
<tree string='Tables'>
|
|
<field name="sequence" widget="handle"/>
|
|
<field name="name" />
|
|
<field name="type" />
|
|
<field name="encoding" />
|
|
<field name="pattern" />
|
|
</tree>
|
|
</field>
|
|
</sheet>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
|
|
<record model="ir.ui.view" id="view_barcode_nomenclature_tree">
|
|
<field name="name">Barcode Nomenclatures</field>
|
|
<field name="model">barcode.nomenclature</field>
|
|
<field name="arch" type="xml">
|
|
<tree string="Barcode Nomenclatures">
|
|
<field name="name" />
|
|
</tree>
|
|
</field>
|
|
</record>
|
|
|
|
<record model="ir.actions.act_window" id="action_barcode_nomenclature_form">
|
|
<field name="name">Barcode Nomenclatures</field>
|
|
<field name="type">ir.actions.act_window</field>
|
|
<field name="res_model">barcode.nomenclature</field>
|
|
<field name="view_type">form</field>
|
|
<field name="view_mode">tree,kanban,form</field>
|
|
<field name="help" type="html">
|
|
<p class="oe_view_nocontent_create">
|
|
Click to add a Barcode Nomenclature .
|
|
</p><p>
|
|
A barcode nomenclature defines how the point of sale identify and interprets barcodes
|
|
</p>
|
|
</field>
|
|
</record>
|
|
|
|
<record model="ir.ui.view" id="view_barcode_rule_form">
|
|
<field name="name">Barcode Rule</field>
|
|
<field name="model">barcode.rule</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Barcode Rule">
|
|
<group col="4">
|
|
<field name="name" />
|
|
<field name="sequence" />
|
|
<field name="type"/>
|
|
<field name="encoding" attrs="{'invisible': [('type','=', 'alias')]}"/>
|
|
<field name="pattern" />
|
|
<field name="alias" attrs="{'invisible': [('type','!=', 'alias')]}"/>
|
|
</group>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
</odoo>
|