Order module release 1.2.8

Improvements to the Order Module, Two new rules have been introduced to help with allocating orders to a location for fulfillment. Order coordinates will now also be properly checked to determine if a delivery location is valid.

• Fix to address an issue with

  `class java.lang.NoClassDefFoundError:javax/net/SocketFactory`

  when using the rule ResolveOrderCoordinates. The processing would stop with the order stuck at RECEIVED status. OSGI package declarations changed to include

  `javax.net.*,`

  . A similar fix was made to the

  `gson`

  library changing its scope from

  `provided`

  to

  `runtime`

  .
• Fixed an unexpected behaviour with the Multi and CC workflow. Previously when an order is placed with a

  `pickupLocationRef`

  that is not part of the existing locations or eligible the network, the system would assign the fulfilment to the location regardless. Now, instead no Fulfilment will be created and the Order will be placed in an

  `ESCALATED`

  status. This was achieved by introducing a new ruleset

  `ValidatePickupLocation`

  with two new rules:

  `ForwardIfPickupLocationValid`

  and

  `ForwardIfPickupLocationNotValid`

  to validate whether the

  `pickupLocationRef`

  requested is valid before proceeding to the usual

  `ProcessOrder`

  ruleset. When the pickup location is invalid the order will move to an

  `ESCALATED`

  status.

You can update to the latest reference order module here.