Follow ups now work for the most part. Here's how it's implemented:



The JournalEntry form now keeps track of whether the subject has changed or the follow-up date has changed (using old_FollowUp_dt, in pretty much the same way that the calendar changes are tracked, so this doesn't look like it was put together by a committee.)



The QuerySave of the JournalEntry form calls a new script, fUpdateFollowUp. This checks a new view, "Follow-ups" for a document with a FollowUp_ID matching the UniqueID of the original JournalEntry. If not found, the new JournalEntry is created with a link back to the original. Otherwise, it's updated (in case the Follow-up date on the original is changed we don't want to create a string of To-Dos… However, I think in normal usage the Follow-up document will be the one to be changed.).



The Follow-ups view checks only for the FollowUp_ID, and not any particular document type, since the type could have been changed since it was created, from To-Do to Phone Call or Meeting.



The only thing it doesn't do at the moment is synch the follow-up doc with the calendar. I've been tossing that back and forth, and I think I've decided that I'd rather just display the follow-up doc after it's been created so the user can decide whether to synch it or change the Type right away. By default, the follow-on meeting is of the same type as the original.



So in a typical use case, you'd document your meeting, set the follow-up date, Click Save&Close, and then immediately be presented with a new JournalEntry that you can confirm, annotate, and Save. The end result is you save a bunch of time scheduling your next meeting, and from a user's point of view there's nothing "new" or different about a follow-up notification… it's just your next meeting.