[rt-users] help with incoming scrip

[Gene LeDuc]

Hi Chris,

I'm not familiar with the extension, but a couple of observations might 
help (or not).

1.  With other templates, you would use "$Transaction->" instead of 
"$self->TransactionObj->".  I don't know whether this is true for this 
extension.  The "$self" notation generally applies to scrips.

2.  It looks like you're setting the subject of the transaction rather than 
the ticket.  I'd try "$Ticket->Set(Subject=>$_)" assuming that the Set 
syntax is correct.  Or "$self->TicketObj->Set(Subject=>$_)" if I'm off-base 
with observation #1.

Just some place to start looking.

Regards,
Gene

At 02:06 PM 4/13/2008, Chris Haumesser wrote:
>Ok, yes... ExtractCustomValues appears to be capable of doing what I want.
>
>I'm unclear on what I can put in the "script" field of the template.
>For example, here's what I've done...
>
>
>1.  Created template in my queue containing the following:
>
>||Body|^Title:\s*(.*)|$self->TransactionObj->Set( Subject => $_ )||
>
>
>2.  Created scrip in my queue: on create, extract custom values, my new
>template.
>
>
>3.  Send test messages; subject does not change, nothing in syslog.
>
>
>I have a feeling that the "script" field in my template isn't right.
>What can I put in this field???
>
>Appreciate any pointers in the right direction...
>
>
>
>-C-
>
>
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Community help: http://wiki.bestpractical.com
>Commercial support: sales at bestpractical.com
>
>
>Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>Buy a copy at http://rtbook.bestpractical.com


-- 
Gene LeDuc, GSEC
Security Analyst
San Diego State University