Search dialog navigation behavior

Search dialogs present users with one or more navigation options: next, previous, finish, and cancel. These options are presented as buttons in the navigation frame at the bottom of the content window. If included, they behave according to the following guidelines:

Search
The user clicks on Search button to perform a search request.
  1. Check if function userSavePanelData() exists, and run it if it does exist.
  2. Run function userValidatePanelData() if it exists. If the input that is found is not valid, you can display an alert message to notify the user in this function, and return a false value. Otherwise, simply return a true value at the end of the function.
  3. If false value is returned, the criteria panel will still display with all the entered input fields pre-populated. If true value is returned, the user will be redirected to the result panel.
Refine
The user clicks on the Refine button to go back to the criteria panel. When the user is brought to the result panel, by default, the user has an option to click on the Refine button to go back to the criteria panel with all the entered criteria fields pre-populated.
Cancel
Displays a cancel confirmation dialog. If the user clicks OK, submitCancelHandler() is called, then the parent frame's cancel method is run.
Result Navigation Buttons
By default, there are two buttons on the result navigation panel: Refine and Cancel. These buttons and their actions can be customized by creating a partial dialog XML file. The following example shows a customized XML file for the result navigation panel: 

<?xml version="1.0"?>
<dialog resourceBundle="samples.samplesNLS"
        windowTitle=""
        finishConfirmation=""
        cancelConfirmation="cancelConfirmation"
        finishURL="DialogNavigation">
    <button name="custom" action="customAction()"/>
    <button name="refine" action="refineAction()"/>
</dialog>
Result Navigation Panel
By default, there is a navigation panel at the bottom of the result panel. If this navigation is not required, it can be turned off by simply assigning a value of mcccontent to the attribute target of <resultPanel> in the XML file as below: 

<resultPanel url="/webapp/wcs/tools/servlet/tools/samples/DumpRequest.jsp"
             target="mcccontent"
             navigationPanelXMLFile="samples.sampleSearchDialogRefine"/>