Oooo, good catch, Fred. I forgot about that. It can get pretty complex, and in most installations there aren't that many escalations to manage. Which is why most of us just do it manually.
Rick On Wed, May 13, 2009 at 7:26 AM, Grooms, Frederick W < [email protected]> wrote: > Actually since an Escalation can run against multiple forms the list of > forms (from Escal_Mapping) should really be displayed as a table. > If you are just going to show a list of the forms then you could use an SQL > Set Fields action on display > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Rick Cook > Sent: Wednesday, May 13, 2009 9:19 AM > To: [email protected] > Subject: Re: Escalation Timeline > > David, > > It's just called 'escalation' - always has been. Note that you will have > to massage/parse some data and map some bitmasks to turn those into human > readable values, etc., so it's not as simple as I might have made it sound. > But as long as the translations go both ways, it should work. > > One thing of note is that neither the form name nor schemaId are in the > escalation table. You have to map the escalation.escalationId field to the > escal_mapping.escalationId field, and then use the schemaId column in > escal_mapping to get the Form Name from arschema. That makes it tricky in > non-7.5 versions, because you'll have to do the joins in SQL. In 7.5, > you can just join the view forms. But you could probably accomplish the > same thing in any 7.x version by adding character fields to the escalations > view form for the schemaId and name, and then using workflow to pull the > data in. As is usually the case in AR System, there are multiple ways to > skin that cat. > > The tables and data appear to be named and formatted the same in all 7.x > versions, so it should migrate just fine. > > Rick > > -----Original Message----- > On Wed, May 13, 2009 at 2:58 AM, Barber, David <[email protected]> > wrote: > > I'm interested about this - what is the relevant metatable to setup a view > over? > > Ta > > Dave > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]]on Behalf Of Rick Cook > Sent: 12 May 2009 16:33 > To: [email protected] > Subject: Re: Escalation Timeline > ** That would make sense. A view form over the metatable would be a great > way of managing that data from the UT. You could set workflow against it to > change them and everything. > > I love everything about that idea except that I didn't have it a year ago. > > Rick > Sent from my Verizon Wireless BlackBerry > > -----Original Message----- > From: "Grooms, Frederick W" > Date: Tue, 12 May 2009 10:24:57 -0500 > To: <[email protected]> > Subject: Re: Escalation Timeline > I did it with a query against the Escalation table in the database. > Unfortunately it was a good while ago so I don't have the details right at > hand. > > Fred > > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Pruitt, Christopher J > Sent: Tuesday, May 12, 2009 10:18 AM > To: [email protected] > Subject: Re: Escalation Timeline > > ARInside would have been great for this, we still use it but that product > is no longer available or supported. I am hoping some new product comes > along soon. I am holding out for ARSmarts, but so far I have not seen one. > > Christopher Pruitt > Consultant Specialist > EDS, an HP Company > mailto: [email protected] > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Rick Cook > Sent: Tuesday, May 12, 2009 10:00 AM > To: [email protected] > Subject: Re: Escalation Timeline > > Unless ARSmarts, Abydos, or some other tool does that, I don't know of a > way, either. I tried to think of one last year when looking at how to > multithread the escalations, and ended up just doing it manually. > > Rick > Sent from my Verizon Wireless BlackBerry > > -----Original Message----- > From: "Schryver, Curt" > Date: Tue, 12 May 2009 10:52:33 -0400 > To: <[email protected]> > Subject: Re: Escalation Timeline > I started tinkering with something just last week to do this exact thing. > Didn't get too far, but will continue to play with it. (Unless someone > comes forward with an already-functioning application) > Curt A. Schryver > 717-810-2109 tel > [email protected] > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of O'Brien, Keith KOB. (Citco) > Sent: Tuesday, May 12, 2009 8:46 AM > To: [email protected] > Subject: Escalation Timeline > Hi, > Just wondering if there is a tool or process available to document the > timeline of all active escalations on a system. > Regards, > Keith. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:[email protected]<sponsor%[email protected]>ARSlist: > "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
