Re: [rt-users] REST API, AUTOMATION and Recipes.
Keith, Cris, thank you for sharing. Cris, I'm going to look into that wiki of yours. To share with both of you, I just finished writing a combination of bash scripts, combined with an Open Source VOIP switch (Asterisk) and am able to create tickets ON THE FLY, real time, with caller id name and number, inserted into the ticket, with a unique identifier for call recordings for an active on-going call. This is more of a hobby / learning exercise. Its very much at its primitive stages but very functional. Since its barely 3-4 days since I started with RT, I'm documenting all the steps and questions that I'm coming up with. Perhaps that doc will help with future learning of enthusiasts. Hopefully more people will share what they are doing with the REST API, as it gives us all more perspective of what can be done and what people doing in real life. Thanks! Reza. Reza wrote on 10/26/2016 3:17 AM: /*Greetings Community:*/ Past 3:00 AM EST here in Toronto and this learning exercise is just too darn addictive! I've already been digging deep inside the API documentations of RT, to be more specific the REST API. The contributors and developers of RT are simply pure ingenious. The REST API is allowing any Joe like me to come up with a beautifully designed web interface and communicate with RT to do almost anything (if not all). I've already started writing code to integrate with bash scripts, php, simple CURL, etc., as the initial input by web-form, or telephone touch pad. I'm only beginning to imagine the potential of a phone system integration of a call centre into RT. Most of us here are systems admins, system analysts and coders. Just curious... how many of you folks here in this community have actually written your own apps to integrate with RT via the REST API? Thanks! Reza. [Superbly pumped to learn more. Cheers!] - RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training * Boston - October 24-26 * Los Angeles - Q1 2017
Re: [rt-users] REST API, AUTOMATION and Recipes.
Hi Reza, I have written a little open source Windows application that sits in the system tray and notifies you when a new ticket arrives or when someone reopens one of your closed tickets. It is communicating with RT through the REST APIs. You can find it here, if you're curious: https://app.assembla.com/spaces/rtcheckerv2/wiki It still has a couple bugs, but we're all using it here in production. Cris Il mercoledì 26 ottobre 2016 alle 03:17:05 CEST, Reza ha scritto: Greetings Community: Past 3:00 AM EST here in Toronto and this learning exercise is just too darn addictive! I've already been digging deep inside the API documentations of RT, to be more specific the REST API. The contributors and developers of RT are simply pure ingenious. The REST API is allowing any Joe like me to come up with a beautifully designed web interface and communicate with RT to do almost anything (if not all). I've already started writing code to integrate with bash scripts, php, simple CURL, etc., as the initial input by web-form, or telephone touch pad. I'm only beginning to imagine the potential of a phone system integration of a call centre into RT. Most of us here are systems admins, system analysts and coders. Just curious... how many of you folks here in this community have actually written your own apps to integrate with RT via the REST API? Thanks! Reza. [Superbly pumped to learn more. Cheers!] - RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training * Boston - October 24-26 * Los Angeles - Q1 2017
Re: [rt-users] REST API, AUTOMATION and Recipes.
Hi Reza. Nothing all that complicated but I did write an interface using Angular that compiles some statistical information on RT tickets and children. It creates a nice report on the progress toward milestones. Things like estimated time, time worked, time remaining, percent complete, and a color-coded status. It gives totals for each “epic” and a total for all work in progress, work completed, and work that has not yet begun. I’m sure I could do a lot more but coding all this really isn’t “my job” and so time is limited. Good luck. Keith Keith Creasy, Programmer and Technical Lead American Printing House f/t Blind Phone: 502.895.2405 Skype: keith537 From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Reza Sent: Wednesday, October 26, 2016 3:17 AM To: rt-users Subject: [rt-users] REST API, AUTOMATION and Recipes. Greetings Community: Past 3:00 AM EST here in Toronto and this learning exercise is just too darn addictive! I've already been digging deep inside the API documentations of RT, to be more specific the REST API. The contributors and developers of RT are simply pure ingenious. The REST API is allowing any Joe like me to come up with a beautifully designed web interface and communicate with RT to do almost anything (if not all). I've already started writing code to integrate with bash scripts, php, simple CURL, etc., as the initial input by web-form, or telephone touch pad. I'm only beginning to imagine the potential of a phone system integration of a call centre into RT. Most of us here are systems admins, system analysts and coders. Just curious... how many of you folks here in this community have actually written your own apps to integrate with RT via the REST API? Thanks! Reza. [Superbly pumped to learn more. Cheers!] - RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training * Boston - October 24-26 * Los Angeles - Q1 2017
