The student replies to the questionnaire by mail and the response data is retrieved and displayed in aggregated form in a Moodle course interface dedicated to examining the responses.
It must present questions with the same answer choices. This is so that the responses coming back by mail into Moodle can be capitalised on consistently. the concrete use case is typically a training evaluation questionnaire.
Example of typical questions with yes/no answers:
This link triggers a test of the cold questionnaire indicated in the block configuration, within 5 minutes without waiting for the CRON to run. Example:
Use of this block can hardly be generalised structurally across all courses and for all users. The pre-scheduled ad hoc task table could grow too significantly and pose a computation time problem for Moodle's cron process (examining several thousand tasks at each run). This architecture is therefore better suited to moderate and occasional use of notifications for a particular training programme.
===In progress === :
: to be completed/modified
The backoffice interface for scheduling events must allow the author to switch to any course context in which they have edit rights (capability tied to the ability to notify) and thereby change the current navigation context. The return to the course (button at the bottom of the interface) will take this current context into account to return to the corresponding course.
The block must allow building a message bank shared in the site, and easily reusable in new courses, by copy, so as to keep the possibility of local customisation.
Inspection tools (list of pending future tasks) could usefully ease the fine-tuning work of the configuration by the course designer.
Two trigger conditions for sending the questionnaire by mail to learners enrolled in the course:
the waiting period before sending the questionnaire must be chosen in the block config: 1d, 3d, one week, one month.