Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

BPM Repeat stage in parallel

edited Jun 4, 2021 6:33AM in Self Service Procurement 7 comments

Summary

BPM Repeat stage in parallel

Content

I have a requisition with 2 lines.

When we are using the feature of "Repeat Stage in Parallel" for Requisition BPM, the path /task:task/task:payload/ns4:findReqHeaderDimensionResponse/ns4:result/ns2:RequisitionLine/ns2:RequisitionLineId always returns the first Requisition Line ID twice.

Am I using the right path or am I missing any setup?

------------------------------------------------------------------

I tried hard-coding the index in the above path as follows and it worked for hard-coding:

/task:task/task:payload/ns4:findReqHeaderDimensionResponse/ns4:result/ns2:RequisitionLine[1]/ns2:RequisitionLineId

/task:task/task:payload/ns4:findReqHeaderDimensionResponse/ns4:result/ns2:RequisitionLine[2]/ns2:RequisitionLineId

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!