I've been searching for days for detailed information about what mapped variables are and how they are related to the MapValues method in PersistenceParticipant, but all I can find is information about how to use them, rather than what they are for or when
to use them.
If I had to guess, I would say that mapped variables are added as write-only values at some point between the CollectValues and MapValues stage, but at what point do we restore these mapped variables? The PurchaseProcess sample application is quite confusing,
as it stores the requestForProposal mapped variable in the instance store as well as in the external XML store, but the requestForProposal is reloaded from the instance store without consulting the external XML store, despite being marked as write-only during
the save process. What is the correct way to load mapped variables? I imagine that the SQL Server instance store does respect the write-only modifier, yet in the HiringRequestProcess sample, I can't see where the workflow loads the hiringRequestInfo
I suppose my actual question is this: I have a bunch of business entities which are persisted in a database elsewhere. I would prefer that the workflow not persist its own copy (especially if it ends up trying to persist the whole object graph) but instead
reload the entities from the database as necessary. I don't thin
View Complete Post