Hacker News Reader

There certainly is some conceptual overlap in defining an experience/decision making process as a directional graph.

However, to my limited knowledge of this, BPMN doesn't quite differentiate between its activities in terms of "does this need user interaction" vs "process this thing". In our case, we have pane nodes for the "need user interaction" activity and processor nodes for the "process this thing" activity.

View on HN

> BPMN doesn't quite differentiate between its activities in terms of "does this need user interaction" vs "process this thing".

User interaction is a distinct BPMN Activity Type, so BPMN can make this distinction quite unambiguously. Concrete BPMN implementations, IIRC, use varying amounts of the spec and have varying degrees to which Activity types are functionally rather than merely visual distinguished, so a particular BPMN tool may or may not make the distinction or treat it as significant.

That's super helpful context, thanks.

Reply on news.ycombinator.com