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

Record Context Is Lost

If Siebel CRM loses the record context while the user navigates between views, even though no Query operation exists, then you must 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 all of the following situations exist, then Siebel CRM repeats a search:

• The first view includes an applet search specification or a view search specification, but the second view does not include either of these search specifications.
• The Retain Applet Search Spec property or the Retain View Search Spec property is set to FALSE.

The Retain Applet Search Spec property or the Retain View Search Spec property is set to FALSE, so Siebel CRM repeats the search, and then it loses the record context. The second view is supposed to display data from the business component without the constraint that the search specification of the first view imposes.

You must configure Siebel CRM to retain the search specification to avoid this situation. To do this, you set the Retain Applet Search Spec property or the Retain View Search Spec property to TRUE.

Guidelines for Defining a Search Specification

To more clearly define the scope of the 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. 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 where you define it.
• A search specification on a view step applies until Siebel CRM runs the next task UI step, depending on the value of the Retain View Search Spec property.

Specialized Code That Starts a Task UI Might Cause a Loss of Context

If any of the following situations apply, then specialized code might start a task UI and can cause a loss of record context:

• The steps include an identical applet.
• The steps include identical search specifications.
• The Retain Applet Search Spec property is TRUE.
• The Retain View Search Spec property is TRUE.
• Repeat runs of the task UI occur.

To debug this situation, you can perform the following work:

• Use logging with the ObjMgrSqlLog event set to 5 to inspect the search specification that Siebel CRM uses for each SQL statement.
• Review your log for the CSSSqlObj::InvalidateSQLCursor call.
• Determine if performing this call creates an error.