Good point. I assumed..and yes, I know what they say about assumed: 

 

"50 bonus points for using all of your tiles in Scrabble"

 

:-)

 

The @@: can be dropped if this is in a filter.

 

Curious: What does  $Email Body$ contain? If it is the full email body that
could be causing the issue. The $PROCESS$ command tops out at 4096
characters long according to the workflow object guide:

 

The $PROCESS$ tag indicates that all text that follows is a command line.
The

command line can include substitution parameters from the current screen to

enable values to be placed into the command line before it is executed. You
can

enter as many as 255 characters for your command definition. The command can

be as many as 4096 characters after the substitution parameters are expanded

 

--- J.T. Shyman

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Thursday, December 11, 2008 10:40 AM
To: arslist@ARSLIST.ORG
Subject: Re: set fields by process error

 

That would only work if the process was running via Active Link...which Anne
didn't specify

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman
Sent: Thursday, December 11, 2008 9:00 AM
To: arslist@ARSLIST.ORG
Subject: Re: set fields by process error

** 

Try changing the command to: 

 

$PROCESS$ @@:echo ""$Email Body"" |
/home/aramey/html2text-0.003/html2text.pl

 

If that doesn't work, start with something simple and work up from there.
Change the set fields to something like

 

$PROCESS$ @@:echo $HOSTNAME

 

And see if that sets the field. If it does try

 

$PROCESS$ @@:echo ""$Request ID"" 

 

(or some other, short field)

 

If that works, it may not be liking fact that the return has multiple lines.
It may see that as multiple values and not a single value for the set
fields.

 

--- J.T. Shyman

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ramey, Anne
Sent: Thursday, December 11, 2008 9:45 AM
To: arslist@ARSLIST.ORG
Subject: set fields by process error

 

I am getting an exit code: 127 set fields action error when trying to use
the following in a set fields action to strip HTML from an email body:

$PROCESS$ "echo ""$Email Body$"" | /home/aramey/html2text-0.003/html2text.pl
"

 

The process works fine when I run it from the command line:

btw, it does work from the command line:

[EMAIL PROTECTED] db#  echo "<h2>Test header</h2><br>test<br>

> Anne Ramey

> test" | /home/aramey/html2text-0.003/html2text.pl

Starting /home/aramey/html2text-0.003/html2text.pl ...

Test header

===========

 

 

test

Anne Ramey test

 

Anyone know what exit code 127 means? or see any syntax errors?  I can't
find the set field error exit codes anywhere in the documentation.

 

AR System 7.0.1 Patch 5, ITSM 7.0.03 patch 7 on Red Hat Linux.  Oracle
backend.

 

Thanks,

 

Anne Ramey
***********************************

E-mail correspondence to and from this address may be subject to the North
Carolina Public Records Law and may be disclosed to third parties only by an
authorized State Official.

 

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are" html___

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to