Hello,
We have an approval workflow in which we call several subworkflows as in below picture. (Picture 1)
Our questions are;
- Is it possible to pass workflow variables from one workflow to another?
- Can we pass workflow variable to the subworkflows?
- Can we pass sub-workflow variable to the parent workflows?
Picture 1
You can set the variable scope, when you define a variable (e.g. in a SQL select node) to 3 values:
- Node
- Job
- Public
usually "job" does the trick, for passing variables back to the parent you might need public
Edwin
Hello,
- We have defined a public variable in sub workflow (Picture 1)
- We tried to reference to this variable in parent WF (Picture 2)
Variable was not reachable.
Is there a step we are missing?
Picture 1
Picture 2
Here is the relation between parent and subworkflows.
There is a bug in Aveksa that prevents the use of "variable scope on job level" safely.
Yes, using public scope solves it most of the times. But if job is "very heavy" on the server you could cause a database lock.
We had a lock last week in production environment, so use public scope with caution! IF any of following applies to your workflow, I would not recommend using "public scope":
Making a support case on this as we speak, so hopefully this will be fixed in 7.0.1
You can set the variable scope, when you define a variable (e.g. in a SQL select node) to 3 values:
- Node
- Job
- Public
usually "job" does the trick, for passing variables back to the parent you might need public
Edwin