Problem:
- when a user opens "Batch Operation" View and
- there is a lot of history data in the database
- then Oracle utilize 100% CPU to execute the historic process instance queries
AT:
- there exists an option that the user can switch between "Filter" and "Search" mode
- "Filter": Initially, first page of historic process instances is shown
- "Search": Initially, no historic process instances are shown (so that, the historic process instance query is not executed)