Search page displaying all records after create

Question

Hi,
I have created the search and the create page using the help of tutorial example. I have run into a 2 problems.
1. After I create the a transaction and click on apply button it directs me to the search page and diaplays all the records in the table. Instead I was looking to display only the record that I created in the create page.
I tried to change the parameter of the "pageContext.forwardImmediately" to "false" for retainAM, it is working fine, but at the same time it is not displaying the confirmation message that it ised to display.
2. Is there a spellchecker that I could add to my page for 3 columns that are of "CLOB" type. Any advise.
Thanks,
Ali

Answer 1

Hi Shiv,
I have added this in the processformrequest method. I do not know how and where to add it in the processrequest methos. Can you please guide me through it. I am pasting my CO file.
Thanks in advance for all your help.
Ali
package saf.oracle.apps.saf.jobperf.server.webui;
import oracle.apps.fnd.common.VersionInfo;
import oracle.apps.fnd.framework.webui.OAControllerImpl;
import oracle.apps.fnd.framework.webui.OAPageContext;
import oracle.apps.fnd.framework.webui.beans.OAWebBean;
import oracle.apps.fnd.framework.OAApplicationModule;
import oracle.apps.fnd.framework.webui.OADialogPage;
import oracle.apps.fnd.framework.webui.TransactionUnitHelper;
import oracle.jbo.domain.Number;
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.webui.OAWebBeanConstants;
import com.sun.java.util.collections.HashMap;
import oracle.bali.share.util.IntegerUtils;
* Controller for ...
public class ReviewCreateCO extends OAControllerImpl
public static final String RCS_ID="$Header$";
public static final boolean RCS_ID_RECORDED =
VersionInfo.recordClassVersion(RCS_ID, "%packagename%");
* Layout and page setup logic for a region.
* @param pageContext the current OA page context
* @param webBean the web bean corresponding to the region
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
// Always call this first
super.processRequest(pageContext, webBean);
// If isBackNavigationFired = false, we are here after a valid navigation
// (the user selected the Create Review button) and we should proceed
// normally and initialize a new Review.
if (!pageContext.isBackNavigationFired(false))
// We indicate that we are starting the create transaction(this
// is used to ensure correct Back button behavior).
TransactionUnitHelper.startTransactionUnit(pageContext,"jobperfCreateTxn");
// This test ensures that we don't try to create a new review if we
// had a JVM failover, or if a recycled application module is activated
// after passivation. If this things happen, BC4J will be able to find
// the row you created so the user can resume work.
if (!pageContext.isFormSubmission())
OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.invokeMethod("createReview",null);
// Initialize the ApplicationpropertiesVO for PPR.
// am.invokeMethod("init");
else
if (!TransactionUnitHelper.isTransactionUnitInProgress(pageContext,"jobperfCreateTxn", true))
// We got here through some use of the browser "Back" button, so we
// want to display a stale data error and disallow access to the page.
// if this were a real application, we would propably display a more
// context-specific message telling the user she can't use the browser
//"Back" button and the "Create" page. Instead, we wanted to illustrate
// how to display the Applications standard NAVIGATION ERROR message.
OADialogPage dialogPage = new OADialogPage(NAVIGATION_ERROR);
pageContext.redirectToDialogPage(dialogPage);
} // end processRequest()
* Procedure to handle form submissions for form elements in
* a region.
* @param pageContext the current OA page context
* @param webBean the web bean corresponding to the region
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
{    //super.processFormRequest(pageContext, 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("jobperfVO1");
// Note that we have to get this value from the VO because the EO will
// assemble it during its validation cycle.
// For performance reasons, we should generally be calling getEmployeeName()
// on the EmployeeFullVORowImpl object, but we don't want to do this
// on the client so we're illustrating the interface-appropriate call. If
// we implemented this code in the AM where it belongs, we would use the
// other approach.
String employeeName = (String)vo.getCurrentRow().getAttribute("FullName");
// We need to get a String so we can pass it to the MessageToken array below. Note
// that we are getting this value from the VO (we could also get it from.
// the Bean as shown in the Drilldwon to Details lab) because the item style is messageStyledText,
// so the value isn't put on the request like a messaqeTextInput value is.
String employeeNumber = (String)vo.getCurrentRow().getAttribute("EmployeeNumber");
//ma String employeeNum = String.valueOf(employeeNumber.intValue());
//ma Number employeeNumber = (Number)vo.getCurrentRow().getAttribute("EmployeeNumber");
//ma String employeeNum = String.valueOf(employeeNumber.intValue());
// Simply telling the transaction to commit will cause all the Entity Object validation
// to fire.
// Note: there's no reason for a developer to perform a rollback. This is handled by
// the framework if errors are encountered.
am.invokeMethod("apply");
// Indicate that the Create transaction is complete.
TransactionUnitHelper.endTransactionUnit(pageContext, "jobperfCreateTxn");
// Assuming the "commit" succeeds, navigate back to the "Search" page with
// the user's search criteria intact and display a "Confirmation" message
// at the top of the page.
MessageToken[] tokens = { new MessageToken("EMP_NAME", employeeName),
new MessageToken("EMP_NUMBER", employeeNumber) };
OAException confirmMessage = new OAException("PER", "LAC_FWK_TBX_T_EMP_CREATE_CONF", tokens,
OAException.CONFIRMATION, null);
// Per the UI guidelines, we want to add the confirmation message at the
// top of the search/results page and we want the old search criteria and
// results to display.
pageContext.putDialogMessage(confirmMessage);
HashMap params = new HashMap(1);
// Replace the current employeeNumber request parameter value with "X"
params.put("employeeNumber", "employeeNumber");
// IntegerUtils is a handy utility
params.put("employeeNumber",IntegerUtils.getInteger(5));
pageContext.forwardImmediately(
"OA.jsp?page=/saf/oracle/apps/saf/jobperf/webui/jobperfPG",
null,
OAWebBeanConstants.KEEP_MENU_CONTEXT,
null,
params, //null,
true, // retain AM
OAWebBeanConstants.ADD_BREAD_CRUMB_YES);
else if (pageContext.getParameter("Cancel") != null)
am.invokeMethod("rollbackReview");
// Indicate that the Create transaction is complete.
TransactionUnitHelper.endTransactionUnit(pageContext, "jobperfCreateTxn");
pageContext.forwardImmediately("OA.jsp?page=/saf/oracle/apps/saf/jobperf/webui/jobperfPG",
null,
OAWebBeanConstants.KEEP_MENU_CONTEXT,
null,
null,
false, // retain AM
OAWebBeanConstants.ADD_BREAD_CRUMB_NO);
} // end processFormRequest()
}