Classification: UNCLASSIFIED Caveats: NONE The only issue I see it that it may break out-of-the-box. I've never researched it, but there may be workflow oriented toward the first three characters of the Request ID. Even so, when ITSM 8.x or any future releases come out you may have to add this change to your list of out-of-the-box changes because I'm sure the new release will reset it. Make sure you start keeping these lists because they will save you headaches down the road.
Gordon M. Frank Remedy Skilled Professional Verizon FNS -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Monday, November 05, 2007 11:46 AM To: arslist@ARSLIST.ORG Subject: Changing Request ID Prefix in Incident Hi all: I asked this last week but got only one reply. I'm thinking that most folks were at the RUG, so maybe that's why I got no replies, so I'm posting again. I know that you can allegedly change the prefix of an incident Request ID from "INC" to something else. Has anyone done this successfully? Does it have any ramifications on the functionality of the system as a whole? Can you have multiple prefixes for incidents? For example, suppose you have three sites: Site 1, Site 2, and Site 3. You want tickets for Site 1 to have a prefix of ST1, Site 2 to be ST2, and Site 3 to be ST3. Is this possible? Any issues with it? Thanks, Norm ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" Classification: UNCLASSIFIED Caveats: NONE _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"