Siebel Business Process Framework: Task UI Guide > Testing and Troubleshooting a Task UI > Troubleshooting a Task UI >

Record Context Is Lost

While navigating between views, if the record context is lost even though there is no Query operation, then make sure the following items are true:

• The search specifications across views are consistent
• The search specifications for the view step match

Inconsistent Search Specifications Across Views

If both of the following situations exist, then there is a forced repeat execution:

• If the first view includes an applet or a view search specification and the second view does not
• If Retain Applet Search Spec or Retain View Search Spec is set to FALSE

This situation causes a loss of record context because the second view is supposed to display data of the business component without the constraint that is imposed by the search specification of the first view.

Consider your business logic. You might need to set the Retain Applet Search Spec or Retain View Search Spec properties to TRUE.

Guidelines for Defining a Search Specification

It is recommended that you set the constraint for a search specification on the business component or on the view step rather than on the applet. This way, the scope of the search specification is more clearly defined. Note the following situations:

• A search specification on a business component applies throughout the task UI
• A search specification on a view step applies only for the step on which it is defined
• A search specification on the view step applies until the next UI step is executed, depending on the value of the Retain View Search Spec property

Specialized Code That Starts Execution

If each of the following situations apply, then specialized code might start execution:

• Both steps contain an identical applet
• Both steps include identical step search specifications
• Retain Applet Search Spec is TRUE
• Retain View Search Spec is TRUE
• Repeat execution is occurring

You can perform the following work to debug this situation:

• Use logging with the ObjMgrSqlLog event set to 5 to inspect the search specification for each SQL statement.
• Review your log for the CSSSqlObj::InvalidateSQLCursor call.
• Determine if there are errors that are caused as a result of performing this call.