This content has been marked as final. Show 4 replies
Assuming that the "before refresh" is not stopped by that Cancel, how about you break things up into 2 DAs. Instead of
in DA1, you set the value of some item.
DA2 is set to run on the same event as DA1 but will be after DA1 and will refresh the region. However it will be conditional on the value set in DA1.
Not 2 DAs(duh), you obviously need one to do the confirmation before the one that fires the refreshso my idea might not work unless you can use apex.confirm or something else in such a way that it will only set a value but not submit the page. Sorry.
Edited by: Kofi on Nov 15, 2012 4:41 PM
Well I guess the situation is that "before refresh" fires after the signal to refresh the region has been heard by the server.
In other words, when I paginate through the region, I click the link to paginate, it wants to refresh but encounters my DA that fires before the region actually refreshes. This is fine. My code fires correctly and prompts "are you really sure...?". Problem is, the answer from the confirmation is ignored (either OK or cancel permits the pagination to continue).
When I've used a confirmation with a "before page submit" in this same manner, answering "cancel" to the confirmation would also abort the submit process.
So I want the same sort of "cancel" action to abort the region refresh in this case, but seems like it's ignored.
I am now thinking this is a bug.
In looking at Apex's help when you click on 'Action' in a DA, it says this about "Confirm":
•Confirm - Displays a confirmation dialog. If the user chooses 'Cancel' then the proceeding actions are not executed and the current event is canceled.
The bolded part above is what is not happening...the event is continuing.
FYI all...in case anyone runs across this. Oracle now has bug# 15916356 for this. I'm not sure when it'll be corrected though.