How about entering your logic on a Groovy Script component and that would set some iflow context variables that would be used by the xpath for data extraction. Your script would be able to dynamically set what the xpath should gather from the payload.
Have you tried it?
If that doesn't work, I would simply add xpath extraction rules for all attributes in the payload, So I would be able to mapp whatever I wanted.
BTW, did you know you can convert your payload into OpenAPI syntax, upload it to Cloud Integration and use it to viasually map the inbound/outbound attributes?
Could you please elaborate a little more on the comment? I didn't quite understand what you really want to achieve. Perhaps if you give a more concrete example it would help.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.