HomeOracle Page 4 - Data Manipulation and More for HTML DB Applications
Close Popup Window - Oracle
In this conclusion to a three-part series covering the addition of validations, computations, and processes to an HTML DB application, you will learn about data manipulation, manually creating a web services process, and more. This article is excerpted from chapter 13 of the Oracle HTML DB Handbook, written by Lawrence Linnemeyer and Bradley Brown (McGraw-Hill, 2006; ISBN: 0072257687).
The final type of process, which is new to version 2.0, is the Close Popup Window type process. This process is used on a page that’s the source for a pop-up window. The process, when executed, will close the pop-up window and according to the wizard refresh the calling window. You can successfully use this process to close a pop-up window if there is no branch defined; however, the refreshing of the calling window does not occur.
In the process-creation wizard, when you select to create a process of this type, all you have to specify is its name, a sequence, and the point at which the process will be evaluated. If you want to add a condition to the process, you must edit the process after it is created.
Editing Processes
To edit a process, click on the name of the process on the Page Definition page. This will open the Edit Page Process page. The Edit Page Process page is primarily the same for all types of processes; the biggest difference is the Sources section, which is dependent on the process type.
Most of the information entered in the process-creation wizards can be changed through the edit page. However, the one thing that can never be changed is the process type. In addition to the elements defined during creation are the standard sections for Authorization, Configuration, and Comments.
One attribute found in the Processing Point section, in addition to the sequence and the processing point, is the Run Process field. This field has two choices that allow you to specify whether the process should be run once per page visit, which is the default, or once per session or when reset. The latter option is very useful for tasks that only need to happen once per unique visit to the application.