One way we do is by using the relationship. We relate ci against each incidents or changes and this way we keep track
Regards On 22 Jan 2014 03:49, "Ray Palla" <ray.pa...@insona.com> wrote: > ** > > Yup... that sounds right to me. Consider a filtering mechanism triggered by > your lookup escalation or filter. With the mechanism you could do all > sorts of tasks like: parse the fields (Short Desc and Details), count the > number of asset numbers, and then iterate through the count to grab each > one individually. Remember you can set filters to be asynchronous and not > use phasing, allowing you to control the order they run in. You could have > a handful of filters that capture a variety of issues, possibilities or > concerns. Within that architecture you would be able to add another > requirement later if it came up. > > > > Kool beans. > > r > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Morrison, David A. > *Sent:* Tuesday, January 21, 2014 3:37 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Workflow ideas > > > > ** > > I think the idea that multiple asset numbers could be in the Short Desc or > Details could get involved. But if the LIKE %*asset number*% comparison > would pick any of them up it should work ok. > > > > David > > > > *From:* Action Request System discussion list(ARSList) [ > mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] *On Behalf Of *Ray Palla > *Sent:* Tuesday, January 21, 2014 4:33 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Workflow ideas > > > > ** > > Drew is well thought out on this one, but I have one question about the > 'first part'... What is the sticky part? Wouldn't a one-time escalation > handle this for you? Then as assets are added a filter could do the > look-up. > > > > r > > > > > > *From:* Action Request System discussion list(ARSList) [ > mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] *On Behalf Of *Morrison, > David A. > *Sent:* Tuesday, January 21, 2014 3:20 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Workflow ideas > > > > ** > > Thanks for the response. This is the way I was leaning toward myself, and > as you said the multiple assets at one time could get sticky. > > > > David Morrison > > ETSU > > > > *From:* Action Request System discussion list(ARSList) [ > mailto:arslist@ARSLIST.ORG <arslist@ARSLIST.ORG>] *On Behalf Of *Drew > Shuller > *Sent:* Tuesday, January 21, 2014 3:29 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Workflow ideas > > > > ** Hi David. You'll need a new form that will include the asset number and > a field for warranty end date. Load your assets into that, and do a real > time lookup from your HD form against the new form. That will tell you if > the asset is in warranty. For reporting, do a join, either with a Remedy > join form or a db join with a Remedy View form. > > The first part can be done with multiple assets at one time, but that's > out of my reach. > > Drew Shuller > SCAB > Honduras > > -- > Sent from MetroMail using my Nokia 920 > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _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"
