I’m currently developing a scrip which is meant to act based on a
field on the transaction, however it appears that at the point the
is fired, the transaction’s custom fields havn’t been saved yet.
It may be that I just need to find a different way to deal with this
problem, but I was wondering if that is considered a bug, or just how
It’s a longstanding design issue. The “right” fix would be very, very
invasive. I believe that if you move your new scrip to the
TransactionBatch stage, things will work out for you.
Thanks - that’s exactly what I was looking for, and actually resulted in
nicer code then I had anyway.
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
21 Southampton Row
London - WC1B 5HA
+44 (0)20 7685 8643
Company registration no: 3152737
Place of registration: England
All the information contained within this this electronic message from
Claranet Ltd is covered by the disclaimer at