Issue with Huge elist (6000-7000) nodes on the Web Contributor 8.4

[LCurve]

Hi All,

When i am trying to open the nodes with huge elist (which contains 6000-7000) from the Web Contributor on 8.4 its giving the following error message.

"A script on this page is causing internet explorer to run slowly. If it continues to run, your computer may become unresponsive".
Do you want to abort the script. Yes/No

But I'm able to open the same nodes from CAC Preview. Please advice

Thanks in advance,
Kumar.

[rbuhrt]

Which version of IE are you running? You are on 8.4 FP1 I assume?

[LCurve]

Hi,

Thanks for the reply.

Yes, we have installed FP1 and the IE version is 6.0.2900. Can you suggest any workaround for this issue.

[JaromirSeps]

Hello,

did this have some solution please?

I'm considering some simple application with 6000+ nodes and I am interested in any possible bugs.

Thank you
Jaromir

[Gunes]

Hello Kumar,

I assume by open 6000-7000 elist items, you mean to say that the page/area that is becoming unresponsive is the intial workflow page (the page with the tree view on the left and the workflow states on the right before you select an elist)?

Or are you trying to do something miraculous with the Multi-Node View functionality? - I am pretty sure you're not doing this as you'd get a different error for sure.

I believe either the tree view or the workflow state is controlled by Javascript (I can never remember which is which) and I think what it's trying to do is load 6000-7000 elist in that view everytime you load the initial page. As you can appreciate This'll take a bit of time if you have given that user, view/review access at the top level, and the review/view depth is set to all.

The CAC preview in the vrsion you are using - uses the classic client - not the rich java client.

This is an area which has been impacted in the rich client, and performs a lot better in the classic client (I won't go into the technicalities) so 1 radical workaround if you must view all of the elist items would be to revert to the classic client.

Something else that you might want to try is setting the workflow refresh rate in the Admin console; within the development section of an application, under Web settings or something along those lines - there is a workflow refresh rate, which I believe is set to 1 (minute) by default - up this to 10 (for testing purposes) and you will hopefully find that the script that is becoming unresponsive will come back within the 10minute timeframe BEFORE another call is made. Alternatively, if you don't care about the workflow states refreshing, then you can set this value to 0.

3rd option is to re-think your review/view depths, and who you give review-edit access to & such like.

Hope this helps,