Show only submitted answers, if the setting Scored Answers of Participant is enabled

1 Initial Problem

A test can be performed several times. The best test pass scores. Users should be able to view their answers after each test pass to learn why they failed the test. The Setting 'Scored Answers of Participant' in the Tab Settings > Scoring and Results is activated.

With the described configuration, users will always see all answer options of a question after finishing a test pass. So you will not only see the answers given, but all answer options with a note which option is correct and which is wrong. Users can transcribe the answer options and/or take screenshots and simply pass the test on the next run. Users should only be able to see their submitted answers after a failed test pass and prepare specifically for the questions that were not answered correctly for the next test pass. 

2 Conceptual Summary

For this reason, a new sub-setting for "Scored Answers of Participant" is to be introduced. The setting should be displayed as a radio button. By default, the setting "Show all answers" should be selected. 

If the radio button "Show only submitted answers" is activated, only the submitted answers will be displayed to users after the test is completed.

3 User Interface Modifications

3.1 List of Affected Views

• Test > Settings > Scoring and Results
• Test > Detailed Test Results > Answers

3.2 User Interface Details

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Zenzen, Enrico [ezenzen]
• Maintainer: Strassner, Denis [dstrassner]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.