Dear Team,
kindly help as all the user task form taking more that 25 sec to 2 mins to load. Im sharing the screenshot. Thank for the help
A bigger question than how many fields are on the form is how many submissions have happened in the history of the instance. If you have a recurring workflow or task that has resulted in dozens or hundreds of submissions in the history of the instance, it can result in very slow loading of the tasks, as they need to review all of that submission history before the current status of the form is loaded.
I made a mistake early on in my use of LFForms and had a process that was doing an update to the form from status in a database (via Workflow) every 15 minutes. I quickly learned that once that form started to show more than a couple dozen submissions from the workflow re-running every 15 minutes, it started to get unbearably slow to load the tasks on screen.
Does your process have anything like that going on?
Dear Matthew,
Thanks for the information. Yes, I have the workflow set to re-run every 15 minutes. How did you resolve this issue? Currently, the cf_bp_workers_history table has about 7 million rows.
Thanks!
I wouldn't mess with the table directly, but you can probably clean up records by modifying the data retention rules on the process (Process Options > Data Maintenance) so that it clears out the data on completed instances sooner. That at least addresses older data from complete instances.
As far as addressing the problem going forward is concerned, I would recommend finding a better way to get what you need from workflow without having to push data back to forms so often. In my case, I was just waiting for a database change which could be minutes or days out, so instead of having a workflow that started and ended every 15 minutes to see if the update happened, I ended up putting the wait and repeat functionality onto Workflow. Forms starts and waits for the workflow, but the workflow runs a loop to keep checking the database every 15 minutes. The loop doesn't end until the database change has occurred, so it doesn't tell forms that the workflow has ended (and doesn't try to push any values back to forms) until the workflow identifies that the database change happened. Now forms only has a single call to and response from the workflow for each time it is wanting to wait for the database change. I have a bunch of long running workflows, but that is handled better by the system than a ton of submissions on the form from a bunch of workflow starts and stops.
Hopefully that all makes sense.