Siebel Business Process Framework: Task UI Guide > Debugging Tasks > Troubleshooting Common Problems >

Record Context Is Lost

While navigating between views, if your record context is lost even though there is no Query operation, verify the following:

  • The applet search specifications between the two views match.
  • The view step search specifications match.

If the first view has an applet or a view search spec, and the second one does not, and if Retain Applet Search Spec/Retain Step Search Spec is set to FALSE, there will be a forced re-execution; this causes loss of record context, because the second view is supposed to show the business component data without the constraints of the first view's search spec.

Consider your business logic. You may want to set the attributes Retain Applet Search Spec or Retain Step Search Spec to TRUE.

It is recommended that you set search spec constraints on the business component or on the view step, rather than on the applet. This way, the scope of the search spec is more clearly defined. Business component search specs apply throughout the task, and view step search specs apply for just the step (that is, until the next UI step, depending on the value of Retain Step Search Spec).

If both steps contain an identical applet, have identical step search specs, and Retain Applet Search Spec/Retain Step Search Spec is TRUE), and you are seeing re-execution, there may be specialized code that is triggering the execution. To debug, use logging with the ObjMgrSqlLog event set to 5 to inspect search specs for each SQL statement. Review your log for the CSSSqlObj::InvalidateSQLCursor call. Check to see if there are any errors triggering the execution of this call.

Siebel Business Process Framework: Task UI Guide Copyright © 2006, Oracle. All rights reserved.