Mark, I prefer the approach that the data rules them all.
I would suggest that if you do not yet have a date/time field in the record that is for 'Notify At' that is set via workflow at Submit/Modify that you start there. Then the "variable" is in the workflow, which can also be data driven. That way your Escalation simply has to "fire often enough" to send out the batch runs. (one a month, day, week, hour, etc..) It would compare "now" (TIMESTAMP) with the 'Notify At' field. If now >= 'Notify At' then touch the record (set field action) and have workflow(filters) on the record send the notification and set/reset the 'Notify At' field as the specs require. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Fri, Feb 22, 2008 at 7:47 AM, Mark Milke <[EMAIL PROTECTED]> wrote: > Hi Listers, > > I need to check a date field in form and notify users x weeks before > that date is reached. > The x should be configurable. Currently it's 3 weeks, but we want to > be able to change it to a different value. > > What is the most elegant solution for that? > > > Regards > > Mark > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
