TransactionBatch scrips always run after TransactionCreate scrips.
If it's running three times, it's quite possibly still applied to a queue
(or globally) in Create mode.
I test whether a scrip is running in batch mode using:
if (my @txns = @{ $self->TicketObj->TransactionBatch }) {
# batch mode; iterate over @txns
...
}
else {
# create mode
...
}
On 17/09/2014 3:09 am, "andriusk" <[email protected]> wrote:
> How should I make my TransactionBatch scrip run after all changes inducing
> scrip? Is it enought if it is the only scrip in batch mode? Because now I
> get this batch scrip run after every different type transaction (3 changes
> -
> status, subject, customfield - 3 times ran scrip in batch mode. Also I dont
> think that checking TicketObj->RanTransactionBatch is correct to determine
> if the scrip done its job in scrip with batch mode?
>
>
>
> --
> View this message in context:
> http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58557.html
> Sent from the Request Tracker - User mailing list archive at Nabble.com.
> --
> RT Training - Boston, September 9-10
> http://bestpractical.com/training
>
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
