Hi all,
I've seen this issue at three different orgs so I'm posting here in hopes that someone has found a solution.
There is a segment of patrons who really care about their salutation - what they see on the envelope or postcard they receive. Some people don't want to see a prefix at all. Some people don't want their spouse on the label. There are many other scenarios.
Delivering on some of these preferences can be tough because "Gen Sal" so easily overrides the field based on A1 and A2 values. I would love to see a little "padlock" symbol next to Gen Sal that you can toggle on an off, but it doesn't exist.
Has anyone a good way to manage these accounts? For people that don't want their spouse to appear, we keep the spouse as an Adult Member but remove A2 - so that scenario is OK. But for many others, we don't have a solution.
Thanks in advance,Megan
Seattle Symphony
That padlock next to the button sounds like such a great idea! Have you submitted an enhancement request?
Hi Nick
Back in the days of annual enhancement voting, we put something like that ( it might have been exactly that) up as an enhancement request several years in a row, but nobody else voted for it, so it never got up.
Now that we have Interceptors, it would probably be an easy one to make - set an attribute called NoGenSal on the constituent, and make an interceptor for salutation changes that reverted any changes for constituenti with that attribute.
¿Perhaps this would be a case where someone could make one, and then share it?
Although the padlock would still be better.
Ken
I continue to fail to understand why enhancement requests are not visible and votable year-round. This would hardly be a major project--and it makes sense that when organizations have a limited number of votes per cycle, that they will naturally assign those to topics with higher priority. Then things like this get artificially buried.
Nick, I wholeheartedly agree.
Ken, thanks for the interceptor idea. I'm not familiar with that technology but have sent to IT for input. Your description sounds very promising.
Megan
This still continues to be an issue for us. We want the padlock!
Me too. :)Megan
Unknown said: This still continues to be an issue for us. We want the padlock!
Just chiming in to join the chorus; a padlock, that the Tess client (and (especially?) TNEW) observes, would be great.
We have a custom Devo sal type, and that solves some things, but a padlock would be better yet. (We do no mass updates of salutations, FYI.)