Story

As an admin, I would like Min/Max values to be set to NULL when the config is turned on for a store or when a store is moved from a zone configured to calculate Min/Max values.

Details

Currently, when we turn Min/Max calculations off for a location, the calculated values persist in the database. Below is the scenario that causes the issue this tickets seeks to solve:

• Location "A" is configured to calculate Min/Max or Location "A" is in a zone configured to calculate Min/Max.
• Min/Max calculation for Location "A" is turned off or Location "A" is moved to a zone where Min/Max calculation is turned OFF.
• Min/Max calculation for Location "A" is turned back on or Location "A" is moved back into a zone where Min/Max calculation is ON.

After the above scenario has happened and the user creates the next order, they might be presented with the old, outdated Min/Max warnings. This problem will fix itself once they place the order as Min/Max values will be recalculated but we do not want to mislead the user by providing a false warning.

Config Name

• "Mobile > Ordering > Calculate Min/Max Values"

Job Name - "Clear VendorEntityItem Min Max"

AC

Assuming a location was configured to calculate Min/Max values:

1. When a store is removed from a Min/Max enabled zone, the Min/Max database values are set to NULL.
2. When the configuration to calculate Min/Max is turned off for a store, the Min/Max database values are set to NULL.
3. Min/Max calculations work correctly with the store in the Min/Max zone or if the config is enabled for the specific location.