Rules are used within a to define when; or if, something should happen. They help translate business logic into your OMS setup.
Send an including the `inventoryPositionExists`
flag indicating whether the corresponding Position exists or not.
This is a simplified version of the `LoadInventoryPosition`
, excluding the logic for:
`LAST_ON_HAND`
in status `ACTIVE`
or `CREATED`
`inventoryQuantityExists`
flag (true or false)Conditionally another when the specified field or does not match the provided value.
This is typically used as an "else" case for the IfPropertyEquals .
Conditionally another when the specified field or is null.
This is typically used as an "else" case for the IfPropertyIsPresent .
Conditionally send an to the (specified by its Reference) if it passes the "Network-Match-Check".
A passes the "Network-Match-Check" when its (s) finds a match with a given Position (s).
The `Rule NotifyVirtualCataloguesByRefsOnNetworksMatch`
is a newer version of the `NotifyVirtualCatalogueOnNetworkMatch`
. Moving forward, please use the `NotifyVirtualCataloguesByRefsOnNetworksMatch`
instead of the `NotifyVirtualCatalogueOnNetworkMatch`
.
The creates one or more articles for the Fulfilment in the incoming .
Forwards the with name {eventName} if the Standard Product exists.
The forwards the input with coordinates of the pickup .
The updates the longitude and latitude of the based on the incoming information received from the ResolveOrderCoordinates rule.
This works only if the comes without coordinates. The ResolveOrderCoordinates resolves the coordinates and sends the with latitude and longitude. After that, the UpdateOrderCoordinates gets coordinates from the and updates the delivery address with coordinates.