Darshana, I understand from where you are coming. I would suggest going with Norm on this one.
You might add search functionality that the users could type part of a word in, hit enter, and remedy would auto-populate (or pull up a list if multiple selections match) the field. This really helps speed up your power-users that are good with the system, and good with computers. It's easy to do, just add an active link on the menu field that runs on <Enter> and does a set field to the fields where it queries your menu form for %$field$%, and then you would bring back the request ID to the menu field, then your active link would fire next that would set the values of the other fields based off of the request id, and then set the main field. Thanks, Gary Opela, Jr., RSP Remedy Engineer Leader Communications, Inc. http://www.5pointleader.com http://www.lcibest.com Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Darshana Jivan [MTN Network Solutions] Sent: Tuesday, June 03, 2008 7:50 AM To: arslist@ARSLIST.ORG Subject: Re: Tiered Menu Thank you Shawn for your suggestion. The thinking behind it was to try to shorten the time is takes to log a request if some of the fields could automatically be set, instead of going through each field menu. Regards, Darshana From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pierson, Shawn Sent: Tuesday, June 03, 2008 2:20 PM To: arslist@ARSLIST.ORG Subject: Re: Tiered Menu ** Personally, I think it would be painful to have a menu like that to begin with. Add more items to it and try clicking around it. You'll see that it's difficult to navigate, especially when you get submenus with larger amounts of items. People will try to click something then it might disappear because they hovered over a different part or something. What I would suggest is to set up either a table field (set up as a tree) or a List Box to do this, otherwise people will not like the application. With that being said though, you probably will have to go the route you don't want to go. The way I would do it would probably be to put the menu of the "Incident" field on another field that stores the request ID of the menu item and sit this field behind the "Incident" field so they appear to be parts of the same field. In the menu, have the labels be what you are displaying ("Down", "Intermittent flapping", etc) and the actual value of the field is the Request ID. Then, when the menu selection is made, run an Active Link that sets the other fields. It's nothing elegant, but it works. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Darshana Jivan [MTN Network Solutions] Sent: Tuesday, June 03, 2008 5:02 AM To: arslist@ARSLIST.ORG Subject: Tiered Menu ** Hi, I have created a search menu with a tiered drop down and I want to set the details that the user chooses into the underlying fields. For example if the user chooses the following from the menu ->Problem ->Link ->ADSL ->Down I would like to set 'Link', 'ADSL', 'Down' into 3 different fields. How could I do this without setting the field with the tiered menu with the Request ID to get the underlying information. Please can someone assist me on this. Also see attached picture of an example. [cid:image002.jpg@01C8C550.C47DBF50] __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 hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
<<inline: image002.jpg>>