Taskflow Issue.

Question

Use Case
I have a search page for searching Employees. This is a taskflow(employee-search.xml). I have edit/create link on the search page which calls another task flow (employee-edit.xml) for the edit/create of employee record. The employee edit taskflow has data-control-scope set as "*isolated*" and transaction set as "*new transaction*" . I want this setting because i should be able to be able to start a new transaction to commit the record. On save i commit the record and navigate back to the search page using task flow return activity. The problem is i am not able to see the changes made when i navigate back to the search page.I am able to see the changes on the search page with a new session though .I understand that because of my edit employee task flow settings, ADF creates new transaction where datacontrol frames for both the task flows are different.So my search page(search task flow)( which already opened a transaction ) is not able to see the changes made by the edit task flow. I could have made data-control-scope ="shared" and transaction="requires transaction" on edit employee task flow to make the changes visible(since they share the same datacontrol in the same transaction) but then i require a commit on the search page which will be quite odd to the users.
How do i achieve the the desired results with out sharing the the data control scope and begining the new transaction on the edit employee taskflow ?

Answer 1

Hi Frank,
I added the execute method as u suggested. But it still doesn't work.
Search task flow is embeded as a region into a jsf page. Search task flow has the data-control-scope set to "Shared" , transaction option to "new transaction" . Edit task flow has the data control scope set to "Isolated" and transaction option set to "new transaction. My understanding from steve's blog is that in this scenario , two new transactions will be started each having its own data control frames.
More Information:
Search task flow uses a read only view object. Edit task flow uses another updatable view object.