How do I get a popup window to stay open with a validation failure?

Question

Environment:
APEX 3.1.1.00.09 on AIX 5.3
Oracle 10.2.0.2 EE on AIX 5.3
Sample app on apex.oracle.com:
Workspace: galway
User: gwicke
Pass: gwicke
Steps:
1- run Page 3
2- select J & B Marketing from drop down
3- select only contract from drop down
4- click on Edit Existing Contract
5- click on Add New Builder
6- Enter the same builder from calling page: Builder Name: Alvarez Construction City: Baton Rouge State: LA
7- click Add Builder
The original version of this page would add the new builder to the database, pass the information back to the calling page and close the popup window. Cool.
I have added a validation on the popup page (Page 4) to check for an existing builder with the same name and city.
What I'd like to have happen is the popup window stay open so the user can see the error message with the instructions for them to click on the CANCEL button and then select the builder from the drop down list. When they click the CANCEL button I need to have the window close.
What is happening is the window is closing as soon as the Add Builder button is clicked.
This is because there is a region called 'scripts' that contains javascript to submit the page and close the window and the condition on the region is only that the Builder Name is not null. So, the good news is that I understand why the window is closing but I'm not sure the best way to keep it open when the error condition happens.
Thanks very much for your help. I'm sure you recall everything about this app you helped me with many months ago. NOT!! :-)
-gary

Answer 1

Gary, I think I've got it working the way you want.
1. I added a conditional branch to page 4 which fires on the not exists builder condition condition.
2. I disabled the reset page process. With that running, the conditional branch to page 4 woul always fire because the builder name and city were always cleared by the time the branch executed.
3. I noticed that the new builder did not show up in your select list until I refreshed page 2. I haven't had a chance to look at that. Maybe a branch back to page 2 from page 4 after successfully loading a new builder will take care of that.
Bob