GDPR, consent, and implementing double opt-in (DOI) in Sugar

RE: GDPR, consent, and implementing double opt-in (DOI) in Sugar

Jeroen Somhorst — Wed, 23 May 2018 14:55:43 GMT

Matt,

thanks for this in detail article. I tried to implement it localy but for some reason there is an issue with the code (or maybe my local instance). When I fill in a web to lead form the after save is (createConfirmOptInRecord) is called. For some reason the code can't find a primary e-mail adress. When I create a lead within sugar there is no issue at all and all seems to work fine.

RE: GDPR, consent, and implementing double opt-in (DOI) in Sugar

Martin Melmuk — Fri, 18 May 2018 12:06:17 GMT

Thank you Matt,

I have a question regarding the audit log.

Currently the behavior is such that If a contact or lead opens the confirmation url, the change will be registered in the audit log as if the assigned user has done the change.

To make it clear from where this action was taken, is there a possibility to tell the audit that the event source was from an entrypoint?

I have seen that an LogicHook can be a source, but a custom source would be nice.

RE: GDPR, consent, and implementing double opt-in (DOI) in Sugar

Mike Leatherwood — Wed, 25 Apr 2018 12:17:10 GMT

Matt,

This is a very detail, but right to the point article, and makes the point well. Good Job.

I will be attempting to do implement your suggestions, and I may reach out to you for a little assistance if it's ok?

Thanks, we all need to be on top of this before it runs us over.