<html>
<body>
Hi Silvana,<br><br>
Since you're suspecting that an extra transaction might be causing your
problem, you probably need to find out what that extra transaction
is. The easiest way I've found to do this is to go into your rt3
database and look for the transaction number (from the rt log) in the
Transactions table (I like Toad for accessing mysql from Windows).
The Type, Field, OldValue, and NewValue fields should get you
started. Don't be tempted to make any changes, though.<br><br>
You also might want to double-check that the condition code in
"scrip Y" is producing TRUE only when the first custom field
changes value (not when any custom field changes):<br>
{ my $x = 7; return ($self->TransactionObj->Type eq
'CustomField') && ($self->TransactionObj->Field == $x);
}<br>
where $x is the field number for the first custom field.<br><br>
Good luck!<br>
Gene<br><br>
At 12:19 AM 4/19/2007, Silvana.Giberti@esa.int wrote:<br>
<blockquote type=cite class=cite cite=""><font size=2>I'm having problems
with scrips modifying the values of 2 custom fields.</font> <br><br>
<font size=2>The first custom field is created and assigned at ticket
creation (by scrip X), while the second custom field is updated whenever
the first one is modified (by scrip Y), that is after ticket creation and
also everytime the user modifes the first cf.</font> <br><br>
<font size=2>What sometime happens is that scrip Y updates the second
custom field twice, that is, a first time assigning the new value
and then a second time setting it back to its original value. Sometimes
instead the same scrips work properly on both custom fields, assigning
the right value also to the second one.</font> <br><br>
<font size=2>The same scrips work always well when the custom fields are
first created and assigned the first value.</font> <br><br>
<font size=2>Comparing the 2 cases in RT log file, it looks like there's
an extra transaction firing after the update of the second custom field,
but I can't tell what it does.</font> <br><br>
<font size=2>The function I call to update the custom fields is the
"AddCustomFieldValue", from Record.pm.</font> <br><br>
<font size=2>The custom fields are defined global for tickets in all
queues.</font> <br><br>
<font size=2>(RT 3.6.1, MySQL 4.1.12)</font> <br><br>
<font size=2>Does anyone have an idea of what to do to fix this
problem?</font> <br><br>
<font size=2>Thanks,</font> <br>
<font size=2>Silvana</font> </blockquote>
<x-sigsep><p></x-sigsep>
<br>
-- <br>
Gene LeDuc, GSEC<br>
Security Analyst<br>
San Diego State University</body>
</html>