Forcing Task Flow instances with Shared Data Control to use different view object instances
If you have have a task flow designed to use shared data control, and still don't want different instances of task flows to use same view object instances, then this post is for you. Use case: Multiple instances of task flow should share same transaction context, however each UI should work independently when they are embedded in a parent page. As of now, there is no direct support for this. In this post I'm sharing a work around solution for this kind of scenario. Solution: As I said earlier, this is just a work around solution, and intended to give you some idea on the implementation. Feel free to modify the code in the attached sample to meet your use cases. Step 1 . Edit the iterator used for for those pages fragments which needs to work independently, and alter binding for the view object instance used for this iterator to use an EL. EL takes the view object instance name from a PageFlow scoped variable. <iterator Binds="#{pageFlowScope.VOInstName}...