Dwayne, I implemented a similar approach to Carey here. One additional data element that I track is a notification code. This code is a small character field that is populated by the Push to the child form.
Each filter, active link or other ARS object that needs to send a notification has a unique code. This code appears on all html emails in a tiny font at the bottom of the email. If a user has a question as to why they received a particular email, the code allows me to rapidly track down what process (ie. ARS object) initiated the notification. For those few notifications where the code should not appear I include it as hidden text within the html email. If I need to see it I select View Source in the email to see the html code. HTH Stephen Remedy Skilled Professional -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Thursday, September 13, 2007 1:35 PM To: [email protected] Subject: Re: Push field sometimes happens and sometimes doesn't Dwayne, I actually prefer a slight variation on the "archive form" approach.... IMHO, the root problem is that you want to keep a parent child relationship in a diary field content. I suggest that you let go of the v3 and v4 thinking and use a table field to the child records. Instead of having "AR System Email Messages" have "custom" workflow/fields start with the creation of the child record and then have the child record create a record in "AR System Email Messages". ( The more we can leave the BMC generated/maintained forms unchanged, the better IMO. ) What this does is effectively what your after. There is no way that the person gets the email without a record in the "child" form. The support agents have a table field showing the whole (or parts) of the email that was queued to be sent. You do not loose any kind of "delivery" or "error" messages that the other ordered approach would have given you either. You would need to use a Push action to do a "Notify" action, but that should really not be an issue. And your "child" form could even do a Notify action if you want it to. ( Well, if the templates your using can be supported from data stored in the child form. However, the child form would also allow you to publish [to Public] some fields that are private [non-Public] on the parent form too.) In short I think you already have the forms in place, I just think the data flow is in the wrong direction between a few of the forms. :) HTH. -- 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 9/13/07, Dwayne Martin <[EMAIL PROTECTED]> wrote: > Doug, > > Thanks! I can see some advantages of your approach over mine. I'll have to consider it. > > Dwayne > > ---- Original message ---- > >Date: Thu, 13 Sep 2007 09:21:15 -0400 > >From: "Tanner, Doug" <[EMAIL PROTECTED]> > >Subject: Re: Push field sometimes happens and sometimes doesn't > >To: [email protected] > > > > ** > > > > Dwayne, > > > > An approach I like to take is > > > > > > > > 1>) Create a form for historical storage of email > > messages > > > > I do this by creating a form called "CMN:Email > > Correspondence" > > > > This form has a lot of the fields - To, From, > > Subject, Body, etc > > > > From AR System Email Messages > > > > In addition to other fields I use for workflow > > > > > > > > Basically On Submit (Or Modify - Your choice) > > ON AR Email Messages > > > > I push (Create) a Permanent record over in > > CMN:Email Correspondence > > > > Passing my GUID from the original "Entry" This > > way I can tie it together > > > > Typically in a table field on the > > request. > > > > > > > > Hit me off list if you want some more details > > > > > > > > Doug > > > > Dwayne Martin > Computing Support > James Madison University ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
