You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

482 lines
17 KiB

[FIX] privacy_consent: Separate automated emails send process Before https://github.com/OCA/data-protection/pull/29 there was a race condition where an email could be sent while the same transaction that created the `privacy.consent` record still wasn't committed, producing a 404 error if the user clicked on "Accept" or "Reject" before all mails were sent. To avoid that, a raw `cr.commit()` was issued, but this produced another situation where the user had to wait until the full email queue is cleared to get his page loaded. It wasn't an error, but a long queue meant several minutes waiting, and it's ulikely that an average human is so patient. So, here's the final fix (I hope!). The main problem was that I was looking in the wrong place to send the email. It turns out that the `self.post_message_with_template()` method is absolutely helpless in the case at hand, where these criteria must be met: * E-mail must be enqueued, no matter if there are less or more than 50 consents to send. * The template must be processed per record. * In an ideal world, a `cr.commit()` must be issued after each sent mail. The metod that was being used: * Didn't allow to use `auto_commit` mode. * Only allowed to render the template per record if called with `composition_mode="mass_mail"`. * Only allowed to enqueue emails if called with `composition_mode="mass_post"`. Obviously, I cannot set 2 different values for `composition_mode`, so a different strategy had to be used. I discovered that the `mail.template` model has a helpful method called `send_mail()` that, by default: * Renders the template per record * Enqueues the email * The email queue is cleared in `auto_commit=True` mode. So, from now on, problems are gone: * The user click, or the cron run, will just generate the missing `privacy.consent` records and enqueue mails for them. * The mail queue manager will send them later, in `auto_commit` mode. * After sending the e-mail, this module will set the `privacy.consent` record as `sent`. * Thanks to *not* sending the email, the process the user faces when he hits the "generate" button is faster. * Instructions in the README and text in the "generate" button are updated to reflect this new behavior. * Thanks to the `auto_commit` feature, if Odoo is rebooted in the middle of a mail queue clearance, the records that were sent remain properly marked as sent, and the missing mails will be sent after the next boot. * No hardcoded commits. * No locked transactions. * BTW I discovered that 2 different emails were created when creating a new consent. I started using `mail_create_nolog=True` to avoid that problem and only log a single creation message. Note to self: never use again `post_message_with_template()`.
6 years ago
[FIX] privacy_consent: Separate automated emails send process Before https://github.com/OCA/data-protection/pull/29 there was a race condition where an email could be sent while the same transaction that created the `privacy.consent` record still wasn't committed, producing a 404 error if the user clicked on "Accept" or "Reject" before all mails were sent. To avoid that, a raw `cr.commit()` was issued, but this produced another situation where the user had to wait until the full email queue is cleared to get his page loaded. It wasn't an error, but a long queue meant several minutes waiting, and it's ulikely that an average human is so patient. So, here's the final fix (I hope!). The main problem was that I was looking in the wrong place to send the email. It turns out that the `self.post_message_with_template()` method is absolutely helpless in the case at hand, where these criteria must be met: * E-mail must be enqueued, no matter if there are less or more than 50 consents to send. * The template must be processed per record. * In an ideal world, a `cr.commit()` must be issued after each sent mail. The metod that was being used: * Didn't allow to use `auto_commit` mode. * Only allowed to render the template per record if called with `composition_mode="mass_mail"`. * Only allowed to enqueue emails if called with `composition_mode="mass_post"`. Obviously, I cannot set 2 different values for `composition_mode`, so a different strategy had to be used. I discovered that the `mail.template` model has a helpful method called `send_mail()` that, by default: * Renders the template per record * Enqueues the email * The email queue is cleared in `auto_commit=True` mode. So, from now on, problems are gone: * The user click, or the cron run, will just generate the missing `privacy.consent` records and enqueue mails for them. * The mail queue manager will send them later, in `auto_commit` mode. * After sending the e-mail, this module will set the `privacy.consent` record as `sent`. * Thanks to *not* sending the email, the process the user faces when he hits the "generate" button is faster. * Instructions in the README and text in the "generate" button are updated to reflect this new behavior. * Thanks to the `auto_commit` feature, if Odoo is rebooted in the middle of a mail queue clearance, the records that were sent remain properly marked as sent, and the missing mails will be sent after the next boot. * No hardcoded commits. * No locked transactions. * BTW I discovered that 2 different emails were created when creating a new consent. I started using `mail_create_nolog=True` to avoid that problem and only log a single creation message. Note to self: never use again `post_message_with_template()`.
6 years ago
[FIX] privacy_consent: Separate automated emails send process Before https://github.com/OCA/data-protection/pull/29 there was a race condition where an email could be sent while the same transaction that created the `privacy.consent` record still wasn't committed, producing a 404 error if the user clicked on "Accept" or "Reject" before all mails were sent. To avoid that, a raw `cr.commit()` was issued, but this produced another situation where the user had to wait until the full email queue is cleared to get his page loaded. It wasn't an error, but a long queue meant several minutes waiting, and it's ulikely that an average human is so patient. So, here's the final fix (I hope!). The main problem was that I was looking in the wrong place to send the email. It turns out that the `self.post_message_with_template()` method is absolutely helpless in the case at hand, where these criteria must be met: * E-mail must be enqueued, no matter if there are less or more than 50 consents to send. * The template must be processed per record. * In an ideal world, a `cr.commit()` must be issued after each sent mail. The metod that was being used: * Didn't allow to use `auto_commit` mode. * Only allowed to render the template per record if called with `composition_mode="mass_mail"`. * Only allowed to enqueue emails if called with `composition_mode="mass_post"`. Obviously, I cannot set 2 different values for `composition_mode`, so a different strategy had to be used. I discovered that the `mail.template` model has a helpful method called `send_mail()` that, by default: * Renders the template per record * Enqueues the email * The email queue is cleared in `auto_commit=True` mode. So, from now on, problems are gone: * The user click, or the cron run, will just generate the missing `privacy.consent` records and enqueue mails for them. * The mail queue manager will send them later, in `auto_commit` mode. * After sending the e-mail, this module will set the `privacy.consent` record as `sent`. * Thanks to *not* sending the email, the process the user faces when he hits the "generate" button is faster. * Instructions in the README and text in the "generate" button are updated to reflect this new behavior. * Thanks to the `auto_commit` feature, if Odoo is rebooted in the middle of a mail queue clearance, the records that were sent remain properly marked as sent, and the missing mails will be sent after the next boot. * No hardcoded commits. * No locked transactions. * BTW I discovered that 2 different emails were created when creating a new consent. I started using `mail_create_nolog=True` to avoid that problem and only log a single creation message. Note to self: never use again `post_message_with_template()`.
6 years ago
  1. # Translation of Odoo Server.
  2. # This file contains the translation of the following modules:
  3. # * privacy_consent
  4. #
  5. msgid ""
  6. msgstr ""
  7. "Project-Id-Version: Odoo Server 10.0\n"
  8. "Report-Msgid-Bugs-To: \n"
  9. "Last-Translator: <>\n"
  10. "Language-Team: \n"
  11. "MIME-Version: 1.0\n"
  12. "Content-Type: text/plain; charset=UTF-8\n"
  13. "Content-Transfer-Encoding: \n"
  14. "Plural-Forms: \n"
  15. #. module: privacy_consent
  16. #: model:mail.template,body_html:privacy_consent.template_consent
  17. msgid "<?xml version=\"1.0\"?>\n"
  18. "<div style=\"background:#F3F5F6;color:#515166;padding:25px 0px;font-family:Arial,Helvetica,sans-serif;font-size:14px;\">\n"
  19. " <table style=\"width:600px;margin:5px auto;\">\n"
  20. " <tbody>\n"
  21. " <tr>\n"
  22. " <td>\n"
  23. " <a href=\"/\">\n"
  24. " <img src=\"/logo\" alt=\"${object.activity_id.controller_id.display_name|safe}\" style=\"vertical-align:baseline;max-width:100px;\"/>\n"
  25. " </a>\n"
  26. " </td>\n"
  27. " </tr>\n"
  28. " </tbody>\n"
  29. " </table>\n"
  30. " <table style=\"width:600px;margin:0px auto;background:white;border:1px solid #e1e1e1;\">\n"
  31. " <tbody>\n"
  32. " <tr>\n"
  33. " <td colspan=\"2\" style=\"padding:15px 20px 0px 20px; font-size:16px;\">\n"
  34. " <p>\n"
  35. " Hello, ${object.partner_id.name|safe}\n"
  36. " </p>\n"
  37. " <p>\n"
  38. " We contacted you to ask you to give us your explicit consent to include your data in a data processing activity called\n"
  39. " <b>${object.activity_id.display_name|safe}</b>, property of\n"
  40. " <i>${object.activity_id.controller_id.display_name|safe}</i>\n"
  41. " </p>\n"
  42. " ${object.description or \"\"}\n"
  43. " <p>\n"
  44. " % if object.state == \"answered\":\n"
  45. " The last time you answered, you\n"
  46. " % elif object.state == \"sent\":\n"
  47. " If you do nothing, we will assume you have\n"
  48. " % endif\n"
  49. "\n"
  50. " % if object.accepted:\n"
  51. " <b>accepted</b>\n"
  52. " % else:\n"
  53. " <b>rejected</b>\n"
  54. " % endif\n"
  55. " such data processing.\n"
  56. " </p>\n"
  57. " <p>\n"
  58. " You can update your preferences below:\n"
  59. " </p>\n"
  60. " </td>\n"
  61. " </tr>\n"
  62. " <tr>\n"
  63. " <td style=\"padding:15px 20px 0px 20px; font-size:16px; text-align:right;\">\n"
  64. " <a href=\"/privacy/consent/accept/\" style=\"background-color: #449d44; padding: 12px; font-weight: 12px; text-decoration: none; color: #fff; border-radius: 5px; font-size:16px;\">\n"
  65. " Accept\n"
  66. " </a>\n"
  67. " </td>\n"
  68. " <td style=\"padding:15px 20px 0px 20px; font-size:16px; text-align:left;\">\n"
  69. " <a href=\"/privacy/consent/reject/\" style=\"background-color: #d9534f; padding: 12px; font-weight: 12px; text-decoration: none; color: #fff; border-radius: 5px; font-size:16px;\">\n"
  70. " Reject\n"
  71. " </a>\n"
  72. " </td>\n"
  73. " </tr>\n"
  74. " <tr>\n"
  75. " <td colspan=\"2\" style=\"padding:15px 20px 15px 20px; font-size:16px;\">\n"
  76. " <p>\n"
  77. " If you need further information, please respond to this email and we will attend your request as soon as possible.\n"
  78. " </p>\n"
  79. " <p>\n"
  80. " Thank you!\n"
  81. " </p>\n"
  82. " </td>\n"
  83. " </tr>\n"
  84. " </tbody>\n"
  85. " </table>\n"
  86. " <table style=\"width:600px;margin:0px auto;text-align:center;\">\n"
  87. " <tbody>\n"
  88. " <tr>\n"
  89. " <td style=\"padding-top:10px;font-size: 12px;\">\n"
  90. " <p>\n"
  91. " Sent by\n"
  92. " <a href=\"/\" style=\"color:#717188;\">${object.activity_id.controller_id.display_name|safe}</a>.\n"
  93. " </p>\n"
  94. " </td>\n"
  95. " </tr>\n"
  96. " </tbody>\n"
  97. " </table>\n"
  98. " </div>\n"
  99. " "
  100. msgstr ""
  101. #. module: privacy_consent
  102. #: model:mail.message.subtype,name:privacy_consent.mt_activity_acceptance_changed
  103. msgid "Acceptance Changed"
  104. msgstr ""
  105. #. module: privacy_consent
  106. #: model:mail.message.subtype,name:privacy_consent.mt_consent_acceptance_changed
  107. msgid "Acceptance Changed by Subject"
  108. msgstr ""
  109. #. module: privacy_consent
  110. #: model:mail.message.subtype,description:privacy_consent.mt_consent_acceptance_changed
  111. msgid "Acceptance status updated by subject"
  112. msgstr ""
  113. #. module: privacy_consent
  114. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_accepted
  115. #: model:ir.ui.view,arch_db:privacy_consent.consent_search
  116. msgid "Accepted"
  117. msgstr ""
  118. #. module: privacy_consent
  119. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_default_consent
  120. msgid "Accepted by default"
  121. msgstr ""
  122. #. module: privacy_consent
  123. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_active
  124. msgid "Active"
  125. msgstr ""
  126. #. module: privacy_consent
  127. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_activity_id
  128. #: model:ir.ui.view,arch_db:privacy_consent.consent_search
  129. msgid "Activity"
  130. msgstr ""
  131. #. module: privacy_consent
  132. #: selection:privacy.consent,state:0
  133. msgid "Answered"
  134. msgstr ""
  135. #. module: privacy_consent
  136. #: model:ir.ui.view,arch_db:privacy_consent.consent_search
  137. msgid "Archived"
  138. msgstr ""
  139. #. module: privacy_consent
  140. #: model:ir.ui.view,arch_db:privacy_consent.consent_form
  141. msgid "Ask for consent"
  142. msgstr ""
  143. #. module: privacy_consent
  144. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_required
  145. msgid "Ask subjects for consent"
  146. msgstr ""
  147. #. module: privacy_consent
  148. #: selection:privacy.activity,consent_required:0
  149. msgid "Automatically"
  150. msgstr ""
  151. #. module: privacy_consent
  152. #: selection:privacy.consent,state:0
  153. msgid "Awaiting response"
  154. msgstr ""
  155. #. module: privacy_consent
  156. #: model:ir.ui.view,arch_db:privacy_consent.activity_form
  157. msgid "Consent"
  158. msgstr ""
  159. #. module: privacy_consent
  160. #: model:ir.model,name:privacy_consent.model_privacy_consent
  161. msgid "Consent of data processing"
  162. msgstr ""
  163. #. module: privacy_consent
  164. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_template_default_body_html
  165. msgid "Consent template default body html"
  166. msgstr ""
  167. #. module: privacy_consent
  168. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_template_default_subject
  169. msgid "Consent template default subject"
  170. msgstr ""
  171. #. module: privacy_consent
  172. #: model:ir.actions.act_window,name:privacy_consent.consent_action
  173. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_count
  174. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_ids
  175. #: model:ir.model.fields,field_description:privacy_consent.field_res_partner_privacy_consent_count
  176. #: model:ir.model.fields,field_description:privacy_consent.field_res_users_privacy_consent_count
  177. #: model:ir.ui.menu,name:privacy_consent.menu_privacy_consent
  178. msgid "Consents"
  179. msgstr ""
  180. #. module: privacy_consent
  181. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_create_uid
  182. msgid "Created by"
  183. msgstr ""
  184. #. module: privacy_consent
  185. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_create_date
  186. msgid "Created on"
  187. msgstr ""
  188. #. module: privacy_consent
  189. #: model:ir.model,name:privacy_consent.model_privacy_activity
  190. msgid "Data processing activities"
  191. msgstr ""
  192. #. module: privacy_consent
  193. #: model:mail.template,subject:privacy_consent.template_consent
  194. msgid "Data processing consent request for ${object.activity_id.display_name|safe}"
  195. msgstr ""
  196. #. module: privacy_consent
  197. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_display_name
  198. msgid "Display Name"
  199. msgstr ""
  200. #. module: privacy_consent
  201. #: selection:privacy.consent,state:0
  202. msgid "Draft"
  203. msgstr ""
  204. #. module: privacy_consent
  205. #: sql_constraint:privacy.consent:0
  206. msgid "Duplicated partner in this data processing activity"
  207. msgstr ""
  208. #. module: privacy_consent
  209. #: model:ir.model,name:privacy_consent.model_mail_template
  210. msgid "Email Templates"
  211. msgstr ""
  212. #. module: privacy_consent
  213. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_consent_template_id
  214. msgid "Email template"
  215. msgstr ""
  216. #. module: privacy_consent
  217. #: model:ir.model.fields,help:privacy_consent.field_privacy_activity_consent_template_id
  218. msgid "Email to be sent to subjects to ask for consent. A good template should include details about the current consent request status, how to change it, and where to get more information."
  219. msgstr ""
  220. #. module: privacy_consent
  221. #: model:ir.model.fields,help:privacy_consent.field_privacy_activity_consent_required
  222. msgid "Enable if you need to track any kind of consent from the affected subjects"
  223. msgstr ""
  224. #. module: privacy_consent
  225. #: model:ir.ui.view,arch_db:privacy_consent.activity_form
  226. msgid "Generate and enqueue missing consent requests"
  227. msgstr ""
  228. #. module: privacy_consent
  229. #: model:ir.ui.view,arch_db:privacy_consent.activity_form
  230. msgid "Generate missing draft consent requests"
  231. msgstr ""
  232. #. module: privacy_consent
  233. #: code:addons/privacy_consent/models/privacy_activity.py:139
  234. #, python-format
  235. msgid "Generated consents"
  236. msgstr ""
  237. #. module: privacy_consent
  238. #: model:ir.ui.view,arch_db:privacy_consent.consent_search
  239. msgid "Group By"
  240. msgstr ""
  241. #. module: privacy_consent
  242. #: model:ir.ui.view,arch_db:privacy_consent.form
  243. msgid "Hello,"
  244. msgstr ""
  245. #. module: privacy_consent
  246. #: model:ir.ui.view,arch_db:privacy_consent.form
  247. msgid "I <b>accept</b> this processing of my data"
  248. msgstr ""
  249. #. module: privacy_consent
  250. #: model:ir.ui.view,arch_db:privacy_consent.form
  251. msgid "I <b>reject</b> this processing of my data"
  252. msgstr ""
  253. #. module: privacy_consent
  254. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_id
  255. msgid "ID"
  256. msgstr ""
  257. #. module: privacy_consent
  258. #: model:ir.ui.view,arch_db:privacy_consent.form
  259. msgid "If it was a mistake, you can undo it here:"
  260. msgstr ""
  261. #. module: privacy_consent
  262. #: model:ir.model.fields,help:privacy_consent.field_privacy_consent_accepted
  263. msgid "Indicates current acceptance status, which can come from subject's last answer, or from the default specified in the related data processing activity."
  264. msgstr ""
  265. #. module: privacy_consent
  266. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent___last_update
  267. msgid "Last Modified on"
  268. msgstr ""
  269. #. module: privacy_consent
  270. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_write_uid
  271. msgid "Last Updated by"
  272. msgstr ""
  273. #. module: privacy_consent
  274. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_write_date
  275. msgid "Last Updated on"
  276. msgstr ""
  277. #. module: privacy_consent
  278. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_last_metadata
  279. msgid "Last metadata"
  280. msgstr ""
  281. #. module: privacy_consent
  282. #: selection:privacy.activity,consent_required:0
  283. msgid "Manually"
  284. msgstr ""
  285. #. module: privacy_consent
  286. #: model:ir.model.fields,help:privacy_consent.field_privacy_consent_last_metadata
  287. msgid "Metadata from the last acceptance or rejection by the subject"
  288. msgstr ""
  289. #. module: privacy_consent
  290. #: code:addons/privacy_consent/models/mail_template.py:25
  291. #, python-format
  292. msgid "Missing privacy consent link placeholders. You need at least these two links:\n"
  293. "<a href=\"%s\">Accept</a>\n"
  294. "<a href=\"%s\">Reject</a>"
  295. msgstr ""
  296. #. module: privacy_consent
  297. #: model:mail.message.subtype,name:privacy_consent.mt_activity_consent_new
  298. #: model:mail.message.subtype,name:privacy_consent.mt_consent_consent_new
  299. msgid "New Consent"
  300. msgstr ""
  301. #. module: privacy_consent
  302. #: model:ir.model,name:privacy_consent.model_mail_mail
  303. msgid "Outgoing Mails"
  304. msgstr ""
  305. #. module: privacy_consent
  306. #: model:ir.model,name:privacy_consent.model_res_partner
  307. msgid "Partner"
  308. msgstr ""
  309. #. module: privacy_consent
  310. #: model:mail.message.subtype,description:privacy_consent.mt_activity_acceptance_changed
  311. msgid "Privacy consent request acceptance status changed"
  312. msgstr ""
  313. #. module: privacy_consent
  314. #: model:mail.message.subtype,description:privacy_consent.mt_activity_consent_new
  315. #: model:mail.message.subtype,description:privacy_consent.mt_consent_consent_new
  316. msgid "Privacy consent request created"
  317. msgstr ""
  318. #. module: privacy_consent
  319. #: model:mail.message.subtype,description:privacy_consent.mt_activity_state_changed
  320. #: model:mail.message.subtype,description:privacy_consent.mt_consent_state_changed
  321. msgid "Privacy consent request state changed"
  322. msgstr ""
  323. #. module: privacy_consent
  324. #: model:ir.model.fields,help:privacy_consent.field_res_partner_privacy_consent_count
  325. #: model:ir.model.fields,help:privacy_consent.field_res_users_privacy_consent_count
  326. msgid "Privacy consent requests amount"
  327. msgstr ""
  328. #. module: privacy_consent
  329. #: model:ir.model.fields,field_description:privacy_consent.field_res_partner_privacy_consent_ids
  330. #: model:ir.model.fields,field_description:privacy_consent.field_res_users_privacy_consent_ids
  331. msgid "Privacy consents"
  332. msgstr ""
  333. #. module: privacy_consent
  334. #: code:addons/privacy_consent/models/privacy_activity.py:100
  335. #, python-format
  336. msgid "Require consent is available only for subjects in current database."
  337. msgstr ""
  338. #. module: privacy_consent
  339. #: model:ir.model.fields,help:privacy_consent.field_privacy_activity_server_action_id
  340. msgid "Run this action when a new consent request is created or its acceptance status is updated."
  341. msgstr ""
  342. #. module: privacy_consent
  343. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_activity_server_action_id
  344. msgid "Server action"
  345. msgstr ""
  346. #. module: privacy_consent
  347. #: model:ir.model.fields,help:privacy_consent.field_privacy_activity_default_consent
  348. msgid "Should we assume the subject has accepted if we receive no response?"
  349. msgstr ""
  350. #. module: privacy_consent
  351. #: model:ir.ui.view,arch_db:privacy_consent.form
  352. msgid "Sincerely,<br/>"
  353. msgstr ""
  354. #. module: privacy_consent
  355. #: code:addons/privacy_consent/models/privacy_activity.py:92
  356. #, python-format
  357. msgid "Specify a mail template to ask automated consent."
  358. msgstr ""
  359. #. module: privacy_consent
  360. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_state
  361. #: model:ir.ui.view,arch_db:privacy_consent.consent_search
  362. msgid "State"
  363. msgstr ""
  364. #. module: privacy_consent
  365. #: model:mail.message.subtype,name:privacy_consent.mt_activity_state_changed
  366. #: model:mail.message.subtype,name:privacy_consent.mt_consent_state_changed
  367. msgid "State Changed"
  368. msgstr ""
  369. #. module: privacy_consent
  370. #: model:ir.model.fields,field_description:privacy_consent.field_privacy_consent_partner_id
  371. msgid "Subject"
  372. msgstr ""
  373. #. module: privacy_consent
  374. #: model:ir.model.fields,help:privacy_consent.field_privacy_consent_partner_id
  375. msgid "Subject asked for consent."
  376. msgstr ""
  377. #. module: privacy_consent
  378. #: model:ir.ui.view,arch_db:privacy_consent.form
  379. msgid "Thank you!"
  380. msgstr ""
  381. #. module: privacy_consent
  382. #: model:ir.ui.view,arch_db:privacy_consent.form
  383. msgid "Thanks for your response."
  384. msgstr ""
  385. #. module: privacy_consent
  386. #: model:ir.ui.view,arch_db:privacy_consent.activity_form
  387. msgid "This could enqueue many consent emails, are you sure to proceed?"
  388. msgstr ""
  389. #. module: privacy_consent
  390. #: model:ir.actions.server,name:privacy_consent.update_opt_out
  391. msgid "Update partner's opt out"
  392. msgstr ""
  393. #. module: privacy_consent
  394. #: model:ir.ui.view,arch_db:privacy_consent.form
  395. msgid "We asked you to authorize us to process your data in this data processing activity:"
  396. msgstr ""
  397. #. module: privacy_consent
  398. #: model:ir.ui.view,arch_db:privacy_consent.form
  399. msgid "We have recorded this action on your side."
  400. msgstr ""
  401. #. module: privacy_consent
  402. #: model:ir.ui.view,arch_db:privacy_consent.form
  403. msgid "You have <b class=\"text-danger\">rejected</b> such processing."
  404. msgstr ""
  405. #. module: privacy_consent
  406. #: model:ir.ui.view,arch_db:privacy_consent.form
  407. msgid "You have <b class=\"text-success\">accepted</b> such processing."
  408. msgstr ""