Open UI Client Executing a Query with the ENTER Key, not the Go / Execute Query button on a List Applet with a Form Applet Web Template for Query Mode, Causes a Hang After Query is Executed, Unable to Change the Current Record, Browser Refresh Fixes Hang.
(Doc ID 2091758.1)
Last updated on APRIL 30, 2018
Applies to:Siebel CRM - Version 188.8.131.52.17 [IP2013] and later
Information in this document applies to any platform.
The View has an applet that has a list applet for EditList mode and a Form applet web template for Query mode. This configuration has existed in the High Interactivity application for a long time. This configuration is used to prevent the users from querying on fields that will cause the query to be slow. The applet in Query Mode exposes only a few fields in query mode. Testing this view with the Siebel Open UI client, found an incorrect behavior that causes the applet to be "stuck" on the current record after a query is executed with the "ENTER" key. After the query is executed with ENTER, the queried records are displayed in the list applet, but the user is unable to navigate to the next record. If the user clicks on the Browser Refresh command, F5, then the problem behavior is fixed.
The incorrect behavior happens only with the Open UI client 184.108.40.206.17 IP2013.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!