[rt-users] Order of multiple transactions in request
mzagrabe at d.umn.edu
Mon Mar 14 14:10:25 EDT 2016
On Mon, Mar 14, 2016 at 1:08 PM, Matt Zagrabelny <mzagrabe at d.umn.edu> wrote:
> On Mon, Mar 14, 2016 at 12:03 PM, Marcos Orallo <m_orallo at yahoo.es> wrote:
>> Hi all,
>> I would like to know what determines the order of creation when a request is
>> translated into more than one transaction, and if this can be customized
>> My use case: I want to add a tag [Resolved] to the subject of the resolving
>> comment *and only that*.
>> From what I've seen, the Comment transaction always happens before the
>> Status change. Thus, the only way for any On Comment Notify X scrip to be
>> aware of the status change is to run it in Batch stage. But this eliminates
>> the possibility of identifying and modifying the recipients of the comment
>> while composing it, which is not acceptable for us.
>> Do you know any alternative way to achieve the same behaviour?
> The limitation of TxnBatch not updating the list of email recipients
> should be fixed in 4.4.
> We have an extension that BP wrote for us that I could share with you
> if upgrading isn't feasible.
...or you could download it yourself. ;)
More information about the rt-users