Re: [rt-users] Order of multiple transactions in request
On 3/14/16 7:29 PM, Matt Zagrabelny wrote: On Mon, Mar 14, 2016 at 1:25 PM, Marcos Orallo wrote: 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: https://github.com/bestpractical/rt/commit/098c568f - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
Re: [rt-users] Order of multiple transactions in request
On Mon, Mar 14, 2016 at 1:25 PM, Marcos Orallo wrote: >> 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 - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
Re: [rt-users] Order of multiple transactions in request
Thanks Matt! El 14/3/2016 7:10 p. m., "Matt Zagrabelny" escribió: > > On Mon, Mar 14, 2016 at 1:08 PM, Matt Zagrabelny 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. ;) > > https://metacpan.org/pod/RT::Extension::AjaxPreviewScrips I understand this was integrated into 4.4 core? Marcos - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
Re: [rt-users] Order of multiple transactions in request
On Mon, Mar 14, 2016 at 1:08 PM, Matt Zagrabelny wrote: > On Mon, Mar 14, 2016 at 12:03 PM, Marcos Orallo 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 >> 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. ;) https://metacpan.org/pod/RT::Extension::AjaxPreviewScrips -m - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
Re: [rt-users] Order of multiple transactions in request
On Mon, Mar 14, 2016 at 12:03 PM, Marcos Orallo 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 > 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 - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
[rt-users] 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. - RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
