I’ve run into a Service Connect problem I can’t seem to figure out. I have a sub workflow that I can see is receiving the correct data from the main workflow in the Start node:
Hi,
Check if your sub-workflow has the same schema as the parent workflow
From the SC documentation:
To pass content of msg:wfl/msg:usr node of main workflow to the sub-workflow, select the Pass msg:usr section check box.
To use message extension and process variables from the main workflow in a sub-workflow, you have to manually create the same structure (message extensions and process variables) in the sub-workflow. Otherwise, XML Mapper and XPath Builder will not show those structures in the sub-workflow.
The create sub-workflow schema button might be useful.
Simon
Thank you so much for your response. I think my biggest problem is that the incoming data is in XML format (I’ve primarily worked with CSV for complex workflows). This is to create AP invoices. It has a main portion that is the header info and another “node” that is for all the separate lines on the invoice. I’m passing that node to get it to cycle and I can see that it’s passing the correct data to the start node of the sub workflow but that’s as far as it gets. I only have the line node schema as an extension in the sub workflow. I’m not sure how to add it to the main workflow as it only seems to see the first iteration of the invoice line node from the file.
Thanks
Jason Duncan
Is it not possible to access the msg:dta info that is being passed to the sub workflow? As I said I can see the data reaching the start node of the sub workflow but no matter what I connect (variables, call context, schema) the data will not show up in the next step.
