Measurement units

With this release, a checkout client can post and customer/merchant can see measurement units for order line items. A measurement unit consists of a numeric value and a unit. It describes how much of a product is ordered when a customer puts quantity=1 of this product in their cart. For example:

"measurementUnit": {
  "value": 1,
  "unit" "m"
}

"measurementUnit": {
  "value": 2,
  "unit" "kg"
}

Only value is a required field. If unit is not provided, it will be interpreted as 1 piece.

The schema of the measurementUnit is a common quantitative-value schema, which you can find here: schema-quantitative-value

You can make use of this data and present it to your users. If you would like to update your order confirmation email templates and include this information in the order line items section, you can add the following code to your email template and customize the styling to your needs:

#if($!{entry.measurementUnit} && $!{entry.measurementUnit.value})
   <span style="color: #3c3c3c; padding-bottom: 10px;">
       #e($!{entry.measurementUnit.value})#e($!{entry.measurementUnit.unit}) per package
   </span><br/>
#end

Please note that this will only work if the order is placed using a checkout service that passes this information correctly to the Order service. The YaaS Checkout service does not support this yet, but it will be introduced soon.

Exposing the RAML API descriptor at the fixed URL

The Order service now exposes the RAML API descriptor at the 'meta-data/api.raml' relative URL. This makes the service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. Although the API descriptor is also served at the previous URL for backwards compatibility, existing Order service API consumers should update to the latest URL.