page items values don't get unset if the conditional flow through a task changes #3
Description
If you have a task definition with a conditional flow and the user first takes on path through the flow but then back tracks and changes the flow condition, meaning they take the alternative path, then the page items from the first path are still set.
This can cause problems with data connectors that don't expect both sets of page items to be passed through.
One possible solution for this would be to maintain a queue of pages encountered when passing through the task - pushing pages onto the queue when the Next button is pressed and popping them off when the Previous button is pressed. At the end of the task, the list would contain only the pages making up the final workflow. Data items belonging to pages not on that list would then not be submitted to the data connector.
This approach means that the user can change their mind about the task workflow as many times as they like and still have access to data items for each page (so they won't lose information if they backtrack then come back down the same route) but only the final workflow page items will get submitted.