Flow Dependency
Which flow calls which through ProcessDirect and JMS, and what is not connected.
When to use it
Section titled “When to use it”- You change a shared flow and want everything that calls it.
- You want to spot an address nobody listens on before it fails at runtime, and listeners nobody calls any more.
- You want to know which flow serves an HTTP path.
How it works
Section titled “How it works”The artifact sync reads the adapters of every flow: ProcessDirect addresses and JMS queues by direction, with externalised parameters resolved, and the address each sender adapter listens on. Per address the page pairs the two sides and gives a state: connected, nobody listens, nobody calls, set per message or parameter not set.
Good to know
Section titled “Good to know”- It is a table, not a graph as in version 1. It answers “who calls this” and “what is broken” directly.
- An address set per message (
${property.x}) cannot be paired. The flows it would reach show as “nobody calls”, which is why that state is neutral and not an error. - ProcessDirect addresses and JMS queues are local to a tenant, so the page covers one tenant.
- As of the last artifact sync.
Credits
Section titled “Credits”Thanks to Umesh Reddy for reporting the use cases behind this feature.