I figured out the problem (a template attached to a scrip whose condition
was true wasn't being run). The problem was in the template; I had typed a
"(" instead of a "{" in an if-else block. RT wasn't catching that there
was an unmatched curly brace and an unmatched open parenthesis in the
te
I just tried hard-coding the headers into the template like so (minus the
"begin" and "end" lines):
= begin template
To: [EMAIL PROTECTED]
Subject: Is the template firing?
{ $RT::Logger->debug("Template DNS:26 (Acknowlege): Entering template");
#(more template code goes here)
}
=
The Acknowledge template builds the $OUT variable, and the first part of
that happens kind of deeply in the template code. When I finally get to
it, it goes like this:
$OUT = "To: $uEmail
Subject: $subj
A request to register a DNS entry has been received by the IT Security
Office with the fo
Gene,
I'm certainly no expert, but usually it's the simple assumed things
that bite us. You're stated
"Since the returned value ($val) is 1, the Acknowledge template should
get run, but it doesn't. I'm certain of this because the first line of
the template is:
{ $RT::Logger->debug("Templat
At Tuesday 4/17/2007 02:00 PM, Gene LeDuc wrote:
Hi All,
I've been scratching my head over this for 2 days and haven't been
able to solve it. I have a scrip that is not firing the Notify
Others action when its user-defined condition is true. The scrip
fires, the condition is true, but the e
Hi All,
I've been scratching my head over this for 2 days and haven't been able to
solve it. I have a scrip that is not firing the Notify Others action when
its user-defined condition is true. The scrip fires, the condition is
true, but the execution chain simply ends without the template ge
