This content has been marked as final. Show 6 replies
Maira wrote:You can split your current dynamic action into two dynamic actions. In the 2nd DA, you can specify a condition type such that it doesn't execute if there are errors.
only in PL/SQL there is such option...
Thanks for your replay but problem is not solved...
The question is : how do you know (code wise) that the submit page button that calls the default "ApplyMRU" Process has FAILED?????
Is there a way to catch an ApplyMRU process error...???? (There is only a Success Message and a Failure Message... which is text... and I can not get it from any other process...)
Sorry for overlooking the fact that your first DA submits the page.
When the first dynamic action executes, it submits the page and the next dynamic action (in sequence) executes. The submit calls the ApplyMRU process. I am not sure if there is a direct way to wait for the successful execution of the ApplyMRU process before triggering the second dynamic action.
Is there a specific need to execute the second action as a dynamic action? Is it possible to replace the same with a on-submit pl/sql process (called after the ApplyMRU)? That way, the second process won't be called if the ApplyMRU had failed.