ZAF call to hide and show option values is slow and blocks browser completely
We have an app which controls which option values in a drop down field are visible based on rules. In some cases, our customers have a large number of option values in a field and they wish to hide all bar a few of them (4500 option values and hide 4480 of them).
We call ZAF.invoke providing a JSON object with details of all the option values we wish to hide. This used to perform ok (maybe 6 months ago). It was never instant but the time taken to hide 4000+ option values was sub 1 second. Nowadays, our customer is complaining about Zendesk being unresponsive since the hide is now taking anything from 8 - 12 seconds and during that time, the browser is completely unresponsive. You cannot scroll, type into a comment, select a drop down or anything.
Can anything be done to either speed up the performance of hiding (or showing) many option values, or at least implement it in such a way that it does not hog the browser thread for an extended period of time.
We have implemented a simple test app. You nominate a drop down field that has lots of option values and then click a button to hide them all using the ZAF. When you click the button you can do nothing with the browser until it has finished.
-
I had the same issue with another provider and "workspace rules" - I mean that's a lot of fields you're hiding, but as you say it was working.
We had nowhere near as many fields but same issue, and we had to get the cache specifically for that function / field increased by the software provider. Not sure that's gonna work for you here as the fields are all distinct by the sounds of it - we were hiding multiple values (hundreds) on a menu field on page load dependent on rules..... but maybe they've dropped the cached amount as a way to increase general performance (what happened to us). I could just be talking rubbish :)
-
To clarify, I am not hiding lots of fields, but hiding lots of field values within a single field.
-
Hey Alan, thanks for reaching out and letting us know about the performance issue you're facing. I'll reach out to you for more details to see how we can improve this.
Please sign in to leave a comment.
3 Comments