Re: [rt-users] Catch all ticket changes in one scrip
Another question. Are the transactions of changes to a ticket made by web UI (fields selected in web ui) and by scrips, that change some other value because one of values was changed by UI, assigned to the same TransactionBatch? 2014-09-23 02:24, Alex Peters [via RequestTracker] rašė: You have established beyond doubt that the SLA extension is breaking core scrip logic. Please file a bug report against the SLA extensionn -- RT Training November 4 5 Los Angeles http://bestpractical.com/training If you reply to this email, your message will be added to the discussion below: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58599.html To unsubscribe from Catch all ticket changes in one scrip, click here http://requesttracker.8502.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=58372code=YW5kcml1cy5rdWxiaXNAZ21haWwuY29tfDU4MzcyfDEwMTAwODYxNzU=. NAML http://requesttracker.8502.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- Pagarbiai Andrius Kulbis -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58602.html Sent from the Request Tracker - User mailing list archive at Nabble.com.-- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
I made a new installation. This is the log, which I got from changing tickets /*Subject, Status, Priority and Due*/ on queue */General/* with /*1 scrip in TransactionBatch*/ mode (CustomCondition: 1; Custom action preparation code: 1; Custom action commit code: 1;), no extensions installed. [10295] [Mon Sep 22 08:22:46 2014] [debug]: Rendering attachment #1 of 'text/html' type (/opt/rt4/share/html/Elements/ShowTransactionAttachments:182) [10294] [Mon Sep 22 08:23:03 2014] [debug]: RT::Date used Time::ParseDate to make '2014-09-25 00:00:00' 1411628400 (/opt/rt4/sbin/../lib/RT/Date.pm:240) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #34 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #34 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #34 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #34 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #35 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #35 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #35 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #35 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #36 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #36 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #36 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #36 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #37 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 3 scrips for TransactionCreate stage with applicable type(s) Status for txn #37 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #12 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #37 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #37 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #38 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #38 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Converting 'utf-8' to 'utf-8' for text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Converting 'utf-8' to 'utf-8' for text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Encode::Guess guessed encoding: utf8 (/opt/rt4/sbin/../lib/RT/I18N.pm:574) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Encode::Guess guessed encoding: utf8 (/opt/rt4/sbin/../lib/RT/I18N.pm:574) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #38 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #11 on txn #38 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Calling SetRecipientDigests for transaction RT::Transaction=HASH(0x7f28f814dcd8), id 38 (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:623) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Working on mailfield To; recipients are (/opt/rt4/sbin/../lib/RT/Action/SendEmail.pm:639) [10294] [Mon Sep 22
Re: [rt-users] Catch all ticket changes in one scrip
You have established beyond doubt that the SLA extension is breaking core scrip logic. Please file a bug report against the SLA extension. On 22/09/2014 6:41 pm, andriusk andrius.kul...@gmail.com wrote: I made a new installation. This is the log, which I got from changing tickets /*Subject, Status, Priority and Due*/ on queue */General/* with /*1 scrip in TransactionBatch*/ mode (CustomCondition: 1; Custom action preparation code: 1; Custom action commit code: 1;), no extensions installed. [10295] [Mon Sep 22 08:22:46 2014] [debug]: Rendering attachment #1 of 'text/html' type (/opt/rt4/share/html/Elements/ShowTransactionAttachments:182) [10294] [Mon Sep 22 08:23:03 2014] [debug]: RT::Date used Time::ParseDate to make '2014-09-25 00:00:00' 1411628400 (/opt/rt4/sbin/../lib/RT/Date.pm:240) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #34 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #34 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #34 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #34 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #35 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #35 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #35 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #35 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #36 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #36 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #36 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #36 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #37 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 3 scrips for TransactionCreate stage with applicable type(s) Status for txn #37 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #11 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Skipping Scrip #12 because it isn't applicable (/opt/rt4/sbin/../lib/RT/Scrips.pm:353) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #37 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #13 on txn #37 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to prepare scrips for transaction #38 (/opt/rt4/sbin/../lib/RT/Transaction.pm:187) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Found 2 scrips for TransactionCreate stage with applicable type(s) Set for txn #38 on ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:495) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Converting 'utf-8' to 'utf-8' for text/plain - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Converting 'utf-8' to 'utf-8' for text/html - Subjectless message (/opt/rt4/sbin/../lib/RT/I18N.pm:295) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Encode::Guess guessed encoding: utf8 (/opt/rt4/sbin/../lib/RT/I18N.pm:574) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Encode::Guess guessed encoding: utf8 (/opt/rt4/sbin/../lib/RT/I18N.pm:574) [10294] [Mon Sep 22 08:23:03 2014] [debug]: About to commit scrips for transaction #38 (/opt/rt4/sbin/../lib/RT/Transaction.pm:210) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Committing scrip #11 on txn #38 of ticket #1 (/opt/rt4/sbin/../lib/RT/Scrips.pm:306) [10294] [Mon Sep 22 08:23:03 2014] [debug]: Calling
Re: [rt-users] Catch all ticket changes in one scrip
I would try to explain my situation again. I want to make AfterAllTicketChanges scrip, which will work in TransactionBatch mode, and fire after all changes to the ticket was made on update off any ticket information. Now, when I change the SLA field, it changes the the Due and the priority of the ticket accordingly. The problem is that the Due and Priority change happens after my AfterAllTicketChanges scrip fires. I understand that the TransactionBatch mode scrips are commited after all TransactionCreate Scrips are done. For example: I change the status and the subject of the ticket in one update. Should the scrip in batch mode run after both of these changes are done and the transactions recorded? Or maybe I understand it wrong ant the scrip in Batch mode run after each different transaction? So technicaly should it be like this: Or like this: ? Because now I get it working like SCENARIO #1, where in step #2 and step #6, the values of Due and Priority are different, but the value of the SLA is the same (the one I changed to) in both steps. Sorry for the mess in thoughts, I am not native English speaker. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58579.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
Scenario #2 is the expected behaviour according to all scrip documentation included with RT. The SLA extension appears to be contradicting this. Therefore, I still believe that the SLA extension is at fault and that a bug report for the SLA extension should be submitted via the URL given in my previous message. When you change a ticket's subject and status in a single update, two transactions are created. A TransactionBatch scrip should run only once for both transactions. The SLA extension seems to be interfering with this expected behaviour. On 20/09/2014 12:15 am, andriusk andrius.kul...@gmail.com wrote: I would try to explain my situation again. I want to make AfterAllTicketChanges scrip, which will work in TransactionBatch mode, and fire after all changes to the ticket was made on update off any ticket information. Now, when I change the SLA field, it changes the the Due and the priority of the ticket accordingly. The problem is that the Due and Priority change happens after my AfterAllTicketChanges scrip fires. I understand that the TransactionBatch mode scrips are commited after all TransactionCreate Scrips are done. For example: I change the status and the subject of the ticket in one update. Should the scrip in batch mode run after both of these changes are done and the transactions recorded? Or maybe I understand it wrong ant the scrip in Batch mode run after each different transaction? So technicaly should it be like this: Or like this: ? Because now I get it working like SCENARIO #1, where in step #2 and step #6, the values of Due and Priority are different, but the value of the SLA is the same (the one I changed to) in both steps. Sorry for the mess in thoughts, I am not native English speaker. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58579.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
I think that the Due and Priority may be the problem. Here I changed Subject, Status, Due, Priority (SLA not changed), and still I get separate TransactionBatch run for each (Subject,Status), (Due), (Priority). The last two fires two separate Batch Scrip commits. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58581.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
Please supply a debug log covering the above updates. Is it possible that the scrip is not applied to the relevant queue in batch mode? On 20/09/2014 12:54 am, andriusk andrius.kul...@gmail.com wrote: I think that the Due and Priority may be the problem. Here I changed Subject, Status, Due, Priority (SLA not changed), and still I get separate TransactionBatch run for each (Subject,Status), (Due), (Priority). The last two fires two separate Batch Scrip commits. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58581.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
On Sat, Sep 20, 2014 at 12:44:46AM +1000, Alex Peters wrote: When you change a ticket's subject and status in a single update, two transactions are created. A TransactionBatch scrip should run only once for both transactions. The SLA extension seems to be interfering with this expected behaviour. Honestly, I found the bug report and this whole thread incredibly difficult to follow. If you'd like a developer to look into this, I suggest providing us a failing test for RT-Extension-SLA or a trivial initialdata file and config snippet that sets it up so we can see the problem you're describing. -kevin pgp3Nyv6BV2A_.pgp Description: PGP signature -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
There is only one scrip in TransactionBatch mode applied to my test Queue. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58586.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
I still suspect that the SLA extension is interfering, but without a debug log it's almost impossible to offer any further suggestions. On 20/09/2014 1:10 am, andriusk andrius.kul...@gmail.com wrote: There is only one scrip in TransactionBatch mode applied to my test Queue. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58586.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
The last two transactions is because of SLA was changed and the due and priority must be changed accordingly. How can I get my scrip run after these two last transactions, because now it is ran first (Found 1 scrips for TransactionBatch stage with applicable type(s) Status,Set,SetWatcher,CustomField). This is a real headache form me... -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58567.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
It sounds like the SLA extension is performing its work after all scrips run instead of before TransactionBatch scrips. I would be inclined to suggest that this is an SLA bug/oversight, as its current design doesn't seem to permit proper execution of TransactionBatch scrips and its documentation doesn't provide a workaround. Please consider describing this situation in a bug report so that an official response can be recorded: http://rt.cpan.org/Public/Dist/Display.html?Name=RT-Extension-SLA On 18/09/2014 8:28 pm, andriusk andrius.kul...@gmail.com wrote: The last two transactions is because of SLA was changed and the due and priority must be changed accordingly. How can I get my scrip run after these two last transactions, because now it is ran first (Found 1 scrips for TransactionBatch stage with applicable type(s) Status,Set,SetWatcher,CustomField). This is a real headache form me... -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372p58567.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training November 4 5 Los Angeles http://bestpractical.com/training -- RT Training November 4 5 Los Angeles http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
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
Re: [rt-users] Catch all ticket changes in one scrip
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 andrius.kul...@gmail.com 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
[rt-users] Catch all ticket changes in one scrip
Hello, I'm trying to figure out, how can I catch all the changes made to ticket fields in one scrip. It would be like OnUpdateTicket script, which will gather all the changes made, and sync them with DB outside trought REST. Is there any solution, or maybe code example doing all of that in RT itself (github)? I do not want a scrip to send every changed field in separate requests. Is it possible? -- View this message in context: http://requesttracker.8502.n7.nabble.com/Catch-all-ticket-changes-in-one-scrip-tp58372.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] Catch all ticket changes in one scrip
On Fri, Aug 22, 2014 at 05:49:29AM -0700, andriusk wrote: Hello, I'm trying to figure out, how can I catch all the changes made to ticket fields in one scrip. It would be like OnUpdateTicket script, which will gather all the changes made, and sync them with DB outside trought REST. Is there any solution, or maybe code example doing all of that in RT itself (github)? I do not want a scrip to send every changed field in separate requests. Is it possible? You need to use TransactionBatch mode and have your scrip run after any other change inducing scrips. Regards, Ken -- RT Training - Boston, September 9-10 http://bestpractical.com/training
