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
On Jan 17, 2008, at 1:57 PM, Grooms, Frederick W wrote:
> I never got it to work in the Subject field, but it does (did) work
> using the Organization field. (Instead of using the Notify action I
> may
> also have been doing a Push Fields action to the messages form)
>
> Fred
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
> Sent: Thursday, January 17, 2008 12:25 PM
> To: [email protected]
> Subject: Re: Appending headers to outgoing email messages
>
> Larry,
>
> You are not imaging that behavior. ( and I think the Email Engine did
> change[AKA: break] how this worked.)
>
> Ref admin_vol1.pdf pg 9-38
> "
> You can include extra header lines in your email message by inserting
> hard returns followed by approximately formatted mail headers in the
> Subject Line field. The resulting notification will contain a Subject
> Line and your header lines. The total of all data must be 255
> characters
> or less.
> "
>
> However in the new(est?) Email Engine you do something like this, but
> totally differently... (and I am not sure this works before v7.1
> either)
>
> Ref: Email-Engine-710.pdf pg:198
> "com.bmc.arsys.emaildaemon.AdditionalMailHeaders=X-Loop-Detect"
>
> But if your content needs to be dynamic... then this option would
> likely
> not meet your needs either.
>
>
> I doubt that helps.. but... Maybe someone else can show us how this
> can
> be done in v5.1.2?
>
> --
> 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 Jan 17, 2008 10:20 AM, L G Robinson <[EMAIL PROTECTED]> wrote:
>> Hi Folks,
>>
>> I can not remember if this used to work, or if it is just something I
>> imagined...
>>
>> When sending email notifications using the Notify action in a filter,
>> I thought that it was possible to add additional email headers to the
>> outgoing email message by appending them to the end of the Subject
>> field, provided you were able to get the newline character into the
>> string.
>>
>> This doesn't seem to be working for me anymore and I'm not sure when
>> it stopped working. Did this used to work as I have described?
>>
>> I am currently running ARS 5.01.02 P1313 on Solaris 8. Maybe this
>> stopped working with the advent of the email engine?
>>
>> Is there any way to make this work as described in a 5.01.02 system?
>>
>> Thanks.
>> Larry
>>
>>
>> Larry Robinson [EMAIL PROTECTED]
>> Office Of Information Technology
>> NC State University 919-515-5432 Voice
>> Raleigh, NC 27695-7109 919-513-1893 FAX
>>
>
>
_______________________________________________________________________________
> 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"
***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"
