Dear experts,
Somehow I conclude designing scenario in integration directory may not be that difficult than mappings are.
For me frankly speaking,i could never understand how removecontext work,splitbyvalue combinations work or
collapsecontext work.Though I have seen pretty number of tutorials where good examples are given and going at
first site to them you understand.But in practical cases example EDI files where xml structure looks infinite ,relating these function doesnot
help much as I cant visualize whole xml(source) in mind then how can I predict what target I want.At times I use removecontext,it works by fluke.
What I mean to say if I do anything in mapping and I get positive results,they all look fluke to me internally and doesnot make me feel confident.
I take payload source ,put in test and see queue of variables,but then going back to start of xml and try to figure out each and every token looks so laborious that I feel to leave thereof.
I am sure there is a clear cut method to actually use mappings effectively and understand and relate to your day to day work.
I am looking at present , best practices to be shared in this thread for using mappings or how are the best ways we can avoid mappings completely ?