I know it's supposed to be configurable, as you indicate. My question is, has anyone done it? And does doing it break anything? I understand that if it's configurable you would expect that it *shouldn't* break anything, but the key word is "shouldn't."
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Monday, November 05, 2007 1:40 PM To: arslist@ARSLIST.ORG Subject: Re: Changing Request ID Prefix in Incident (UNCLASSIFIED) Make sure that you have checked out the Incident Number generation processes (HPD:INC:GIN_ workflow) that are called from both the HPD:Help Desk form and the HPD:IncidentInterface_Create form. The latter is used by all integrations to include Incident creation by the CAI Plugin for the Requester Console/SRM. I would expect that the prefix is actually set there, at the time of generation. Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://itsm.unt.edu/ > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of FRANK, GORDON CTR DISA JSSC > Sent: Monday, November 05, 2007 1:21 PM > To: arslist@ARSLIST.ORG > Subject: Re: Changing Request ID Prefix in Incident (UNCLASSIFIED) > > Classification: UNCLASSIFIED > Caveats: NONE > > A quick scan of a 7.1 .def file tells me that "INC" only > occurs on the form, so it may be that it doesn't affect > workflow. This would make sense I think. BMC Remedy will > still keep it in the next release, so note it as a customized > enhancement. > > Gordon M. Frank > DISA\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 1:12 PM > To: arslist@ARSLIST.ORG > Subject: Re: Changing Request ID Prefix in Incident (UNCLASSIFIED) > > Well that's really what I'm asking. Does changing the three > letter prefix break ITSM? > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of FRANK, GORDON CTR DISA JSSC > Sent: Monday, November 05, 2007 11:39 AM > To: arslist@ARSLIST.ORG > Subject: Re: Changing Request ID Prefix in Incident (UNCLASSIFIED) > > 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" > > ______________________________________________________________ > __________ > _______ > 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" > > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
