Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Task UI Guide > Testing, Troubleshooting, Deploying, and Administering a Task UI > Troubleshooting a Task UI > Record Context Is LostIf 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:
Inconsistent Search Specifications Across ViewsIf all of the following situations exist, then Siebel CRM repeats a search:
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 SpecificationTo 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:
Specialized Code That Starts a Task UI Might Cause a Loss of ContextIf any of the following situations apply, then specialized code might start a task UI and can cause a loss of record context:
To debug this situation, you can perform the following work: |
Siebel Business Process Framework: Task UI Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |