Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
654
Reminder Questions
posted

Hello -

I've been using the WebSchedule components to see how difficult our implementation will be.  In doing so I've run into some quirks of the reminder features.  Any insight on the items below would be appreciated:

 

1) Snooze Functionality - It doesn't look like the original data structures account for storing snooze information.  I also see that there are 2 different persistance types for snooze information (Cookie and ControlState).  I didn't notice any difference when using these two.  When I refresh the page I always get reminders for the items I previously snoozed.  Is there a trick to this that I'm missing?  I'm just setting the SnoozePersistenceType on my custom DataProvider.  Should I have implemented something to handle this?

 

2) Reminders and Recurrence - When a reminder is dismissed, I see the UpdateReminder event firing, which is great.  The problem is that the same event seems to fire when dismissing a recurring event and a standard activity - but it sends in a recurrenceID (not an activityID) when dismissing a recurring event.  I haven't seen a way to distinguish whether I should update a recurrence or a standard activity.  The UpdateRemindersContext has no way to tell between the two.  Complicating this is the fact that recurrences seem to be added to the reminder list by default.  I'm not adding them in my FetchReminders method, but reminders are popping up for them (and I can't dismiss them properly).  Has anyone else noticed these problems?

Parents Reply Children
No Data