Hi Sree,

Below are sequence of steps that needs to be followed to implement the required functionality.

Steps which needs to be followed to implement this requirement.

1. Extend the CO and personalize the page with GO button and refer the extended CO.
2. Capture the GO button event in the extended CO in ProcessFormRequest. ( Don't call the super.processFormRequest() , because that will create the PA).
3. Use CallableStatement to call the package and pass the Supplier Details.
4. Based on Yes/No returned from the package, write IF block.
5. If the value returned is YES, then use the OADialogPage to show the Dialog Page( Refer Development guide for implementation of Dialog Pages)
6. In the YES button click of OADialogPage, call the super.processFormRequest() to create the PA.
7. In case NO button is clicked, you can either show a message on OAF Page, that Supplier does not qualify for PA or you can put some logging.
8. Same thing you can do when the Package returns No/N in STEP-3.

Thanks Sameer for detailed steps.

Regards,
Sree

Hi Sameer,

Step mentioned at 6 causing problem:
6. In the YES button click of OADialogPage, call the super.processFormRequest() to create the PA.

Here the problem is, once the button on dialog box is clicked, the pageContext changed and when it goes to super.processFormRequest(), (pageContext.getParameter("GO") != null) becomes false and not firing the actual submission of PA.

Please suggest if you think there is any way to pass the parameter of "GO" to super class after accessing dialog box.

Regards,
Sree

Hi Sree,

Your processFormRequest() method will look like this


public void processFormRequest()
{


if(pageContent.getParameter("Go")!=null)
{
"Create the OADialog Page"
}

if("When Yes button of OA Dialog is clicked" )
{
super.processFormRequest();
}

if( "When No button of OA Dialog is clicked")
{
"Do some logging> OR < Display a message on the Page"
}

}


So on click of YES button of OA Dialog, it will not go inside the GO Button block, instead it will go in IF block where you have handled the YES button click.

Hope this clarifies.

Hi Sameer,

I have tried this in sample tutorial, kind of :
My extended code

package xx.oracle.apps.fnd.framework.toolbox.labsolutions.webui;



import java.io.Serializable;



import oracle.apps.fnd.common.MessageToken;

import oracle.apps.fnd.framework.OAApplicationModule;

import oracle.apps.fnd.framework.OAException;

import oracle.apps.fnd.framework.OAViewObject;

import oracle.apps.fnd.framework.toolbox.labsolutions.webui.EmployeeCreateCO;

import oracle.apps.fnd.framework.webui.OADialogPage;

import oracle.apps.fnd.framework.webui.OAPageContext;

import oracle.apps.fnd.framework.webui.OAWebBeanConstants;

import oracle.apps.fnd.framework.webui.TransactionUnitHelper;

import oracle.apps.fnd.framework.webui.beans.OAWebBean;



import oracle.apps.fnd.framework.webui.beans.form.OASubmitButtonBean;



import oracle.jbo.domain.Number;



public class xxEmployeeCreateCO extends EmployeeCreateCO {



    public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)

    {

    

         if (pageContext.getParameter("Apply") != null) 

         {

         

             OAException mainMessage = new OAException("You are creating contract agrrement relationship with different supplier");

             OADialogPage dialogPage = new OADialogPage(OAException.WARNING, 

               mainMessage, null, "", "");



             String yes = pageContext.getMessage("AK", "FWK_TBX_T_YES", null);

             String no = pageContext.getMessage("AK", "FWK_TBX_T_NO", null);



             dialogPage.setOkButtonItemName("DeleteYesButton");



             dialogPage.setOkButtonToPost(true);

             dialogPage.setNoButtonToPost(true);

             dialogPage.setPostToCallingPage(true);



             dialogPage.setOkButtonLabel(yes); 

             dialogPage.setNoButtonLabel(no);

             //skipped the form value to pass

             pageContext.redirectToDialogPage(dialogPage);

             

         }         

      else if (pageContext.getParameter("DeleteYesButton") != null)

          { 

              super.processFormRequest(pageContext, webBean);

          }        

         



        super.processFormRequest(pageContext, webBean);           

       

         



    }     // end processFormRequest()

    

    

    



}

But when I click the Yes button on dialog box it goes to super class oracle.apps.fnd.framework.toolbox.labsolutions.webui processFormRequest but if if skips the apply button logic from main class , so actual saving logic never fires.

package oracle.apps.fnd.framework.toolbox.labsolutions.webui;



...



  public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)

  {

    // Always call this first.

    super.processFormRequest(pageContext, webBean);



    OAApplicationModule am = pageContext.getApplicationModule(webBean);

    

    // Pressing the "Apply" button means the transaction should be validated

    // and committed.

    if (pageContext.getParameter("Apply") != null) 

    {

      // Generally in the tutorial application and the labs, we've illustrated

      // all BC4J interaction on the server (except for the AMs, of course).  Here,

      // we're dealing with the VO directly so the comments about the reasons

      // why we're obtaining values from the VO and not the request make sense

      // in context.  

      OAViewObject vo = (OAViewObject)am.findViewObject("EmployeeCreateVO1");

Regards,
Sree

Sree,

You need to first understand the execution sequence of the methods in your extended controller.

When you click YES button on the Dialog, then ProcessRequest() gets executed first, followed by the IF Statement of your ProcessFormRequest() where you are capturing the "Yes" button click.

In your extended controller, have processRequest() method, which will call super.ProcessRequest(). This super.processRequest() should only get executed once, when u land on the extended controller page. When you click the Go button, set a parameter Temp='Y', whose value you should check in PR. This is to ensure, we don't execute super.ProcessRequest() again.

PR()
{
if (Temp == null) {
super.processRequest();
}
}

This will ensure that your page does not get re initialize when YES button is clicked.

Next, in your ProcessFormRequest(), you should only call super.ProcessFormRequest() once within the click of "YES" button.

In your above code it is present at 2 places.

I would suggest, put debug messages and see what all is executing in which order.