[6976][ADD] product_classification - #5
Open
yostashiro wants to merge 13 commits into
Open
Conversation
yostashiro
force-pushed
the
6976-add-product_nif
branch
6 times, most recently
from
July 9, 2026 04:58
7390412 to
28aa260
Compare
Member
Author
|
Add ja.po Translation notesTranslations are referenced from existing Odoo translations where available (odoo/base, odoo/stock). The following terms have no reference in the dependency (
|
yostashiro
force-pushed
the
6976-add-product_nif
branch
2 times, most recently
from
July 9, 2026 06:00
e2291b8 to
c8d18aa
Compare
yostashiro
force-pushed
the
6976-add-product_nif
branch
from
July 9, 2026 07:00
c8d18aa to
abc5cd1
Compare
Member
Author
|
Update ja.po (module renamed product_nif → nif; add root menu) Translation notesMerged with the existing translations — all prior entries preserved. One new term added for the Navi in Flow Configuration menu, referenced from existing Odoo translations (odoo/base, odoo/stock):
|
yostashiro
force-pushed
the
6976-add-product_nif
branch
2 times, most recently
from
July 9, 2026 07:38
74ea496 to
5c10785
Compare
Add the Navi in Flow (ナビフロー) module, an all-in-one home for the product- and (later) partner-side master data and field extensions exchanged with the CIAS system. It provides a dedicated Navi in Flow app menu so configuration lives in one place instead of scattered under Inventory settings. Currently included: - equipment classification (機器分類) and sub-classification (機器分類サブ), seeded with HOT / Concentrator, CPAP, HIT and Other (Auxiliary Device) - manufacturer (メーカー) master - product flags is_equipment / is_consumable (mutually exclusive) and their many2one links, shown in a Navi in Flow tab on the product form Configuration is maintained by admins (base.group_system); all users have read access so the classifications/manufacturer render on products. task-6976
yostashiro
force-pushed
the
6976-add-product_nif
branch
from
July 9, 2026 08:21
9ec2249 to
097e838
Compare
The module was scoped and named after a single consumer (Navi in Flow), but the product master data it holds (classification, manufacturer) has value independent of that integration, and new fields (e.g. consumable classification) are not necessarily interfaced with Navi in Flow. Rename it to product_classification and reframe it as product classification master data, with Navi in Flow as one consumer: - replace the mutually-exclusive is_equipment/is_consumable booleans with a single product_kind selection - add a product.consumable.classification taxonomy and the consumable_classification_id field, parallel to the equipment axis - move configuration menus under Inventory > Configuration > Products (drop the standalone app menu) - present the fields on a "Classification" product tab (was "Navi in Flow"), with equipment/consumable groups shown per product_kind - record Navi-in-Flow usage in the help text of the fields that feed the integration, so their purpose stays traceable
Add an "accessory" (付属品) value to product_kind, between equipment and consumable. Accessories share the equipment classification taxonomy, so the Equipment Classification group on the product form is shown for both equipment and accessory kinds.
smorita7749
force-pushed
the
6976-add-product_nif
branch
from
July 29, 2026 09:54
90af526 to
6959781
Compare
yostashiro
commented
Jul 30, 2026
Comment on lines
+9
to
+10
| <field name="middle_category_id" options="{'no_quick_create': True}" /> | ||
| <field name="minor_category_id" options="{'no_quick_create': True}" /> |
Member
Author
There was a problem hiding this comment.
I think we should keep these fields inside the classification page.
- Add middle and minor product category seed records (moved in from ocj_config so all classification master data lives with the module that defines the models). - Drop the Navi in Flow reference from the middle/minor category field help: these categories are maintained in Odoo and not exchanged with NaviFlow. - Add Japanese translations for the new records.
…the Classification page Per review: keep the middle/minor category fields inside the Classification notebook page alongside the other classification fields, instead of placing them next to categ_id on the general form.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
QT6976
Add the product_classification module — product-side classification master data so equipment and consumables can be categorized consistently. Several of these fields feed the Navi in Flow (ナビフロー) integration with CIAS, but the data is scoped by domain (product classification) rather than by that single consumer.
Included:
product_kindselection (equipment / consumable) on the productproduct_kindRenamed from the earlier
nifmodule (supersedes #4); reframed from a Navi-in-Flow-specific extension to product classification master data.