the unique identifier for this nozzle.
-------------------LIFECYCLE----------------------------
Optional brand: AvailabilityModel<any>Set the values used to determine the selected pourable for this nozzle.
The pourable to set.
Utility method that will return the availability nodes that belong to the specified group as defined in the dispenser beverage graph. For example, a dispenser implementation may group availability nodes by Brand, Beverage, or Flavors
The group to filter by.
The availability nodes that are available to be dispensed from this nozzle and are in the specified group.
Utility method that will return the availability nodes that are tagged with the specified parent id.
This is useful when brandsets use the taggedIds property to associate nodes with a parent node. For example, when organizing a brandset into brands and beverages, the brand nodes will be tagged with the beverage nodes.
The parent id to filter by.
the availability nodes that are tagged with the specified parent id.
An action that will initiate a fixed volume pour for this nozzle using the specified pourable volume name.
The invocation of this action will result in a Future being returned that will provide the status of the pour and return any errors that may occur.
Optional tracker: stringkosFuture
The NozzleModel provides the availability of pourables that are associated with the nozzle.
Its primary purpose is to provide a mechanism for selecting from available pourables and initiating a pour.
It is possible for a dispenser to have multiple asymmetrical nozzles. For example, a dispenser may have a nozzle that is used for dispensing a syrups and flavors and another that is just dispensing water.
The NozzleModel is a IKosDataModel and is registered with the model registry using the Nozzle type.
See
Lifecycle
Load
During the
loadphase of the model lifecycle, the set of Availability nodes will be retrieved for the nozzle. The nodes will be indexed based on the definedgroupIdfor the node. ThegroupIdis defined in the dispenser beverage graph and is used to group availability nodes.Extension Points
The
loadlifecycle hook will first call into the ExtensionType.AvailabilityLoader extension point in order to establish the context that will be used to populate the availability nodes.The
loadlifecycle hook will then call into the ExtensionType.AvailabilityMapper for each Availability node that is retrieved. The extension point will be called the the Availability context data and the NozzleServices.BeverageResponse for the availability node.