As per my understanding there is no clear restrictions as such. Storing data in Property or Header consumes RAM I guess so in case if you are storing huge data it might affect performance of overall tenant ( lets say you are running multiple flows parallelly with huge data stored on properties ).
So its your call to model your iflow in such a way( As there is no concrete answer I can give as per the records but you need to manage efficiently as it consumes RAM ).
Thanks for your answer on this, Sriprasad. You have given me some good advice in this and several other questions I have brought up on this platform. I really appreciate your willingness to share your knowledge with others.
I've tried in previous integration work to never assign a whole XML to a property and instead use a data store operation. Unfortunately a requirement I am currently working on would make this method very inefficient, so I think I will have to go the exchange property route.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.