True, but if you take that to the extreme there are six checkboxes, 37 icons, and 999 possible notification IDs, for a total of 2,365,632 possible combinations. So writing a flow that is as flexible as possible would be a bit silly.
You could write a flow handling only the cases you need, but that means updating the flow every time there's a new case or (what I do) having a "notification manager" flow plus a pair of flows for every case, one that calls the manager and passes it identifying info about the case (typically part or all of the second flow's name) and another that is called by the manager, using that info, to display the notification for the case.
There could be other ways to handle it but none less complicated than those. I'd rather have the ability to use variables for everything (even checkboxes, somehow).
