With disregard for actual Physical Inventory in a Warehouse, the following would work for simple control of Product Sales…
Work Period Started
Event containing Action with [?Prompt]
…
- (optional) Action
Update Program Setting
with:[?How Many Soup are Available Today]
to put value in{SETTING:Soups Available}
- Action
Update Product Tag
with:[?How Many Soup are Available Today]
to put value in{ITEM TAG:Available}
- Rule for
Order Added
Event with ActionUpdate Product Tag
with:[=TN('{ITEM TAG:Available}')-1]
to decrease count and with Constrained Action toCancel Order
when[=TN('{ITEM TAG:Available}')-1] == 0
.
That would suffice for those types of products, where the number of bowls of onion soup is changed daily, and you’re not necessarily concerned with tracking Physical Inventory of onions.
In fact, now that I look at it, you wouldn’t even need a Product Tag
at all, just a Program Setting
alone would work. Although having the ability to update the Product Tag
could still be useful… once {SETTING:Soups Available}
becomes 0
, update the Product Tag {ITEM TAG:Available}
to No
.
For actual Physical Inventory in a Warehouse
(like Soda, Beer, Buns, etc), that is a different matter. There are no provisions currently built in to read Inventory
counts for use in Rules, are there @emre?
We would need an Action to read the count of Inventory Items, something like Read Inventory Values
with a parameter for Inventory Item Name
, and have it return the Physical Quantity
at the very least, or determine the Consumption
on-the fly, which might be expensive.