here the logs will help you, or the email message form comes in handly as it will have all the email which is genereated/Created from the system
On Wed, Jul 25, 2012 at 5:20 PM, Joe <hornetlo...@gmail.com> wrote: > Thanks Everyone for the input, > > Based on your inputs I believe the best path is to create a custom Status > Reason instead of a custom Status. Then create a notification based on the > qualification of Status="Resolved" and Status Reason="<custom reason>" > (with obvious syntax corrections). > > There is not an SLA tied to this. > > 1. My plan is to create a filter that is similar to the current one that > will fire a notification based on the qualification Status="Resolved" and > Status Reason="<custom reason>" (with obvious syntax corrections). > > 2. Create an entry in SYS:Notification Messages for this specific > reassigned email message with corrected verbiage. > 3. Add the "reassigned" selection to the Status Reason menu. > > How can I test that it creates the email correctly? In our test > environment we do not have email engine connected. > What workflow makes the "tiering" on status reason connect with the > various selections in status? I think I need to add my custom field to > that workflow. > > Anything you think I might have missed? > > Thanks! > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
