n Activiti 6, the direction of an exclusive gateway is not normally chosen directly from a form element like a radio button. The gateway evaluates the conditions defined on the outgoing sequence flows, usually based on process variables.
You can absolutely use a form field to influence the decision, though. For example, store the selected radio button value as a process variable, then define expressions/conditions on the outgoing flows that check that variable and route the execution accordingly.
Something like: user selects option A → variable gets value A → gateway condition ${choice == 'A'} sends the process down that path.
The same idea applies to other workflow decisions too — the UI collects data, and the process engine handles the routing logic. If you’re also dealing with payment or external workflow integrations, understanding the underlying provider flow can help; this useful guide on acquiring banks gives a good overview of how transaction routing works on the payment side.
Hope that helps. The key point is: don’t try to make the form control the gateway directly; make the form set variables and let the BPMN logic decide.
