When accessing the workflow inputs via the workflowtoken, the token remains the same, when called from a nested workflow, but the inputproperties are not available.
[javascript] accessing inputproperties for the rootworkflow. When using this code from a workflow with a dummy inputfield :
var oWorkflowToken = workflow
System.log("workflow :" + workflow)
System.log("Inputparameters object : " + JSON.stringify( oWorkflowToken.getInputParameters(),null,2))
Get an object containing the inputparameters with their values. When request the workflowtoken Id from a nested worklow, I get the same Id as when requested from the rootworkflow.
System.log("Workflowtoken id : " + oWorkflowToken.id )
When request the workflow name, from a nested workflow in this fashion I get the workflow name for the rootworkflow, not the nested workflow.
System.log("Workflowtoken name : " + oWorkflowToken.name )
VMware Aria Automation Orchestrator 8.x
Calling several workflows simultaneously runs the called workflows synchronously as part of the run of the calling workflow. The calling workflow waits for all the called workflows to complete before it continues. The calling workflow can use the results of the called workflows as input parameters when it runs its subsequent schema elements.
You call several workflows simultaneously from another workflow by using the Nested workflows element. You can use nested workflows to run workflows with user credentials that are different from the credentials of the user of the calling workflow.
Log in to the Automation Orchestrator Client.
Navigate to Library > Workflows, and select your workflow.
Select the Schema tab.
Drag a Nested workflows element from the Generic menu to the appropriate position in the workflow schema.
Click Add Workflow, and add a workflow to the Nested workflows element.
Repeat for all the workflows you require.
To finish editing your workflow, click Save.
You called several workflows simultaneously from a workflow.