Consent History (RE7.96 patch 10)

Mirijam Marx · June 2018

Hi All,

We have been collecting consent from our constituents through various inputs, and I would like to bring this all into RE now.

I am not sure if this has been asked before or if I am missing any documentation, or maybe I'm just not seeing the blindingly obvious. I am trying to ensure that the Solicit Code for the consent settings matches the most recent consent date, regardless of when a consent record was added to the database.

In a manual test, RE set the Solicit Code to match the latest added consent statement, even though it had an earlier consent date than the most current consent date. I.e. my test constituent is now set to have "opted in" to emails, even though a few days later constituent chose to opt out through Online Express, which was already recorded on the system before I added the "opt in" record (with an earlier consent date than the Online Express Opt Out). This is a scenario that could happen because we have different ways of collecting consent, and based on the incoming channel some consent updates happen in a more timely manner than others. I have only tried this manually, but I assume a similar thing would happen if I imported data.

Does anyone know if there is a way to enforce that the most recent consent date is used for setting the solicit code, rather than the date the consent record is added to RE?

I have attached a screenshot, the highlighted record is the one I added, the last one is the record that was already there with a more current consent date. The history is shown in the correct order, with the Opt Out through Online Express having the most current consent date, yet the Solicit Code is set to "Opt In" which matches the most recently added consent record with an earlier consent date.

Thank you!

Mirijam

Steven Cinquegrana 2 · June 2018

Hi Mirijam,

Are you self- or Blackbaud-hosted?

The reason I ask is that I think the only way you can manage this is by using some back-end/macro code to trigger off changes to Consent records and update the Solicit Code based on the dates associated with the Consent records (rather than the dates they were added).

To do this, you would need to not be Blackbaud-hosted AND to have the optional Macro/API module. (You could conceivably use a plug-in but you would have to run this manually as a post-process.)

Maybe, though, this is an oversight in implementing the Consent feature and it'll be corrected in a later release.

Otherwise, I don't think you're going to have any luck here.

Cheers,

Steve Cinquegrana | CEO and Principal Developer | Protégé Solutions

Mirijam Marx · June 2018

Steven Cinquegrana:

Hi Mirijam,

Are you self- or Blackbaud-hosted?

The reason I ask is that I think the only way you can manage this is by using some back-end/macro code to trigger off changes to Consent records and update the Solicit Code based on the dates associated with the Consent records (rather than the dates they were added).

To do this, you would need to not be Blackbaud-hosted AND to have the optional Macro/API module. (You could conceivably use a plug-in but you would have to run this manually as a post-process.)

Maybe, though, this is an oversight in implementing the Consent feature and it'll be corrected in a later release.

Otherwise, I don't think you're going to have any luck here.

Cheers,

Steve Cinquegrana | CEO and Principal Developer | Protégé Solutions

Hi Steve,

thank you for your response, very helpful - we are self-hosted, but I don't think we have the Macro/API module. I will look into setting up a post-process to hopefully capture these cases. It does seem odd to enforce setting a consent date, if it isn't actually relevant for the validity of the solicit code itself, so I will raise this with support and see what they come back with.

Thank you again,

All the best,

Mirijam

Consent History (RE7.96 patch 10)

Comments

Categories