Order of multiple transactions in request

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
somehow.

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?

Our RT version is currently 4.2.11.

Thanks!

Marcos.

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
somehow.

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.

-m

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
somehow.

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. :wink:

-m

Thanks Matt!

wrote:l

The limitation of TxnBatch not updating the list of email recipients
should be fixed in 4.4.

Updating was in our short term plans. I’m glad to know this limitation was
removed.

Any other undesirable effects of using batch?

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. :wink:

https://metacpan.org/pod/RT::Extension::AjaxPreviewScrips

I understand this was integrated into 4.4 core?

Marcos

https://metacpan.org/pod/RT::Extension::AjaxPreviewScrips

I understand this was integrated into 4.4 core?

@BPS,

Can you confirm the merge of AjaxPreviewScrips in 4.4?

-m

https://metacpan.org/pod/RT::Extension::AjaxPreviewScrips
I understand this was integrated into 4.4 core?
@BPS,

Can you confirm the merge of AjaxPreviewScrips in 4.4?
Yes, this appears to be the commit that pulled in that code: