Is it possible to pass information from one iteration of a cycling sub-workflow to another? Seems that I can only pass data from the parent workflow to the sub-workflow via inherited containers, and back to the parent via a response container. I’m hoping someone has found a way to pass data between cycles of the sub-workflow.
Has anyone ever tried storing data in the BpmDataSet of the BO objects as a way of passing information between sub-workflow cycles? I wonder if that would work?
I haven’t found a clean way yet, but then again i haven’t wasted a lot of time trying either. I have in the past when i needed to do that either stored the variables needed in some UD field on the tables available in the work flow or UD tables (this assumes you’ll do an update to those records). I typically avoided doing this to records i was working on and either used a UD table outside the process. For performance reasons i moved on to doing a DB element, did a simple update statement to a custom table for this purpose. It was fast and easy to generate the query and return the results dynamically through each iteration. Just store the values you want to pass to the next cycle in whatever place seems practical or functional in your workflow.