All I want to do is add an entry in the ticket history that contains the return information from the call to the web service. I have the information logged to the log file, but I also want an entry record in the history of the ticket. So no action something very simple.
I know when a custom fields are changed or updated this information shows up in the history of the ticket. With the web service call a message is received but a custom field is not needed for the information, just would like an entry in the history of the ticket of the message from web service call.
I hear what you are saying. I don’t know off the top of my head how to
accomplish it.
So you have:
Email → RT → Scrip gets triggered → Web service call is made
All I want to do is add an entry in the ticket history that contains the return information from the call to the web service. I have the information logged to the log file, but I also want an entry record in the history of the ticket. So no action something very simple.
I know when a custom fields are changed or updated this information shows up in the history of the ticket. With the web service call a message is received but a custom field is not needed for the information, just would like an entry in the history of the ticket of the message from web service call.
Thanks
Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726 Ext. 2296 • 262-783-6261 Ext. 2296 bbaker@copesan.com
Yes that is what I am doing I hoping for some kind of call like “$RT::Logger->debug” for logging. But I have not found anything. The web service call is actually being executed from inside custom home built actions.
Thanks Matt come up with any ideas it would be greatly appreciated.
Thanks
Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726 Ext. 2296 • 262-783-6261 Ext. 2296 bbaker@copesan.com
All I want to do is add an entry in the ticket history that contains the return information from the call to the web service. I have the information logged to the log file, but I also want an entry record in the history of the ticket. So no action something very simple.
I know when a custom fields are changed or updated this information shows up in the history of the ticket. With the web service call a message is received but a custom field is not needed for the information, just would like an entry in the history of the ticket of the message from web service call.
I hear what you are saying. I don’t know off the top of my head how to accomplish it.
So you have:
Email → RT → Scrip gets triggered → Web service call is made
Yes that is what I am doing I hoping for some kind of call like “$RT::Logger->debug” for logging. But I have not found anything. The web service call is actually being executed from inside custom home built actions.
That would work. Or:
RT->Logger->debug(‘a line of debug’);
Regarding creating a txn for the ticket history: I may have at one
time created a txn and added it to the history, but I’m not seeing any
code examples in my extensions. I don’t quite remember how and don’t
have time to dig into the RT upstream code.
You could create a custom field called Web Services and set that CF to
whatever value your web services returns. That is pretty easy.
Yes I thought of the custom field and that would be easy, but I have so many now. I just didn’t want to add another. But if I can’t find anything else that is what I will do eventually.
I’m sure there is a way to add a txn - apparently I’ve never done it
and would have to research (which I have no time for.)
Yes I thought of the custom field and that would be easy, but I have so many now. I just didn’t want to add another. But if I can’t find anything else that is what I will do eventually.
Thanks
Bryon Baker
Network Operations Manager
Copesan - Specialists in Pest Solutions
800-267-3726 Ext. 2296 • 262-783-6261 Ext. 2296 bbaker@copesan.com
Yes that is what I am doing I hoping for some kind of call like “$RT::Logger->debug” for logging. But I have not found anything. The web service call is actually being executed from inside custom home built actions.
That would work. Or:
RT->Logger->debug(‘a line of debug’);
Regarding creating a txn for the ticket history: I may have at one time created a txn and added it to the history, but I’m not seeing any code examples in my extensions. I don’t quite remember how and don’t have time to dig into the RT upstream code.
You could create a custom field called Web Services and set that CF to whatever value your web services returns. That is pretty easy.
Yes I thought of the custom field and that would be easy, but I have so many now. I just didn’t want to add another. But if I can’t find anything else that is what I will do eventually.
I’m sure there is a way to add a txn - apparently I’ve never done it and would have to research (which I have no time for.)