Consumables Tab Configuration

You can view the Consumables tab's default configuration using the Configuration Preview feature. Its structure is shown below:

          "consumables": {
      "label": "Inventory",
      "icon": "wrench",
      "element": {
        ...
      },
      "article": {
        ...
      },
      "enable": []
    },

The task, asset, and employee defaults are set on a consumable record when it's created.

          "defaults": {
          "custrecord_nx_constask": "${ event.internalid }",
          "asset": "${ options.asset || event.asset }",
          "custrecord_nx_consemployee": "${ user.internalid }"
        }

Here are some things to consider when configuring the Consumables tab:

As a custom record, Field Service Consumables can have additional fields added, but the record and bundled fields are locked to ensure the product will function as designed.
You can add more fields to the Consumables record, but you can't connect them to the sales order creation process through configuration. Scripts or workflows may be able to do this.
The Consumables tab is supported by FSM's billing feature. This means that the billing rules for the consumables tab can be configured through the billing feature. This includes applying price levels and more complex business requirements, or making the charges billable, or billable at $0 (no revenue or financial impact to the end customer).
You can't set specific pricing or let users set pricing for an item in the mobile app. You can only choose between billable and non-billable, or set price levels. However, the price levels will in turn apply different rates, and if a customer has customer-specific pricing set, that pricing will be applied when the sales order is created.
You can set up consumables so users can choose if an item is billable or non-billable through configuration.
You can turn off sales order creation or auto-fulfillment from consumables through configuration.

You can set the bill and fulfill properties to true or false. The "bill" element controls whether a sales order is created. The "fulfill" element controls whether it gets fulfilled.
```
              "consumable": {
    "bill": true,
    "fulfill": true
  }, 

            
```

Related Topics