Maybe you could try:
First process has a sub-process for iterate the first collection, while you are iterating the first collection, you will do a comparison through a XSLT transformation, where you will use a "for-each" tag to iterate each element inside the second collection, then you can compare this value with the actual value of the first collection.
1 person found this helpful
As I understand, you loop over collection 1 and want to process collection 2 for those rows that match the attribute for the selected/current row in collection1, right?
If so you could simply try to do a dataassociation/copy rule where you copy collection2 to another variable with the collection1 attribute as a selection condtion. For instance, if collection1 contains departments, and collection two employees:
$collection2/employees/employee[debtNo=$collection1Row/deptNo] => $deptEpmloyees
Then then do the innerloop over all rows of $deptEmployees.
By the way, this seems like something I'd prefer to do in BPEL, since it seems to me like a more lower granual piece of functionality that would clutter up your Business Process Model.
And BPEL is handier for these kinds of constructions.
I will try this. The 2 collections need not be of same size right?