Axton,
Thanks for articulating my muddled pile of thoughts. I knew
what I wanted, and I kinda knew how to get there, but I didn't know
exactly how to say it. You have pointed me in precisely the correct
direction. You're the man!
Thanks again,
Michael
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Thursday, November 08, 2007 12:01 PM
To: arslist@ARSLIST.ORG
Subject: Re: One notification engine to rule them all?
Read up on external qualifications and advanced workflow. You can very
easily write a small set of forms workflow to store the notifications to
be sent, to whom they are sent, and when they are sent. Think of using
a config form that stored the following info:
- form (which form the notification fires from)
- to (fieldid)
- subject (the subject text, can substitute variables)
- body (body, can substitute variables)
- fire when (external qual to evaluate on modify)
One tricky thing will the the include fields if you want to use
templates.
This could be integrated to any number of forms by walking a table
(where $SCHEMA$ = 'form') and firing advanced workflow if the qual is
met.
Axton Grams
On Nov 8, 2007 1:38 PM, Durrant, Michael M. - ITSD
<[EMAIL PROTECTED]> wrote:
> **
>
> Like Bing Crosby, I'm dreaming, but not of a White Christmas. I'm
> dreaming of a single set of forms and workflow that I would use to
> control all of my notifications. Originally, my co-worker and I
> envisioned a single system for ALL notifications, regardless of the
> form. Realizing that was quite the undertaking, we're limiting it to
one form right now: HPD:HelpDesk.
>
> The idea is "Send xxxxxxx notification to yyyyyyyyy based on criteria
> a, b, and c (and possibly d through z)." I can see a few different
> ways of doing this - has anyone already done it?
>
> Thanks,
>
> Michael The information contained in this email may be privileged,
> confidential or otherwise protected from disclosure. All persons are
> advised that they may face penalties under state and federal law for
> sharing this information with unauthorized individuals. If you
> received this email in error, please reply to the sender that you have
> received this information in error. Also, please delete this email
after replying to the sender.
> __20060125_______________________This posting was submitted with HTML
> in it___
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
The information contained in this email may be privileged, confidential or
otherwise protected from disclosure. All persons are advised that they may
face penalties under state and federal law for sharing this information with
unauthorized individuals. If you received this email in error, please reply to
the sender that you have received this information in error. Also, please
delete this email after replying to the sender.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
