In a recent change, we have introduced various backend and frontend code changes that requires users to select a filter for ROS calculations. These changes impact New Assortment and Allocation modules, as we use the same ROS Model calculation for both.
Frontend - When saving the ROS Model without a filter, users will now see a error message as the first screenshot below.
Backend - We have also implemented a backend change that will prevent the ROS calculation if the model does not have any filters. Because the change applies to existing products as well as new products, our users will need to add filtering options if it is missing. You can see the backend error message as in the second screenshot below when they right-click on the color-coded bars on line plan window.
Backend - In another backend change, we have also added a limit of 1000 on the total number of choices x clusters that a ROS model can leverage. This is currently a hard-coded limit but we have plans to introduce this as a client config in Settings > Configuration > Intelligence > ROS Configuration screen.
