I'm suprised this workflow made it into the end product. The model state changes could have made working with automated (toggling suppression states and BOM's with iLogic) assemblies a much better experience. Especially since it's now possible to do this in 'master' state/lod, which circumvents a lot of state/lod problems previously present in Inventor. Yet, now the end user has to 'sometimes' check every drawing for zero QTY entires in any BOM. I'm stating 'sometimes' because the iLogic 'IsActive' command still sets BOM's to 'reference' and thus creates the behavior I would expect when something is suppressed in a model state: Make the part invisible and remove it from the BOM.
If a correct BOM is to be manually generated (with no '0' entries) the end user will still have to both suppress items AND set them to 'Reference' (or make entries invisible in the drawing BOM). It's a bit of a let-down, because Inventor can now easily handle this scenario with model states, but will show '0' entires in the BOM, which is rather silly. Not sure how this was passable for the test group. Perhaps they lacked power-users.
Manually hiding entries means there's a brand new area where human error can occur. The point of modern CAD is to automate mundane and/or repetitive tasks, not create more.
TLDR: The suppress behavior should be universal and predictable: Make the part/feature/item/etc. dissappear completely.