There have been a lot of interesting responses, but there have been a few areas 
that haven't been covered here that I've either built myself or with a team so 
I'll list them below.

A data-driven ARS-based survey application to tie in with a trouble ticket 
system, but was created generically enough to tie in with anything.  It rivaled 
BMC's ITSM survey application, and was completely ARS-based unlike many others 
out there.  Basically, I had a view form with a list of questions show up on a 
table field, and an attribute on each question that caused different types of 
fields to become visible for each question, so for example if the survey was 
set up with a scale of 1 - 10 type of question, a radio button with that scale 
would show up, or if it was a text question, I'd give a textbox.  It was pretty 
cool, at least I thought so.

Another was a telecom provisioning system.  Eventually, I was able to work with 
some other teams to get this really cool, so that the POS (Point Of Sale) 
system would create the record in Remedy, then Remedy (via a custom DLL I wrote 
in VB6) could interface with applications to request phone service from the 
major telecoms.  So for example, if the POS system passed an invalid address to 
me in Remedy, Remedy would use some calls to the DLL via Active Links using OLE 
to pull back potential address suggestions from the postal database, and prompt 
the technician responsible for this to select a correct address or completely 
reject the service request.

I also built a sort of dispatching applications to send trucks out to people's 
houses to work on their lines, and integrated it with mapquest so I could 
provide a view field on the form that automatically pulled in the fields for 
the customer's address and then displayed a map based on that information.  
Later, we purchased an application to display maps and generate routes based on 
the list of customers assigned to a specific representative (we had a list of 
zip codes that a technician serviced in a table to automatically assign them 
work), and I had Remedy pass the addresses to that other application, which 
then generated a route automatically.

Just to get practice, I've built a family-tree type of application that I 
haven't finished, but was mostly working.  It was sort of cumbersome due to the 
limitations of ARS, so I never finished it.  Also for practice I've built 
simple translator applications that make usage of web services.

I hope these are some good examples.  I could go into more detail on some of 
them, but a few of these were quite a while ago.  Mostly, I've built 
applications that cover what ITSM does, primarily trouble ticketing, some 
change management, and some CMDB-type functions.  Still, you can do pretty much 
anything that requires a front end and a database.  You're not going to be 
writing the next great game for the Xbox360, but you can either create or 
integrate with most business applications.

Shawn Pierson

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of sam appecherla
Sent: Friday, November 14, 2008 10:22 AM
To: [email protected]
Subject: ARS for non Trouble Ticketing applications

** Hi List,

Just curious to know..

Apart from using Remedy for HelpDesk, Trouble Ticketing and the kinds, what 
else can we do with this workflow engine for? Does anyone have a custom built 
product/application built on ARS apart from Trouble Ticketing kinds that you 
would like to share?

Regards,
SriSamSri Appecherla
Mobile# +91 991 610 6008
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

Private and confidential as detailed here: 
http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the 
link, please e-mail sender.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to