...
Go to Conferences/Edit and edit your conference. Here you have the option to send feedback codes to all participants or to a single email (use this for testing).
When using 'mail all participants'
...
who receives the feedback invitation?
It is left to the developer to add the list of participants to CORE. In application/modules/core/models/Feedback.php::getParticipants you have to provide the $participants array. Use the same format as the debug example. Here is an example of how CORE hooks into the TERENA registration system:
...
Every participant gets an email with a link containing a UUID. The link initializes initialises their feedback session during which the UUID value is mapped to a feedback_id. This id is used for authentication. Only users with a valid and existing UUID code can provide feedback.
See: Core_Model_Feedback::_init()
...
- Every feedback section has its own database table in the feedback schema.
- Every feedback section has its own web form , located here:
application/modules/core/forms/Feedback/
If you want to modify the sections or questions, you have to change the respective database table and the respective feedback form. The feedback controller takes care of saving saves the feedback values. So if you modify a form or a database table, this should not break your functionality.
...
All the feedback results are stored in the CORE database , in the feedback schema.