View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 10
IDProjectCategoryView StatusDate SubmittedLast Update
05372Bug reportsAssessmentspublic2011-08-02 14:182017-01-25 14:40
Reporterwabrit Assigned ToTMSWhite  
PrioritylowSeverityminor 
Status closedResolutionno change required 
Product Version1.91+ 
Target Version2.00a1 
Summary05372: {ASSESSMENT_CURRENT_TOTAL} always 0 unless at least one assessment rule defined
Description

If a survey is set into assessment mode, but there are no assessment rules, then the variable {ASSESSMENT_CURRENT_TOTAL} is always 0.

This is a problem if you want to create an assessment-based survey but don't want any rules to fire (e.g. you want to redirect to an endURL instead).

Steps To Reproduce
  1. Create a survey in assessment mode.
  2. Create at least one question Q1 with all answers having positive assessment scores (e.g. radio buttons).
  3. Create a question Q2 with script to load the answer from {ASSESSMENT_CURRENT_TOTAL} in a subsequent question group.
  4. Create one assessment rule.

If you run this survey then Q2 will present a non-zero value based on current assessment total.

If you delete the assessment rule and then rerun the survey Q2 will always present a 0 value.

Additional Information

Attached sample survey (currently contains no assessment rule)

TagsNo tags attached.
Attached Files
limesurvey_survey_94455.lss (20,020 bytes)
Bug heat10
Complete LimeSurvey version number (& build)10604
I will donate to the project if issue is resolvedNo
Browser Chrome/IE/Firefox
Database type & versionMS SQL Server 2008 R2
Server OS (if known)Windows 7
Webserver software & version (if known)Tomcat 6.0.32
PHP Version5.3.6

Users monitoring this issue

There are no users monitoring this issue.

Activities

wabrit

wabrit

2011-08-02 14:23

reporter   ~15928

Note that if you import the attached survey you will need to change the script associated with the question that displays the {ASSESSMENT_CURRENT_TOTAL} as the target SGQAID will have changed.
c_schmitz

c_schmitz

2011-08-02 17:32

administrator   ~15942

This is too much effort for a simple bugfix - Maybe we can schedule this for the assessment engine in 1.92.
wabrit

wabrit

2011-08-02 18:33

reporter   ~15943

Understood - the workaround in the meantime is I guess to add a "dummy" assessment rule to the survey; it will never be exercised if you specify endURL behaviour, but it's presence is enough to persuade limesurvey to maintain {ASSESSMENT_CURRENT_TOTAL}.
TMSWhite

TMSWhite

2012-01-20 15:41

reporter   ~16849

Since there is an easy work-around, re-classifying this a low priority.
TMSWhite

TMSWhite

2012-02-07 21:54

reporter   ~17293

What is the desired solution here? That {ASSESSMENT_CURRENT_TOTAL} will return '' instead of 0 if there are no assessment rules defined?
Mazi

Mazi

2012-02-09 09:51

updater   ~17314

To me this doesn't even look like a bug. Wabrit, what would be the alternative behavior you would expect?
wabrit

wabrit

2012-02-09 10:05

reporter   ~17317

The behaviour I would expect would be that {ASSESSMENT_CURRENT_TOTAL} would return the actual current total regardless of whether I had supplied any assessment rules or not.
TMSWhite

TMSWhite

2012-02-23 16:57

reporter   ~17592

This isn't really a bug. We just need to update the wiki to state that if the user wants to see an assessment value, then at least one assessment must be defined
webmasterlpo

webmasterlpo

2017-01-25 13:11

reporter   ~42833

Hello,

I've seen this bug report and now I've found why {ASSESSMENT_CURRENT_TOTAL} wasn't working for my survey (limesurvey 2.62.0 170124). With a dummy rule it works.

Can someone update the wiki here : https://manual.limesurvey.org/Assessments (the Tip& Tricks part) ?

Thanks in advance !
Mazi

Mazi

2017-01-25 14:12

updater   ~42834

@webmasterlpo, our manual is a wiki. Everyone can and should improve it if possible. You can log in using your bugtracker user account details.
webmasterlpo

webmasterlpo

2017-01-25 14:40

reporter   ~42835

Ok, done !

Issue History

Date Modified Username Field Change
2011-08-02 14:18 wabrit New Issue
2011-08-02 14:18 wabrit File Added: limesurvey_survey_94455.lss
2011-08-02 14:23 wabrit Note Added: 15928
2011-08-02 17:31 c_schmitz Assigned To => TMSWhite
2011-08-02 17:31 c_schmitz Status new => assigned
2011-08-02 17:31 c_schmitz Target Version => 2.00a1
2011-08-02 17:32 c_schmitz Note Added: 15942
2011-08-02 18:33 wabrit Note Added: 15943
2011-10-08 22:39 c_schmitz Status assigned => confirmed
2012-01-20 15:41 TMSWhite Note Added: 16849
2012-01-20 15:41 TMSWhite Priority normal => low
2012-01-20 15:41 TMSWhite Severity partial_block => minor
2012-02-07 21:54 TMSWhite Note Added: 17293
2012-02-09 09:51 Mazi Note Added: 17314
2012-02-09 10:05 wabrit Note Added: 17317
2012-02-23 16:57 TMSWhite Note Added: 17592
2012-02-23 16:57 TMSWhite Status confirmed => resolved
2012-02-23 16:57 TMSWhite Resolution open => no change required
2012-02-26 10:19 c_schmitz Status resolved => closed
2017-01-25 13:11 webmasterlpo Note Added: 42833
2017-01-25 14:12 Mazi Note Added: 42834
2017-01-25 14:40 webmasterlpo Note Added: 42835