Currently I have a content type that contains 10 date fields that I use as reminders. Not every date field is necessary. What I would like to do is to create my normal document, fill out the normal meta-data and then if I need a reminder date, I would click on a link that would create a reminder date field and attach it to the document. If I needed two reminder fields, I would be able to "add" these reminders twice. Currently I have some documents that have up to 10 events that need "reminding". My first solution was to create 10 separate fields. That works. Now I'm looking for a cleaner solution. Ideas?
Stump the Panel » Site Managers and Site Collection Managers
Create content type with one to many relationship
(3 posts)-
dipetersen
MemberPosted 1 week ago # -
I had similar issues, I ended up trying to coerce people into taking a more proactive view of the world rather than being constantly pinged by reminders. I built a series of views on the list along the lines of "due next 7 days", "due next 14 days", "due next 30 days" etc and advocated that the team utilised these views during their weekly planning sessions to ensure that they had capacity to address and ensured that all actions were addressed.
Obviously this approach does not work with the headless chicken teams, of which I work with many, I'm looking forward to hearing if anybody else has an approach to resolve the 'multi stage reminder' approach which gets asked for so frequently!
Posted 1 week ago # -
gmaass
MemberCreate a dedicated list for reminders, and run a custom workflow off of this list:
-Whenever a new item is added to the reminder list, the workflow waits until the reminder date, and then sends a reminder email (or whatever action is appropriate) that contains a link to the document.
-You can also have a view on the reminder list per 27palms use above.Posted 1 week ago #
Reply
You must log in to post.