How does everyone interrogate itemFlows around the system - just graphically?
Essentially, yes this is how I would do it. If there's something useful to be communicated, then I draw a diagram to show it. Otherwise I don't bother drawing a diagram.
However, I also think of ItemFlows as part of the Interface Specification (and I'm sure I'm not the only one). So for example, to specify an interface between 2 Blocks, I would:
i. define 'data items' (using e.g. signals, Blocks etc) for all the signals in taht part of the system
ii. create my Blocks
iii. add Ports to the Blocks
iv. type the Ports using an InterfaceBlock (and conjugation for the opposite one)
iii. define flowproperties on the InterfaceBlock that are Typed by the 'data items' created in step (i) above
v. draw ItemFlows and Connectors between my Ports, and use my 'data items' when I select "Information Flows Realized"
I would then use my diagrams and tables of flowproperties & 'data items' to generate an interface specification (ICD) type document as would normally be requested by a customer. For any given Connector between 2 Ports (i.e. one specification of one interface), the ICD will list only those ItemFlows (and thus only those 'data items') that pass over that particular interface.
There's nothing novel or unique in all that. And some of it is just 'the way that EA does it' rather than perhaps a more grammatically-correct version of the SysML spec. But as you requested, this is how I do it