Actions

Old mapping

From LimeSurvey Manual

Revision as of 18:32, 31 July 2018 by Cdorin (talk | contribs) (Created page with "=Mapping of LimeSurvey 1.91+ to Expression Manager Functionality= <!--T:194--> <!--T:195--> {| class="wikitable" !Old Feature!!New Feature!!Comments |- |Conditions||Relevanc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Mapping of LimeSurvey 1.91+ to Expression Manager Functionality

Old Feature New Feature Comments
Conditions Relevance You can use very complex conditional equations, and access a broader range of variables
Assessments Equation Any assessment scores can be re-structured into an Equation. This both ensures that the score is written to the database, and also lets you see dynamic changes to the score value on the current page
Replacements Expression Manager The core engine takes the input string and treats everything within curly braces as an Expression - so it handles all historical replacements types.  To avoid messing up embedded JavaScript, Expression Manager only processes content between curly braces as long as (a)  there is no leading or trailing whitespace within the curly braces - e.g. {expr} is an expression, but { expr}, {expr }, and { expr } are not expressions.  Furthermore, Expression Manager does not process content within its own strings (e.g. {list('hi','there {braces}')} generates "hi there {braces}").  It also ignores escaped curly braces (e.g. \{this is not an expression\})
Validation Expression Manager The plan is to take the current min/max Question Attributes and have Expression Manager process them.  That way the min/max values can be expressions themselves