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
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 Waitin
Hello,
I'm having a little trouble setting a custom field from a scrip.
What I'm trying to do is add some kind of notification so web interface
users see which of their tickets has unanswered customer responses.
What I have now is:
Description: WaitingFieldOnTransaction
Condition: OnTransaction
