View Issue Details

This bug affects 1 person(s).
 0
IDProjectCategoryView StatusLast Update
07609Feature requestsConditionspublic2013-01-23 01:05
Reportercberghoff Assigned To 
PrioritynormalSeverityfeature 
Status acknowledgedResolutionopen 
Summary07609: We should be able to specify a page break at any point in the survey
Description

Groups are the primary method of organizing the display of large surveys (creating new page loads) as well as randomizing blocks of questions in survey batteries (e.g., stress scale, depression scale, cognitive test, etc. in one sitting). We (well, at least I) need a way of controlling presentation that is not directly linked to randomization.

The problem comes when one has A) a large number of questions that should be presented in order together but randomized as a group with other groups, or B) an array item with many subquestions in a similar randomization situation, and we don't want a user to scroll down the page. Multiple groups must be used to create new pages on the screen, which results in the loss of randomization ability without breaking up a component of the assessment.

Additional Information

A possible solution: Create a Page Break Item
I don't mind creating two array questions (Q1 & Q2) with 1/2 my subquestions in each, as long as I can keep these items logically connected. Place these questions together in a group, with an object placed between (js function?) that creates a new page for Q2, and randomize at the group level. It would work the same way with a set of individual multiple choice, text, or any other questions. All items that go together in a group, the Page Break item tells LS to present the previous questions on one page, then print the remaining questions on another till either another Page Break or the end of the group, then back to the group level randomization.

TagsNo tags attached.
Bug heat0
Story point estimate
Users affected %

Users monitoring this issue

There are no users monitoring this issue.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change