Changes between Version 17 and Version 18 of S3/ConsentTracking

Timestamp:

06/12/19 08:13:09 (6 years ago)

Author:

Dominic König

Comment:

--

S3/ConsentTracking

@@ -70 +70 @@
 === Post-processing the Widget ===
 
-After successful form submission, the consent response must be post-processed in order to get recorded. 
-
-This post-processing requires a {{{person_id}}} for the person in question, so the post-processing can only happen after the person record has been established.
+After successful form submission, the consent response must be post-processed in order to get recorded. For this, a {{{person_id}}} for the person in question is required, so the post-processing can only happen after the person record has been established.
 
 To post-process the response, simply pass it to {{{auth_Consent.track}}} (a class method, instance not required):
@@ -78 +76 @@
 auth_Consent.track(person_id, form.vars.consent_question)
 }}}
+
+This will record the new response, and expire previous consent records of that person for the same processing types.
 == Checking for Consent ==