In one of our Siebel IP17 upgrade project we had to set an option for the end users cancel currently long running queries. In Siebel 8.1x if user executes a query in the application UI then if the result is taking longer time then a popup window appeared asking and informing user to wait as query is taking longer execute time or Cancel the current operation. In the meanwhile user do not have the option/permission to click anywhere else on the screen while the current operation is in progress.
But in OpenUI (until IP17.5), in case of long running query a circle appears showing as system is busy but after certain amount of time it stop spinning and disappear and from here the user can click on other screens but as the current operation was not completed the next screen will not be loaded and system appears as stuck.
In case we set set CancelQueryTimeOut >=1 say 10 in the corresponding Object Manager and execute a long running query then a popup window starts appearing after 10 seconds but on clicking Cancel button it did not work and stays as below:
But in OpenUI (until IP17.5), in case of long running query a circle appears showing as system is busy but after certain amount of time it stop spinning and disappear and from here the user can click on other screens but as the current operation was not completed the next screen will not be loaded and system appears as stuck.
In case we set set CancelQueryTimeOut >=1 say 10 in the corresponding Object Manager and execute a long running query then a popup window starts appearing after 10 seconds but on clicking Cancel button it did not work and stays as below:
No comments:
Post a Comment