summaryrefslogtreecommitdiff
path: root/addons/survey/data/survey_data.xml
diff options
context:
space:
mode:
authorAurélien Warnon <awa@odoo.com>2019-02-06 09:29:37 +0000
committerAurélien Warnon <awa@odoo.com>2019-02-06 10:34:40 +0000
commitafb1abbb60e5cdc4f76ab7b5a1b54b5e8a9283d5 (patch)
tree351e5ef81e76689378b77739af1adfe0b1efcd02 /addons/survey/data/survey_data.xml
parentdba478332681dd21a39c4a183c002b1cf6e046d2 (diff)
[IMP] survey: scoring & certification
Task #1902306 Purpose ======= This commit adds certification capabilities to the survey module. A certification is a survey with the "certification" flag set to true than can be linked to a certification email template that contains a certification document (PDF). This template can be edited by the user in the technical settings to customize the certification email/document. To be able to implement this certification concept, we also have to add scoring mechanisms to surveys. survey.questions of type 'simple_choice' and 'multiple_choice' now have scores for the suggested answers. These question scores allow to compute a global score that is used to determine whether the user has successfully passed the certification or not. As additional features, we also have: - A time limit with an interface timer that limits the test to X minutes When reached, the survey is automatically submitted and unregistered (= unsubmitted) answers are not taken into account. - A limited number of attempts for the survey/certification If reached, the user can't take the survey/certification anymore The 'survey result' layout was adapted accordingly to show the success rate of participants and the correct answers to the survey questions. Specs ======= - Create a new survey : - Add a description field for the survey - Options on a survey : - Passing score : (sum of all good answers) in % - If No scoring => No passing score, no certificate - If Scoring with answers => Passing score and can see the answers (can create certificate) - If Scoring without answers => Passing score but can't review the answers at the end (can create certificate) - for the questions, if "no scoring" selected, can 't see the option "good answer" and "score" on the questions - If the 2 others options, can see the options "good answer" and "score" on the questions - all the types of questions are available for each option. - Questions - Add the option correct answer on the multiples questions (one or more good answers) - Certifications - If scoring, force "mandatory" for "mutliple choices (1or multiple answers)" - On the dashboard => visual information that this specific survey is a certification - Time Limit : The student is informed on the home screen of the survey of the time limit. The clock start when he clicks on "start survey" - Template of the certificate : send email with attachment PDF - Front-end : - Add some margin - Replace "Back to survey" with the blue-bar from the portal - Add a timer (start when the survey starts) - Add a progress bar (number of section and number of question inside the section) - Analyse of the results : - First a global graph with the number of people who''ve participated and passed the test - Stages of a survey : - Remove the stage "Permanent" - 3 stages : - draft : not on-line but can be tested (with phantom token) - In progress : on-line - closed : not on-line - Who can test a survey : the manager and the user. Add this condition to the phantom token.
Diffstat (limited to 'addons/survey/data/survey_data.xml')
-rw-r--r--addons/survey/data/survey_data.xml8
1 files changed, 1 insertions, 7 deletions
diff --git a/addons/survey/data/survey_data.xml b/addons/survey/data/survey_data.xml
index 87cefb946c9..a900d03ce8a 100644
--- a/addons/survey/data/survey_data.xml
+++ b/addons/survey/data/survey_data.xml
@@ -5,7 +5,7 @@
<record id="stage_draft" model="survey.stage">
<field name="name">Draft</field>
<field name="sequence" eval="1" />
- <field name="closed" eval="False" />
+ <field name="closed" eval="True" />
<field name="fold" eval="False" />
</record>
<record id="stage_in_progress" model="survey.stage">
@@ -20,11 +20,5 @@
<field name="closed" eval="True" />
<field name="fold" eval="True" />
</record>
- <record id="stage_permanent" model="survey.stage">
- <field name="name">Permanent</field>
- <field name="sequence" eval="4" />
- <field name="closed" eval="False" />
- <field name="fold" eval="True" />
- </record>
</data>
</odoo>