I did the bug tracking thing as a learning exercise, but the first full thing I built was a purchasing front end for AM 5.0 - before it had one. Substantially similar to the structure AM uses now, though not as complex. Or as large.
Rick Cook On Wed, Nov 12, 2014 at 10:07 AM, Rick Westbrock <[email protected]> wrote: > ** > > I built an asset tracking module for the Expense Management department > because they were tracking cell phones and pagers (yes, it was that long > ago) in spreadsheets. I built in all kinds of logic to remind them when a > contract or warranty date was coming up etc. This was back when only the IT > department used the fat client so I had to build it for the web but at that > time you had to manually build separate web views for all the forms. In the > end after all that effort they ended up not using it after all. > > > > I actually ended up making that extensible to cover everything from > company cars to company credit cards and so forth to make it available to > the other non-IT teams who needed to track lots of assets but again they > ended up not using it. It sure was a good exercise though. > > > > > > -Rick > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Jason Miller > *Sent:* Wednesday, November 12, 2014 9:28 AM > *To:* [email protected] > *Subject:* OT: What was the first ARS app you built? > > > > ** > > I thought I would start a side topic from the "how fast could that be?" > thread. We have seen more and more "out of the box ITSM" installs in > recent years and custom development appears to be less prevalent. Many of > us started out building anything and everything under the sun. > > > > For me, I had just switch from working in an aerospace fabrication shop to > my first IT job at a help desk. About 6 months in I became very interested > in what else Remedy could do. As I learned more about what Remedy could do > I really wished we would of had it at the job I had left. > > > > So with that my first app was one geared around running a fab shop. The > app tracked customers, jobs/parts, equipment and staff. It could associate > what machine a part is in and who is working on it. Also it could show the > status of a machine so planners didn't schedule a job in a machine that was > down for maintenance. Also you could not schedule machinists to a job if > they were on vacation. > > > > It probably also had things like an email to the worker when a job/part > was assigned to them. I have been trying to find the definition in recent > years. I am sure I would get a kick out of how I built things back then. > > > > Jason > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
