Inform users on unsaved data when switching between/starting new TaskFlows?

Question

Hi
In our case, we are using the multiTaskFlow concept to dynamically start new TaskFlows in Tabs. The simple requirement is to have a generic way to inform users on modified unsaved data when switching or starting new TaskFlow
I did research in google for answers, but did not found anything working.
For example, I added following checks (df=dirtyFlag) just before switching between Tabs and Menu-items:
boolean df1 = am.getApplicationModuleDef().isDirty();
boolean df2 = ControllerContext.getInstance().getCurrentRootViewPort().isDataDirty();
boolean df3 = ControllerContext.getInstance().getCurrentViewPort().isDataDirty();
boolean df4 = AdfFacesContext.getCurrentInstance().getDirtyPageHandler().isDataDirty();
boolean df5 = am.getTransaction().isDirty();
boolean df6 = am.getDBTransaction().isDirty();
boolean df7 = bindingContext.getDefaultDataControl().isTransactionDirty();
boolean df8 = dcBindingContainer.getDataControl().isTransactionModified();
boolean df9 = dcBindingContainer.getDataControl().isTransactionDirty();
Start Application and perform a TAB switch without searching or changing anything
df1 true
df2 false
df3 false
df4 false
df5 false
df6 false
df7 false
df8 false
df9 false
Within a TaskFlow I perform a SEARCH and perform a TAB switch, flags change to following:
df1 true
df2 true
df3 true
df4 true
df5 true
df6 true
df7 false
df8 false
df9 false
I MODIFY values within TF and perform a TAB switch, flags remain same and regardless what I do, they remain so:
df1 true
df2 true
df3 true
df4 true
df5 true
df6 true
df7 false
df8 false
df9 false
Do you know a working approach?
Thanks in advance!

Answer 1

Hi,
its for when you leave a view, not when you switch task flows in a page. To get back to your question, one thing you forgot to mention is what data control state is it that the task flows have: shared or isolated? If they have a shared state then only a single transaction is on and you should be able to tell the dirty state by calling
boolean df2 = ControllerContext.getInstance().getCurrentRootViewPort().isDataDirty();
However, if the task flow is in isolated mode then you will need to get a handle to the data control frame used by that task flow.
BindingContext ctx = oracle.adf.controller.binding.BindingUtils.getBindingContext();
String frameName = ctx.getCurrentDataControlFrame();
DataControlFrame frame = ctx.findDataControlFrame(frameName);
boolean isDirty = frame.isTransactionDirty();
//see: http://docs.oracle.com/cd/E15051_01/apirefs.1111/e10653/oracle/adf/model/DataControlFrame.htmlHowever, this information is only available from within the task flow, which means to check this from the outside you need to provide a mechanism to get to this information (contextual events would be an option. You define a contextual event receiver on the task flows that when called checks the current transaction state and then "fires" the answer back to the caller, which then obtains a map of task flow transaction states to check before navigating away or switching task flows.
Frank
Edited by: Frank Nimphius on Apr 11, 2013 2:48 PM