Author Topic: Is deceased and membership status (Read 3303 times)

speleo · February 01, 2008, 07:11:22 am

Hi, I just did a mailing and found that one of are members who had died was still listed as a current member. When the is deceased field is checked it would be good if the UpdateMembershipRecord process could kick in and set the status of any memberships to "expired". Should I raise an issue for this?

Dave Greenberg · February 02, 2008, 03:45:04 pm

Yes - sounds like the right thing to do (although I'm a bit concerned about what happens if someone is marked deceased by accident - and then the other action has to be undone).

Go ahead and file an issue (it will need to wait for 2.1 though) - and maybe think about including this related behavior relative to mailings / deceased state:
http://forum.civicrm.org/index.php/topic,2144.0.html

petednz · March 02, 2008, 01:00:59 pm

Hah - just hit this same issue - not with a mailing, but with exporting lists for local MembSecs to make use of.

In this case the person had Override Status = Expired - but that still doesn't avoid the situation of a MembSec running their eyes down the list to ring up people who are 'expired'.

I think the most desirable would be to have the 'Is Deceased' trigger a 'Deceased' status in the Membership records. And I am not sure what the problem is about undoing this if, as you suggest, the 'Is Deceased' is triggered by accident?

petednz · March 02, 2008, 01:09:49 pm

Hmm - and I note that Chris who is working on our project posted this http://forum.civicrm.org/index.php/topic,1549.0.html which suggests that if I were to temporarily set up a 'Deceased' membership status - I could not then search to find all deceased members so cannot allocate the status to them anyhow. Any tips?

Kurund Jalmi · March 02, 2008, 10:13:06 pm

There is an issue in jira regarding this, http://issues.civicrm.org/jira/browse/CRM-2613

kurund

petednz · March 03, 2008, 12:42:31 am

There is indeed

but it sets the rule to make the membership status 'expired' but i know from our workflows that we often have branch officers chasing the 'expired' people to rejoin - ie they get a list of all 'expired' people in their area, and ring them up.
That risks the deceaseed household being rung - hence my suggestion of having a 'deceased' membership type. Just a thought.

speleo · March 03, 2008, 04:53:06 am

you can create a membership type of lapsed which should cover this

Dave Greenberg · March 03, 2008, 11:02:10 am

Using a "reserved" Deceased status does seem preferable as it's a bit clearer than "Lapsed" or something more generic. We've modified the 2.1 issue for this:

http://issues.civicrm.org/jira/browse/CRM-2613

petednz · March 03, 2008, 11:28:46 am

Thanks Dave - I know you could drown in all these minor suggestions - I just keep spotting ways of reducing user errors - cheers

lcdweb · June 19, 2010, 12:08:33 pm

I think this needs to be revisited --
currently functionality only processes the status changes via the cronjob. I think it really needs to be triggered from the interface. At the point a contact is marked deceased, the membership status change and mail exclusion flags should be triggered.

Dave Greenberg · July 01, 2010, 04:10:08 pm

Agreed.
http://issues.civicrm.org/jira/browse/CRM-6433

CiviCRM Community Forums (archive)

News:

Author Topic: Is deceased and membership status (Read 3303 times)

speleo

Is deceased and membership status

Dave Greenberg

Re: Is deceased and membership status

petednz

Re: Is deceased and membership status

petednz

Re: Is deceased and membership status

Kurund Jalmi

Re: Is deceased and membership status

petednz

Re: Is deceased and membership status

speleo

Re: Is deceased and membership status

Dave Greenberg

Re: Is deceased and membership status

petednz

Re: Is deceased and membership status

lcdweb

Re: Is deceased and membership status

Dave Greenberg

Re: Is deceased and membership status