You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to some issues within \ezcWorkflowNodeSubWorkflow it is not possible to pass variables from the parent workflow to a sub-workflow and vice versa.
There are three distinct problems:
When a sub-workflow is resumed variables from the parent workflow are not mapped to the variables names in the sub-workflow (based on the variable mapping configuration): zetacomponents/workflow/src/nodes/sub_workflow.php:166
When the waitingFor variables from the sub-workflow are being fed back to the parent workflow the names are again not mapped back to the variables names in the parent workflow (based on the variable mapping configuration): zetacomponents/workflow/src/nodes/sub_workflow.php:191-194
The \ezcWorkflowNodeSubWorkflow::passVariables() method does not check whether a variable exists in the from workflow resulting in an exception if a variable is mapped but not yet set on the from workflow.
I'll provide a pull request to fix these issues.
The text was updated successfully, but these errors were encountered:
sgehrig
pushed a commit
to teqneers/Workflow
that referenced
this issue
Jan 17, 2018
Due to some issues within
\ezcWorkflowNodeSubWorkflow
it is not possible to pass variables from the parent workflow to a sub-workflow and vice versa.There are three distinct problems:
zetacomponents/workflow/src/nodes/sub_workflow.php:166
waitingFor
variables from the sub-workflow are being fed back to the parent workflow the names are again not mapped back to the variables names in the parent workflow (based on the variable mapping configuration):zetacomponents/workflow/src/nodes/sub_workflow.php:191-194
\ezcWorkflowNodeSubWorkflow::passVariables()
method does not check whether a variable exists in thefrom
workflow resulting in an exception if a variable is mapped but not yet set on thefrom
workflow.I'll provide a pull request to fix these issues.
The text was updated successfully, but these errors were encountered: