Hi there,
I would like to check the value of a transaction custom field in a scrip
condition to trigger an action.
It seems, however, that I can’t achieve this purpose. I found that the
custom field for a transaction is not set when IsApplicable() is called.
The transaction custom field is set in Interface/Web.pm separately after
the transaction is created.
Any alternatives are available?
Any suggestion is appreciated.
Sometime around 6 months ago, I sent out mail with a patch to enable
this feature. It was way too hacky to be reasonable to include in the
core, but might be reasonable to use in your situation.On Wed, Mar 29, 2006 at 11:43:20AM +0800, lwang wrote:
Hi there,
I would like to check the value of a transaction custom field in a scrip
condition to trigger an action.It seems, however, that I can’t achieve this purpose. I found that the
custom field for a transaction is not set when IsApplicable() is called.The transaction custom field is set in Interface/Web.pm separately after
the transaction is created.Any alternatives are available?
Any suggestion is appreciated.
- Wang
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.comDiscover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.comWe’re hiring! Come hack Perl for Best Practical:
Careers — Best Practical Solutions
Jesse,
Did you post your patch in rt-user list or rt-devel list?
Thanks.
Jesse Vincent wrote:
Jesse,
Did you post your patch in rt-user list or rt-devel list?
I think it was rt-devel. But I found and attached the patch. Thanks to
svk 
transaction-cfs-for-scrips.patch.patch (6.26 KB)
Jesse,
Thank you very much! It works!
Jesse Vincent wrote: