Finding the system to perform very poorly when running searches on large datasets, particularly on screens such as the Task Planner.
Accredited this performance issue to the fact that the system attempts to run a search after every key that is entered into the search box.
It would be preferable if an actual search button was present so that only one search was executed when the entirety of the search had been entered. This should stop the semi-freezes the application experiences in-between character entries.
The functionality has been enhanced in Orchestrate version 7.77. Please upgrade to this version or above.