### Configure Product Form Fields Conditionally (XML)

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This XML snippet demonstrates how to configure fields within a product form based on module installations, application configurations, and company-specific settings. It utilizes `if-module`, `if`, and `showIf` attributes to conditionally display or enable fields like `isActivity`, `configurator`, `salePrice`, `salesUnit`, and stock management features.

```xml
<form name="product-form" model="com.axelor.apps.base.db.Product">
  <!-- Conditional field visibility based on module -->
  <field name="isActivity"
    if-module="axelor-human-resource"
    if="__config__.app.isApp('employee')"/>

  <!-- Feature toggle based on app configuration -->
  <field name="configurator"
    showIf="__config__.app.getApp('sale')?.getEnableConfigurator()"
    if="__config__.app.isApp('sale')"/>

  <!-- Company-specific field management -->
  <field name="salePrice"
    if="!__config__.app.getApp('base')?.companySpecificProductFieldsSet?.find({it.name == 'salePrice'})"/>

  <!-- Multi-unit management toggle -->
  <field name="salesUnit"
    if="__config__.app.getApp('sale')?.getManageSalesUnits()"/>

  <!-- Stock management features -->
  <panel name="stockPanel"
    if-module="axelor-stock"
    if="__config__.app.isApp('stock')"
    showIf="productTypeSelect == 'storable'">
    <field name="stockManaged"/>
  </panel>
</form>
```

--------------------------------

### Axelor XML: Define Product Action Group

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Creates an action group in Axelor XML to execute a sequence of predefined actions for a new product, including setting defaults, adjusting scale and precision, and marking it as sellable.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-group name="action-group-base-product-onnew">
    <action name="action-product-record-default-new"/>
    <action name="action-product-attrs-scale-and-precision"/>
    <action name="action-product-record-sellable"/>
  </action-group>

</object-views>
```

--------------------------------

### Axelor XML: Define Product Validation Action

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Sets up a validation action in Axelor XML to display an alert message when specific conditions are met, such as attempting to procure a 'service' type product from stock.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-validate name="action-product-validate-sale-supply-select">
    <alert message="A product of type service can't be procured from stock."
      if="saleSupplySelect == 1 &amp;&amp; productTypeSelect == 'service'"/>
  </action-validate>

</object-views>
```

--------------------------------

### Axelor XML: Define Product View Action

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Configures a view action in Axelor XML to open a grid or form view for product variants, filtered by the parent product's ID and setting a context variable for available quantities.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-view name="action-product-view-product-variant"
    title="Products variants"
    model="com.axelor.apps.base.db.Product">
    <view type="grid" name="product-product-variant-grid"/>
    <view type="form" name="product-form"/>
    <domain>self.parentProduct.id = :id</domain>
    <context name="_xFillProductAvailableQty" expr="eval: true"/>
  </action-view>

</object-views>
```

--------------------------------

### Define Product Grid and Form Views in XML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Defines the user interface for the 'Product' entity in Axelor Open Suite, including a grid view for displaying lists of products and a form view for detailed editing. These XML definitions control how data is presented and interacted with in the application's UI.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<object-views xmlns="http://axelor.com/xml/ns/object-views"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://axelor.com/xml/ns/object-views http://axelor.com/xml/ns/object-views/object-views_7.4.xsd">

  <grid name="product-grid" title="Products" model="com.axelor.apps.base.db.Product" orderBy="code,name">
    <toolbar>
      <button name="catalogBtn" title="Catalog" onClick="action-print-product-catalog" icon="fa-book"/>
    </toolbar>
    <field name="picture" widget="Image"/>
    <field name="code" x-bind="{{code|unaccent|uppercase}}" width="120"/>
    <field name="name" width="300"/>
    <field name="productCategory" form-view="product-category-form" grid-view="product-category-grid"/>
    <field name="salePrice" x-scale="2"/>
    <field name="unit" width="70"/>
  </grid>

  <form name="product-form" title="Product" model="com.axelor.apps.base.db.Product"
    onNew="action-group-base-product-onnew"
    onSave="action-group-product-onsave"
    onLoad="action-group-product-onload"
    width="large">
    <panel name="mainPanel">
      <field name="code" required="true" colSpan="5"/>
      <field name="name" required="true" colSpan="7"/>
      <field name="productTypeSelect" required="true" onChange="action-group-base-product-producttype-onchange"/>
      <field name="salePrice" readonlyIf="autoUpdateSalePrice"/>
      <field name="purchasePrice" showIf="purchasable"/>
      <field name="sellable"/>
      <field name="purchasable"/>
    </panel>
  </form>
</object-views>
```

--------------------------------

### Define Product Domain Model in XML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Defines the data structure and business entities for a 'Product' within the Axelor Open Suite. It includes fields, relationships, constraints, and business logic. This XML file is part of the domain model definition and specifies how product data is stored and managed.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<domain-models xmlns="http://axelor.com/xml/ns/domain-models"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://axelor.com/xml/ns/domain-models http://axelor.com/xml/ns/domain-models/domain-models_7.4.xsd">

  <module name="base" package="com.axelor.apps.base.db"/>

  <entity name="Product">
    <string name="name" title="Name" initParam="true" translatable="true"/>
    <string name="code" title="Code" initParam="true" unique="true"/>
    <string name="description" large="true" title="Description" translatable="true"/>
    <many-to-one name="productCategory" ref="ProductCategory" title="Product category" massUpdate="true"/>
    <many-to-one name="unit" ref="Unit" title="Unit" massUpdate="true"/>
    <string name="productTypeSelect" title="Type" selection="product.product.type.select" massUpdate="true"/>
    <decimal name="salePrice" title="Sale price W.T." precision="20" scale="10" massUpdate="true"/>
    <decimal name="purchasePrice" title="Purchase price W.T." precision="20" scale="10" massUpdate="true"/>
    <decimal name="costPrice" title="Cost price" precision="20" scale="10" massUpdate="true"/>
    <boolean name="sellable" title="Sellable" default="true"/>
    <boolean name="purchasable" title="Purchasable" default="true"/>

    <extra-code>
      <![CDATA[
        public static final String PRODUCT_TYPE_SERVICE = "service";
        public static final String PRODUCT_TYPE_STORABLE = "storable";
        public static final int SALE_SUPPLY_FROM_STOCK = 1;
        public static final int SALE_SUPPLY_PURCHASE = 2;
      ]]>
    </extra-code>

    <track on="UPDATE">
      <field name="name"/>
      <field name="salePrice"/>
      <message if="true" on="UPDATE">Product updated</message>
    </track>
  </entity>
</domain-models>
```

--------------------------------

### Configure CSV Data Import Mapping in XML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This XML configuration defines how data from a 'products.csv' file is imported into the 'com.axelor.apps.base.db.Product' entity. It maps CSV columns to entity fields, specifies search criteria for related entities (like category and unit), and uses an adapter for boolean type conversion.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<csv-inputs xmlns="http://axelor.com/xml/ns/data-import">
  <input file="products.csv" type="com.axelor.apps.base.db.Product">
    <bind column="code" to="code"/>
    <bind column="name" to="name"/>
    <bind column="product_type" to="productTypeSelect"/>
    <bind column="sale_price" to="salePrice"/>
    <bind column="purchase_price" to="purchasePrice"/>
    <bind column="category_code" to="productCategory"
      search="self.code = :category_code"/>
    <bind column="unit_name" to="unit"
      search="self.name = :unit_name"/>
    <bind column="sellable" to="sellable"
      adapter="com.axelor.csv.script.ImportBoolean"/>
  </input>
</csv-inputs>
```

--------------------------------

### Axelor XML: Define Product Record Action

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Defines a record action in Axelor XML to compute the sale price of a product based on its cost price and management coefficient. It includes conditional logic for updates.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-record name="action-product-record-compute-sale-price"
    model="com.axelor.apps.base.db.Product">
    <field name="salePrice"
      expr="eval: managPriceCoef * costPrice"
      if="costPrice != null &amp;&amp; managPriceCoef != null &amp;&amp; autoUpdateSalePrice"/>
  </action-record>

</object-views>
```

--------------------------------

### Generate Axelor Open Suite CHANGELOG.md

Source: https://github.com/minhtuanvu/axelor-open-suite/blob/master/changelogs/README.md

This command executes the Gradle task to generate the `CHANGELOG.md` file from unreleased entries. It also handles the removal of entries from the `changelogs/unreleased` directory after generation. A `--preview` argument is available for a dry run.

```bash
./gradlew generateChangeLog

```

--------------------------------

### Document Release Changes with YAML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This YAML snippet documents changes for Axelor Open Suite releases, detailing bug fixes and new features. It includes information on module impact, developer notes, and migration steps, such as updating view definitions or regenerating domain classes using Gradle.

```yaml
---
title: Invoice type is now correctly hidden in canceled invoices
module: axelor-account
developer: |
  Fixed hidden attribute handling for Invoice.typeSelect field:
  - The field is now properly hidden when statusSelect equals STATUS_CANCELED
  - View definition updated in views/Invoice.xml
  - Impact on custom modules: If you have overridden the invoice form view,
    update your hideIf conditions for typeSelect field

  Migration steps:
  ```bash
  # Update any custom view overrides
  $ find . -name "Invoice*.xml" | xargs grep -l "typeSelect"
  # Review and update hideIf/showIf conditions as needed
  ```
---
title: New barcode generation feature for products
module: axelor-base
developer: |
  Added barcode generation support to Product entity:
  - New fields: barCode (MetaFile), barcodeTypeConfig (BarcodeTypeConfig)
  - Configuration option: activateBarCodeGeneration in AppBase
  - Controller method: ProductController.generateBarcode()

  Breaking changes:
  - Product.xml domain model updated with new barCode relationship
  - Product form view includes new barcode panel

  If you extend Product entity, regenerate domain classes:
  ```bash
  $ ./gradlew clean build
  ```
```

--------------------------------

### Structure Axelor Forms with Panels and Tabs

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This XML defines a complex form layout in Axelor using nested panels, tabs, and conditional rendering for better data organization. It includes panels for general information, images, sales, purchase/costs, and stock, with specific widgets and related views.

```xml
<form name="product-form" model="com.axelor.apps.base.db.Product" width="large">
  <panel name="mainPanel">
    <panel name="namePanel" colSpan="4">
      <field name="code" colSpan="5"/>
      <field name="name" colSpan="7"/>
    </panel>

    <panel name="imagePanel" colSpan="2">
      <field name="picture" widget="Image"/>
    </panel>
  </panel>

  <panel-tabs name="productSpecificAttributes">
    <panel name="salePanel" title="Sale">
      <field name="sellable"/>
      <field name="salePrice" showIf="sellable"/>
      <panel-related name="saleProductMultipleQtyListPanel"
        field="saleProductMultipleQtyList"
        grid-view="product-multiple-qty-grid"
        form-view="product-multiple-qty-form"/>
    </panel>

    <panel name="purchasePanel" title="Purchase/Costs">
      <field name="purchasable"/>
      <field name="purchasePrice" showIf="purchasable"/>
    </panel>

    <panel name="stockPanel" title="Stock"
      showIf="productTypeSelect == 'storable'"
      if-module="axelor-stock">
      <panel-dashlet action="action-product-view-stock"/>
    </panel>
  </panel-tabs>
</form>
```

--------------------------------

### Axelor XML: Define Product Search Filters

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Defines a set of search filters in Axelor XML for the 'Product' model, including simple field filters and predefined domain filters for categorizing products (current, storable, service, obsolete).

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <search-filters name="products-filters" model="com.axelor.apps.base.db.Product" title="Products filters">

    <field name="purchaseProductMultipleQtyList" title="Multiple quantities of purchase"/>
    <field name="serialNumber"/>
    <field name="productCategory"/>

    <filter name="products-filters-current-products" title="Current Products">
      <domain>self.endDate IS NULL or CURRENT_DATE &lt; self.endDate</domain>
    </filter>

    <filter name="products-filters-storable-products" title="Storable Products">
      <domain>(self.endDate IS NULL or CURRENT_DATE &lt; self.endDate)
        and self.productTypeSelect = 'storable'</domain>
    </filter>

    <filter name="products-filters-service-products" title="Service Products">
      <domain>(self.endDate IS NULL or CURRENT_DATE &lt; self.endDate)
        and self.productTypeSelect = 'service'</domain>
    </filter>

    <filter name="products-filters-obsolete-products" title="Obsolete Products">
      <domain>CURRENT_DATE &gt; self.endDate</domain>
    </filter>
  </search-filters>

</object-views>
```

--------------------------------

### Axelor XML: Define Product Method Action

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Implements a method action in Axelor XML to call a specific Java controller method ('updateCostPrice') in the 'ProductController' class. This is used for executing custom business logic.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-method name="action-product-method-update-cost-price">
    <call class="com.axelor.apps.base.web.ProductController" method="updateCostPrice"/>
  </action-method>

</object-views>
```

--------------------------------

### Axelor Open Suite Changelog Entry Format

Source: https://github.com/minhtuanvu/axelor-open-suite/blob/master/changelogs/README.md

Defines the structure for changelog entries in YAML format. It includes fields for the title, the affected module, and detailed technical information for developers. The `developer` field can contain code snippets for migration steps.

```yaml
---
title: Some text
module: axelor-base
developer: |
  some description here with technical details about breaking changes
  and migrations steps.

  ```
  $ find -iregex ".*domains.*.xml" | xargs -l sed -i 's|cachable=|cacheable=|g'
  ```

```

--------------------------------

### Define Sales Order Entity Schema in XML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Defines the 'SaleOrder' entity for the sales module in Axelor Open Suite. It includes fields for customer information, dates, pricing, status, and associated order lines and taxes. This XML schema dictates the structure of sales order data within the application.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<domain-models xmlns="http://axelor.com/xml/ns/domain-models">
  <module name="sale" package="com.axelor.apps.sale.db"/>

  <entity name="SaleOrder">
    <many-to-one name="company" ref="com.axelor.apps.base.db.Company" required="true" title="Company"/>
    <string name="saleOrderSeq" title="Internal Number" readonly="true"/>
    <many-to-one name="currency" ref="com.axelor.apps.base.db.Currency" title="Currency"/>
    <string name="externalReference" title="Customer reference"/>
    <date name="creationDate" title="Creation date" required="true" readonly="true"/>
    <datetime name="confirmationDateTime" title="Confirmation date" readonly="true"/>

    <many-to-one name="clientPartner" ref="com.axelor.apps.base.db.Partner" title="Customer"/>
    <many-to-one name="contactPartner" ref="com.axelor.apps.base.db.Partner" title="Customer contact"/>
    <many-to-one name="mainInvoicingAddress" ref="com.axelor.apps.base.db.Address" title="Main/Invoicing address"/>
    <many-to-one name="priceList" ref="com.axelor.apps.base.db.PriceList" title="Price list"/>
    <many-to-one name="deliveryAddress" ref="com.axelor.apps.base.db.Address" title="Delivery address"/>

    <boolean name="inAti" title="In ATI"/>
    <date name="endOfValidityDate" title="End of validity"/>

    <one-to-many name="saleOrderLineList" ref="com.axelor.apps.sale.db.SaleOrderLine"
      mappedBy="saleOrder" title="Sale order lines" orderBy="sequence"/>
    <one-to-many name="saleOrderLineTaxList" ref="com.axelor.apps.sale.db.SaleOrderLineTax"
      mappedBy="saleOrder" title="Tax Lines"/>

    <decimal name="exTaxTotal" title="Total W.T." scale="3" precision="20" readonly="true"/>
    <decimal name="taxTotal" title="Total tax" scale="3" precision="20" readonly="true"/>
    <decimal name="inTaxTotal" title="Total A.T.I." scale="3" precision="20" readonly="true"/>

    <integer name="statusSelect" title="Status" selection="sale.order.status.select" readonly="true"/>

    <decimal name="totalCostPrice" title="Total cost price" precision="20" scale="3"/>
    <decimal name="totalGrossMargin" title="Gross Profit" precision="20" scale="3"/>
    <decimal name="marginRate" title="Margin (%)"/>

    <many-to-one name="salespersonUser" ref="com.axelor.auth.db.User" title="Salesperson"/>
    <many-to-one name="team" ref="com.axelor.team.db.Team" title="Team"/>

    <string name="description" title="Comment to display" large="true"/>
    <string name="internalNote" title="Internal note" large="true"/>
  </entity>
</domain-models>
```

--------------------------------

### Axelor XML: Define Product Attribute Action

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

Configures attribute actions in Axelor XML to dynamically change the 'title' property of the 'salePrice' field and control the 'hidden' property of 'purchasePrice' based on conditions like 'inAti' and 'purchasable'.

```xml
<object-views xmlns="http://axelor.com/xml/ns/object-views">

  <action-attrs name="action-product-attrs-change-title-based-on-inAti">
    <attribute name="title" for="salePrice"
      expr="eval: com.axelor.i18n.I18n.get('Sale price A.T.I.')" if="inAti"/>
    <attribute name="title" for="salePrice"
      expr="eval: com.axelor.i18n.I18n.get('Sale price W.T.')" if="!inAti"/>
    <attribute name="hidden" for="purchasePrice" expr="eval: !purchasable"/>
  </action-attrs>

</object-views>
```

--------------------------------

### Implement Field Tracking and Audit in Axelor Entities

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This XML snippet demonstrates how to configure tracking for specific field changes on entity updates in Axelor. It defines which fields to track and sets up custom messages to be logged in the audit trail upon modification.

```xml
<domain-models xmlns="http://axelor.com/xml/ns/domain-models">
  <entity name="Product">
    <string name="name" title="Name"/>
    <string name="code" title="Code"/>
    <decimal name="salePrice" title="Sale price"/>
    <many-to-one name="productCategory" ref="ProductCategory"/>
    <boolean name="sellable" title="Sellable"/>

    <!-- Track specific field changes on UPDATE -->
    <track on="UPDATE">
      <field name="name"/>
      <field name="code"/>
      <field name="productCategory"/>
      <field name="sellable"/>
      <field name="salePrice"/>
      <field name="saleCurrency"/>
      <field name="purchasePrice"/>
      <field name="costPrice"/>
      <message if="true" on="UPDATE">Product updated</message>
    </track>
  </entity>
</domain-models>
```

--------------------------------

### Configure Dynamic Field Behavior in Axelor Forms

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This XML snippet illustrates how to control field behavior (readonly, show/hide, required) in Axelor forms based on dynamic conditions using expression language. It also shows data binding with transformations and domain filtering for related records.

```xml
<form name="product-form" model="com.axelor.apps.base.db.Product">
  <!-- Readonly based on condition -->
  <field name="salePrice" readonlyIf="autoUpdateSalePrice || costTypeSelect != 1"/>

  <!-- Show/hide based on conditions -->
  <field name="purchasePrice" showIf="purchasable"/>
  <field name="supplierDeliveryTime" hideIf="!purchasable || isShippingCostsProduct"/>

  <!-- Required based on context -->
  <field name="code" requiredIf="!__config__.app.getApp('base')?.getGenerateProductSequence()"/>
  <field name="netMass" requiredIf="usedInDEB"/>

  <!-- Conditional visibility with complex logic -->
  <field name="standardDelay"
    showIf="saleSupplySelect == 2 || saleSupplySelect == 3"
    if-module="axelor-supplychain"/>

  <!-- Data binding with transformations -->
  <field name="code" x-bind="{{code|unaccent|uppercase}}"/>

  <!-- Domain filtering for related records -->
  <field name="defaultSupplierPartner"
    domain="self.isContact = false AND self.isSupplier = true"/>
</form>
```

--------------------------------

### Define Multi-Entity Relationships in Axelor XML

Source: https://context7.com/minhtuanvu/axelor-open-suite/llms.txt

This snippet demonstrates how to define various relationships (many-to-one, one-to-many, many-to-many, self-referential) between entities in Axelor using XML. It specifies the referenced entity and mapping details for cascading operations.

```xml
<domain-models xmlns="http://axelor.com/xml/ns/domain-models">
  <entity name="Product">
    <!-- Many-to-one: Product belongs to one category -->
    <many-to-one name="productCategory" ref="ProductCategory" title="Product category"/>

    <!-- Many-to-one: Product has one default supplier -->
    <many-to-one name="defaultSupplierPartner" ref="com.axelor.apps.base.db.Partner" title="Default supplier"/>

    <!-- One-to-many: Product has multiple price list entries -->
    <one-to-many name="priceListLineList" ref="com.axelor.apps.base.db.PriceListLine" mappedBy="product"/>

    <!-- One-to-many: Product has multiple company-specific settings -->
    <one-to-many name="productCompanyList" ref="com.axelor.apps.base.db.ProductCompany"
      title="Products per companies" mappedBy="product"/>

    <!-- Many-to-many: Product can be sold by multiple trading names -->
    <many-to-many name="tradingNameSellerSet" ref="com.axelor.apps.base.db.TradingName"
      title="Trading names that can sell this product"/>

    <!-- Self-referential: Product variants -->
    <many-to-one name="parentProduct" ref="com.axelor.apps.base.db.Product" title="Parent product"/>
    <boolean name="isModel" title="Is model"/>
  </entity>
</domain-models>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.