AS A Service-Module user
I WANT predefined variables to continue through MCQ downstream paths
SO THAT I do not have to redefine the same parameters after every MCQ branch
Description
Currently, when a service reaches an MCQ node, the selected MCQ path may trigger a new background service/DSL flow. Parameters defined before the MCQ are not passed forward to downstream nodes.
Example: Service A defines a value in an Assign node before the MCQ. After the user selects an MCQ option, all downstream nodes on the selected path should still receive that predefined value automatically.
Service A:
Assign (userName = "Mato")
↓
MCQ
↓
Next Service → Service B
Service B:
MCQ
↓
Next Service → Service C
Service C:
MCQ
↓
Message to Client: "Hello {userName}"
The variable userName is assigned only once in Service A.
After passing through multiple MCQ nodes and Next Service transitions, the variable must remain available in all downstream steps without requiring reassignment.
Variables propagated through MCQ nodes must also be visible and selectable in subsequent node configurations, including nodes located in chained services.
AC checklist
Services to test with:
services_2026_06_10_09_31_04.zip
AS A Service-Module user
I WANT predefined variables to continue through MCQ downstream paths
SO THAT I do not have to redefine the same parameters after every MCQ branch
Description
Currently, when a service reaches an MCQ node, the selected MCQ path may trigger a new background service/DSL flow. Parameters defined before the MCQ are not passed forward to downstream nodes.
Example: Service A defines a value in an Assign node before the MCQ. After the user selects an MCQ option, all downstream nodes on the selected path should still receive that predefined value automatically.
Service A:
The variable userName is assigned only once in Service A.
After passing through multiple MCQ nodes and Next Service transitions, the variable must remain available in all downstream steps without requiring reassignment.
Variables propagated through MCQ nodes must also be visible and selectable in subsequent node configurations, including nodes located in chained services.
AC checklist
Services to test with:
services_2026_06_10_09_31_04.zip