Number of Questions in a Questionnaire
There isn't a limit per-say Rajesh, but the number of questions on a give screen will be a potential performance hit in the browser and if there any dde's to hide/show questions/section will also suffer a performance hit.
A workaround is that you can group questions into tabs which will help reduce the load on the browser.
No that I know of Rajesh. The performance is also based on specs of the client machine, configuration of the web and database servers along with the network connection.
You can contact support and see if they have some recommendations.
I've tested out to 2500 and notice a pretty good performance hit. The real question is the user experience and how many questions do you want to force them to answer.
The plan is to use events to display certain questions. Questions will be "scoped" and displayed when user selects an option/scope as soon as he starts.
Here is an example:
Do you wish to see Questions belong to X domain? If Yes (display these 250 questions below)
Do you wish to see Questions belong to Y domain? If Yes (display these 25 questions below)
Do you wish to see Questions belong to Z domain? If Yes (display these 75 questions below)
There is a possibility that the user selects Yes to X domain and/or Y domain and/or Z domain.
When you say "performance hit", what do you mean?
1) How long would it take to load the questions?
2) If Findings are generated on the Questionnaire, how long would it take the generate the findings?
3) I assume any reporting on the questionnaire would also take a hit. True?
Performance hit that I was referring to is related to the time required to render the questions and load the questionnaire. With DDE's and hide all rules you could eliminate some of that and incorporate tab sets. The time required is depending on the environment but took an extra 20 seconds or so to load a raw 2500 feed. The largest findings generation I have done was on 900 questions and it took less than 5 minutes to run. The reporting performance will depend on the fields your pulling, and the amount of iViews rendering so you may or may not notice a performance hit there. Hope that answers your question, will be happy to assist further if you need additional information.