you can mix control flow and object flow in an activity diagram, but you don’t do it with dashed arrows. uml expects explicit object nodes and object flows, which can fan out to multiple actions without forks.
plantuml is the blocker here. its activity diagram support is control-flow first, and object flow is very limited. you can model action → object → action, but not a clean parallel data flow running alongside the control flow like the spec shows.
bottom line: uml supports combined control and data flow, plantuml mostly doesn’t. if you need proper object flow semantics in an activity diagram, you’ll hit a wall with plantuml.