Applies to JDeveloper: 11.1.1.2, 11.1.1.3
Today I tried if the Bug (discussed in http://forums.oracle.com/forums/message.jspa?messageID=3568706) is still reproducible.
And sadly to say: “Yes the bug still exists!”
The behaviour changed a bit but the table filtering feature still does not working as expected if used INSIDE PAGE FRAGMENT/TASKFLOW.
So take a look at the viewlet where I shortly explain the buggy behaviour.
Download Testcase: http://www.box.net/shared/sviqlzzobp
Related resources
http://forums.oracle.com/forums/message.jspa?messageID=3568706http://forums.oracle.com/forums/thread.jspa?threadID=2157454
Hi Andreas,
ReplyDeleteIt's March 2010 and the bug is still there :(
Did you find any workarounds for this issue? In our case we have a pre-set filter and when we try to change that to some other value it gives an sql error as well.
Sample TestCase,
http://www.box.net/shared/lztqffqdsu
Thanks,
-Sreeja.
Hi,
ReplyDeletethe table filtering feature still does not working as expected in Jdeveloper 11.1.1.3.
Follow the newest information on http://forums.oracle.com/forums/thread.jspa?threadID=2157454
Currently the following is logged
bug 8602867, "FILTER CRITERIA FOR A TABLE NOT RESTORED WHEN INSIDE A TASK FLOW"
*** 08/30/10 02:31 pm ***
RELEASE NOTES:
]]After the fix if a user re-enters a taksflow and does a filtering operation,
]]results from the previous filtering will not be displayed.
REDISCOVERY INFORMATION:
see bug text.
WORKAROUND:
None
*** 08/30/10 02:34 pm *** (CHG: Fixed->11.1.1.4.0)
*** 08/30/10 02:34 pm *** (CHG: Sta->80)
*** 08/30/10 02:43 pm *** (CHG: Fixed->11.1.2.0.0)
Andreas.