[rt-users] Custom Fields / Transaction Custom Fields inScrips [FIX!]

Mike Coakley mcoakley at managedbusiness.com
Thu Jul 20 09:06:38 EDT 2006


Jesse,

Thanks for the reply and that makes complete sense to this old
C++/Java/Object Pascal (yeah I'm dating myself) programmer. I've started to
look through the code for RT but haven't gotten through it enough to wrap
myself around the object hierarchy and philosophies behind its design. I'll
keep on digging and maybe I can come up with a patch that can make it into
the core.

Thanks,

-- 
Mike Coakley
Managed Business
http://www.managedbusiness.com
http://my.managedbusiness.com
Voice - 973-252-0770 x2100
Fax - 973-252-1797




> From: jesse vincent <jesse at bestpractical.com>
> Date: Wed, 19 Jul 2006 16:24:48 -0700
> To: <mcoakley at managedbusiness.com>
> Cc: <rt-users at lists.bestpractical.com>
> Subject: Re: [rt-users] Custom Fields / Transaction Custom Fields inScrips
> [FIX!]
> 
> Unfortunately, the patch violates abstraction barriers all over the place. Io
> never found a way to do it cleanly
> 
> ------- Original message -------
> From: Mike Coakley <mcoakley at managedbusiness.com>
> Sent: 19.7.'06,  16:33
> 
>> For anyone following this thread (doubtful as it is old) I've got everything
>> working. After looking through the code I noticed that the patch that Jesse
>> had released for 3.4 that I had tried to apply did not apply fro some reason
>> although I didn't remember getting any errors. So I re-applied the patch to
>> my 3.6 and everything is working as I expected it in the past.
>> 
>> So, I concur with Jesse... His patch does fix the issue :-D
>> 
>> Now my only question would be why isn't this patch in the core yet as of
>> 3.6?
>> 
>> Thanks,
>> 
>> -- 
>> Mike Coakley
>> Managed Business
>> http://www.managedbusiness.com
>> http://my.managedbusiness.com
>> Voice - 973-252-0770 x2100
>> Fax - 973-252-1797
>> 
>> 
>> 
>> 
>>> From: Mike Coakley <mcoakley at managedbusiness.com>
>>> Date: Fri, 07 Jul 2006 15:30:03 -0400
>>> To: "rt-users at lists.bestpractical.com" <rt-users at lists.bestpractical.com>
>>> Conversation: [rt-users] Custom Fields / Transaction Custom Fields in Scrips
>>> Subject: Re: [rt-users] Custom Fields / Transaction Custom Fields in Scrips
>>> 
>>> Hello all...
>>> 
>>> In further attempts to get this working I've done the following:
>>> 
>>> 1. I upgraded to RT 3.6.0. Upgrade went smooth but this still does not work.
>>> 
>>> 2. In further research I found an article in the archives that stated that
>>> this was a known issue back in the 3.4 timeframe basically stating the the
>>> Transaction Custom Fields don't get populated until after the scrips are
>>> run. There was a patch file available through the archives but this patch
>>> file also did not fix my issue.
>>> 
>>> So, I'm wondering if anyone has any further help or places I can look.
>>> 
>>> Thanks,
>>> 
>>> -- 
>>> Mike Coakley
>>> Managed Business
>>> http://www.managedbusiness.com
>>> http://my.managedbusiness.com
>>> Voice - 973-252-0770 x2100
>>> Fax - 973-252-1797
>>> 
>>> 
>>> 
>>> 
>>>> From: Mike Coakley <mcoakley at managedbusiness.com>
>>>> Date: Wed, 05 Jul 2006 16:02:42 -0400
>>>> To: <rt-users at lists.bestpractical.com>
>>>> Conversation: Custom Fields / Transaction Custom Fields in Scrips
>>>> Subject: [rt-users] Custom Fields / Transaction Custom Fields in Scrips
>>>> 
>>>> I'm trying to write a custom condition that will trigger every time a
>>>> transaction custom field is updated that will update other custom fields.
>>>> The idea is to keep track of time in a better way.
>>>> 
>>>> So I have 2 custom fields: Billable Time and Non-Billable Time. These are
>>>> attached to a ticket. I can easily manually update these fields. I also
>>>> have
>>>> two Transaction based custom fields: TRANS Billable Time and TRANS
>>>> Non-Billable Time. I want to have a condition that fires when the "TRANS*"
>>>> fields get updated. Then when the condition is fired the action will be to
>>>> update the Billable Time and Non-Billable Time field appropriately.
>>>> 
>>>> I've been doing some debugging within the Scrip condition and it appears
>>>> the
>>>> condition gets tested twice during a "comment" (haven't worked on reply
>>>> yet). BUT I don't see the transaction custom field values so my condition
>>>> fails. So I'm either not retrieving the transaction custom field values
>>>> improperly (I get no value) or I'm not seeing the right condition.
>>>> 
>>>> Anyone have any ideas?
>>>> 
>>>> Thanks,
>>>> 
>>>> -- 
>>>> Mike Coakley
>>>> Managed Business
>>>> http://www.managedbusiness.com
>>>> http://my.managedbusiness.com
>>>> Voice - 973-252-0770 x2100
>>>> Fax - 973-252-1797
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>>>> 
>>>> 
>>>> We're hiring! Come hack Perl for Best Practical:
>>>> http://bestpractical.com/about/jobs.html
>>> 
>>> _______________________________________________
>>> 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
>>> 
>>> 
>>> We're hiring! Come hack Perl for Best Practical:
>>> http://bestpractical.com/about/jobs.html
>> 
>> _______________________________________________
>> 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
>> 
>> 
>> We're hiring! Come hack Perl for Best Practical:
>> http://bestpractical.com/about/jobs.html
>> 
> 




More information about the rt-users mailing list