Problem:
- when a user opens "Batch View" View and
- there is a lot of history data in the database
- then Oracle utilize 100% CPU to execute the historic batch query
AT:
- There exists a Cockpit config to enable or disable the automatic loading of the "Ended Batches" in "Batch view".
- If AutoLoad is enabled - It will load the "Ended Batches" automatically
- If AutoLoad is disabled - We will provide a button in "Batch view" page, clicking on which will load "Ended Batches".