There are workflow connections between the different class values and the approval processes.
What we did to change the values was to create a new field with the values our customer wanted to use...and lay it on top of the OOTB class field. I also mapped the customers class values to the OOTB values as they were basically the exact same...they just insisted on using their values. So when a value was selected in the customers class field...it set the OOTB class field via workflow based upon the mapping. Convoluted...but it is what the customer wanted. Bruce Sent from my iPad On Oct 17, 2012, at 3:04 PM, "Hodgdon, Paul" <[email protected]> wrote: > ** > I was interested if anyone has ever changed the Class* menu in the Change > Management Console for 7.6.04. We would like to possibly hide some of the > classifications and rename Normal or Standard to something else. Is this > easily done and would it cause OOTB workflows to break? I know there have > been similar posts about changing statuses and that can be a challenge when > changing menu items. > -Paul > > <image001.png> > IT Accounts & Remedy Administration Manager > University of New Hampshire > Client Services > Primary: (603) 862-2377 > Alternate: (603) 862-4242 > [email protected] > http://accounts.unh.edu > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
