Sorry, I guess I should have followed the chain farther back. I see now that you are on 5.1.2. I'm using 6.3 (ARS and email engine) for this process.
Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "L G Robinson" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 01/19/2008 06:33 AM Please respond to [email protected] To [email protected] cc Subject Re: Appending headers to outgoing email messages Hi Thad, During my experimentation, I tried exactly what you have described, but it did not work for me. Can you tell me what version of ARS server and email engine you are using? Thanks. Larry On Jan 18, 2008, at 5:05 PM, Thad K Esser wrote: > ** > Larry, > > In regards to your first bullet: > "It is not possible to pass a multi-line character value to > any of the email header fields using the Notify action." > > I'm actually doing just that. In my scenario I use a temporary > character field and build out the header elements I want, making > sure the first character is a hard return which ensures that its at > the start of a new line in the header. And then in the Notify > action, I use the Organization field on the Messages tab, as Fred > suggests, and put my temp char field there. > > Action one: Set fields, $ztmpChar$ = "|Importance: 1" (where the > pipe symbol represents a hard return) > Action Two: Notify, set Organization field to $ztmpChar$ (and of > course all the other information you need for the notify). > > Works like a champ. Hopefully that helps. > > Thad Esser > Remedy Developer > "Argue for your limitations, and sure enough, they're yours."-- > Richard Bach > > > "L G Robinson" <[EMAIL PROTECTED]> > Sent by: "Action Request System discussion list(ARSList)" > <[email protected]> > 01/18/2008 01:42 PM > Please respond to > [email protected] > > To > [email protected] > cc > Subject > Re: Appending headers to outgoing email messages > > Hi Carey and Fred, > > Thanks for the replies and suggestions. After experimenting for a > day, I have found the following: > > - It is not possible to pass a multi-line character value to any > of the email header fields using the Notify action. > > - It is possible to send multi-line character values to headers > fields by pushing directly to the "AR System Email Messages" > form. This almost works. > > When I push values directly to the form, a couple of other problems > have popped up: > > - The email messages created by a Push action do not get deleted after > they are sent, but they do get deleted automatically when the > message > is created by using a Notify action. I suspect that I am missing > some > critical value when pushing, but I have not been able to identify > the > missing field yet. > > - My goal is to add two custom headers to the outgoing email message: > X-Sender: Prog=arserver - Group=TEST - Type=Ownership > X-Mailer: Prog=arserver - Group=TEST - Type=Ownership > > As suggested, the content is dynamic such that workgroup will > change. > When I append these headers to the "Organization:" header, they DO > make it through to the Email Messages form and they DO make it into > the actual email that gets delivered. That is good! However, on my > console, if I start the ARServer manually, I see the following error > message each time a record is pushed to the Email Messages form: > > sh: X-Mailer:: not found > > So obviously, something isn't quite right. > > Anyway... sorry this is so long. I'll keep poking at it to see if I > can > stumble upon a winning combination. > > Thanks for your suggestions. > Larry _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
