Survey Question Type Binary Result Mail
This module adds compatibility between the survey_question_type_binary and suervey_result_mail modules
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds file answers (single or multiple uploads) to the survey result email, so respondents receive their uploaded documents attached to the confirmation email.
This module is an automatic bridge between two survey extensions: one that lets surveys ask for file uploads, and one that emails the answers to the respondent. It changes nothing in the menus; it works behind the scenes when a survey is completed.
When a respondent finishes a survey, the module collects every uploaded file from the answers that were not skipped. If the survey is configured to send the result email and the respondent has an email address, those files are attached to the email. The email itself uses the survey's result email template, or a default one if none is set.
It also adjusts the answer summary shown in the email: file-upload questions are listed separately, showing the file names (for single uploads) or a bullet list of file names (for multiple uploads), while all other question types keep their normal formatting.
A small safeguard temporarily disables the 'send result mail' flag while the standard completion process runs, then re-enables it, so the email is sent only once with the attachments. The module touches survey.user_input and relies on the survey configuration fields send_result_mail and result_mail_template_id.
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/survey.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.