Author Topic: Scheduled Reminders should be activity (Read 663 times)

reperry · January 08, 2013, 12:33:58 pm

This keeps coming up for us, and wondering if others are on the same page.

We LOVE the scheduled reminders for events feature, but it's unfortunate that it leaves no trace when it goes off to do its work of reminding participants to attend the event.

It's impossible to tell via the user interface if the reminder actually went out (if our cron jobs scheduler gets out of whack, the reminder doesn't go out and we don't find out until a minute before the event when folks are frantically looking for the webinar log-in information). I've also gotten random event reminders and I can't tell why without being able to look at what was sent out and to whom.

We need to be able to check who received the reminder and it seems like this would fit right into the activity functionality. If an activity of activity type Scheduled Reminder Sent was triggered when the reminder is sent out, it would be easy to search and see who received the reminder and when. This would help to give event administrators more control, and help with cron job debugging.

I'm sure there are more good reasons to include this functionality. Would love to hear from others.

We're using 4.2.

Yashodha Chaku · January 09, 2013, 02:49:03 am

reperry :

There 's actually provision of storing the sent reminders as activities,

You might want to fire a simple SQL to set the record_activity column as 1 in civicrm_action_schedule table for the mapping that you want reminders to be logged as activities of Type 'Reminder Sent'.

We don't expose Record as Activity option through UI yet, though we can do it easily for 4.3

Hope that helps!
-Yashodha

Dave Greenberg · January 09, 2013, 10:20:49 am

Yash - based on this 'Wont Fix' issue, I'm not sure the code is in place to handle 'record_activity' flag:

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

Can you check and let us know. If this behavior has not been coded, can you get us an estimate of effort (noting that the code should ideally have logic to differentiate reminders where 'source_record_id" is either activity or memberships or event - which wasn't part of original spec since at that point reminders were only for activities).

reperry · January 09, 2013, 12:57:21 pm

Thanks for your responses. Curious to know what you find out, Yashi! Please keep us posted -- if there's a way to do this, we want to do it.

Yashodha Chaku · January 10, 2013, 02:59:44 am

Dave :

I checked and it works, its just a matter of exposing the 'record_activity' field to the UI.

'source_record_id' stores the corresponding membership id, participant id properly.

-Yashodha

reperry · January 10, 2013, 08:02:16 am

Thanks Yashi and Dave for helping us sort this out. I suspected that Reminder Sent activity had to be related

Dave Greenberg · January 10, 2013, 11:11:54 am

Issue filed to expose the checkbox for 4.3: http://issues.civicrm.org/jira/browse/CRM-11645

Yashodha Chaku · January 11, 2013, 06:43:58 am

For your reference, this has been fixed for 4.3

Here is the patch :
https://fisheye2.atlassian.com/changelog/CiviCRM?cs=44762
https://fisheye2.atlassian.com/changelog/CiviCRM?cs=44769

-Yashodha

CiviCRM Community Forums (archive)

News:

Author Topic: Scheduled Reminders should be activity (Read 663 times)

reperry

Scheduled Reminders should be activity

Yashodha Chaku

Re: Scheduled Reminders should be activity

Dave Greenberg

Re: Scheduled Reminders should be activity

reperry

Re: Scheduled Reminders should be activity

Yashodha Chaku

Re: Scheduled Reminders should be activity

reperry

Re: Scheduled Reminders should be activity

Dave Greenberg

Re: Scheduled Reminders should be activity

Yashodha Chaku

Re: Scheduled Reminders should be activity