Change Solicit Code Security to allow users to see Solicit Codes for Constituents even if they cannot assign/remove them

In the video which explains the new changes to Consent with patch 8 of Raisers Edge it says that you can increase the security around solicit codes as part of this update.

This would enable you to set that certain users can't manually delete or add solicit codes so that all solicit codes have to be linked to a Consent Line. I thought this was really beneficial as it would help to ensure consistency in the use of the Consent Lines.

However, I just set this up and if you untick 'Solicit Codes' on the security for a certain group of users it doesn't just mean they can't manually add or delete them, it also means they can't see them. It totally hides all solicit codes from this group of users. I can't understand why this would be beneficial as it's important that anyone using Raisers Edge knows the supporter's preferences and can quickly identify from their record how best they want to be contacted. 

I think this needs to be amended so that Solicit Codes can be seen but not manually edited - so they are only updated when a consent line is added.

  • Guest
  • Mar 2 2018
  • Shipped
Constituent record
  • Attach files
  • Van Ho commented
    August 27, 2020 13:03

    This is rather annoying and a massive oversight, how can you add in the ability to lock solicit but not let users see it in the solicit box....... You cannot run queries to output this each time you update a record to check its been updated. Rather annoying!

    ×

    Attachments Open full size

  • Sosheila Ernestine commented
    August 09, 2018 09:34

    the issue we have is that people may be able to see the solicit codes in the constituent but cannot Query them? Please can you advise....

    ×

    Attachments Open full size

  • Jarod Bonino commented
    March 02, 2018 17:18

    I'll reply to each of those on the respective ideas so as not to create a confusing paper trail for others that share your questions! Thanks for raising these. 

    ×

    Attachments Open full size

  • Guest commented
    March 02, 2018 17:02

    Hi Jarod, 

    That's great to hear! I've been chatting to the Raisers Edge support today and they actually suggested I post this on here but very happy to hear it's going to get fixed. 

     

    I also have two other issues with the Consent add on, wondering if you could help? I've put them on this community but it would be good to know if they're already in process of being resolved?

     

    1. There isn’t the option for the Consent and Privacy statements to autofill by the ‘Source’. So we just won’t use this function as it would be too time consuming to copy and paste each time when we could just refer to our Data Protection log for the wording used at that time.
     
    Vote here - https://renxt.ideas.aha.io/ideas/RENXT-I-1282
     
    2. The source isn’t a required field – so it could be missed. But it is mandatory that we record how the consent was gained - especially so we know if the supporter saw a privacy statement at the time. eg. Oral, written, form
     
    Vote here - https://renxt.ideas.aha.io/ideas/RENXT-I-1281
    ×

    Attachments Open full size

  • Jarod Bonino commented
    March 02, 2018 16:54

    Hey Sally! Sorry about the confusion. This was actually a bug that we will be resolving with the late March patch of RE (which will actually be Patch 10). I completely agree with you that hiding the solicit codes renders this security option useless. The intent was to control how solicit codes are added (through Consent opt-ins/opt-outs) but to allow solicit codes to still be respected. They obviously can't be respected though by users that cannot see them. Sorry about the confusion but rest assured that we're on it and will be addressing it ASAP!

    ×

    Attachments Open full size

Related ideas