[rt-users] trouble setting custom field from scrips

[Gene LeDuc]

Might there be another scrip that is firing right after the one you 
described?  I was experiencing that sort of behavior in a workflow chain 
until I disabled all of the global scrips.  I've found that rt.log (logging 
at debug level) and my apache logs give a lot of useful information when I 
can't figure out what is going on.  In fact, when I'm working on new scrips 
or templates, I usually have "tail -f rt.log" and "tail -f 
www/logs/error.log" running in separate windows so I can watch what happens 
as the scrips and templates run (or don't).

At 02:42 AM 4/3/2007, Borut Mrak wrote:
>Borut Mrak wrote:
> > What happens is that in case the requestor responds, the custom field
> > gets set to 'Waiting', but right after that it falls back to
> > 'answered':
>
>My bad, it's the other way around. We display newest transactions first.
>The CF gets set to answered, and then right back to Waiting.
>
> > Mon Apr 02 08:29:42 2007      RT_System - WaitingForOwner answered
> > changed to Waiting
> > Mon Apr 02 08:29:42 2007      RT_System - WaitingForOwner Waiting
> > changed to answered


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