Thanks, I ended up creating ROs for each of the applications that had a template that placed them each into the appropriate Incident Classification. :-) Danny Date: Tue, 5 Nov 2013 00:09:48 +0100 Subject: Re: [servman] limit drop down options in incident From: [email protected] To: [email protected]
Well...I had a similar requirement on a project that I followed some months ago.Basically, we:1) created a lot of ROs for each desired limited set of the IR classification2) represented such limited set by a simple list, hardcoded into each Request Offering 3) mapped the user choice into an unused IR field (for example: alternate contact method), because we didn't want to extend the incident class3) used Orchestrator to execute a Runbook Automated Activity (RAA) inserted into the applied incident template The RAA and, so, the Runbook simply reads the value of the alternate contact method field and writes it as the IR classification Of course, the simple list elements values must match with the ones that you defined into the IR Classification List Hope this helps :) 2013/11/4 Daniel Ruiz <[email protected]> I was trying to figure out a way to have users select a limited sub select from the Incident Classification drop down list so that if they went to the portal to submit an application incident they could chose from a list of software application that are in the Incident Classification drop down instead of seeing the entire list of classifications. I tried configuring a Query in the Request Offering and limiting it to just Software list but that's not working out. Has anyone done this or worked around an issue like this? Thanks, Danny
