We have discovered if a user-initiated Chorus work object search is taking some time to return results, the user might again select the Search button resulting in further lookup request being initiated.
Because multiple long-running lookups can then eat up a lot of system resources it has resulted in wider performance/stability issues for other users, impacting the business and reputation of the system.
Although a spinning wheel is displayed the Search button control does not get disabled upon being selected, which would stop this issue from arising.
Please could this be considered for a future enhancement request? Many thanks.
(See INC1402966 for additional context.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.