I have hit an issue that is causing a list and search page to load really slowly (~15 seconds+). I have a number of buttons of the Submit type in the modal position of the search form view. I noticed the issue was being caused by the Task in the buttons being set as Process (Ajax). The more buttons on the form with this Task, the longer the page takes to load. When I change the Task to just Process it fixes the issue.
My question is, what is the difference between Process and Process (Ajax), and why might this be impacting page load time?
Just looking into this a bit further, and when the Process (Ajax) task is set for the button it is loading the ids of all the results of the search into an items array in a JavaScript function on the page, hence why page load time is increasing. When having the Process task set it doesn't have this overhead.
This seems to be the code in question
Any thoughts on this? Does Process (Ajax) just not reload the page when executing the process script?
I received the following information direct from Octopoos:
The main purpose of "Process (Ajax)" is to allow to process hundreds/thousands of items without timeout or memory issue. It will trigger many AJAX calls where n items will be processed (SEBLOD Toolbox > Options > Process > Items per AJAX request) and reload the page only after processing the last call.
