So that DSO can be used to copy records to other Remedy servers and no have conflicting Incident IDs
On Tue, Feb 9, 2010 at 3:36 PM, Matt Worsdell <[email protected]> wrote: > FWIW I'd be taking the view that the effort does not make sufficient > business > sense. Throw in impact on upgrades and maintaining/documenting a further > customisation, it makes even less sense. > > Why do they want to add two chars? > > Matt > > > We have a request to change the Incident ID prefix on the HPD:Help Desk > > form. We are being asked to change it from INC to NOINC. Now what I am > > finding is the mess of logic behind this field that runs when searching > by > > Incident ID. By modifying the current prefix searching IDs with the > > NOINC does not work - with or without the NOINC. The only records that > can > > searched now are the old records with the INC prefix. Typing in a new ID > > fails because work flow converts the value based on old logic. > > > > The issue I see is that the system will need to be taught how to search > > using the old prefix or the new prefix but it won't know what to use if > > the > > user types in the straight numeric value without the leading INC or NOINC > > - > > which our users do. > > > > Has anybody done this and if so what direction did you take? > > > > TY > > > > Frank > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > Platinum > > Sponsor:[email protected]<sponsor%[email protected]>ARSlist: > > "Where the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:[email protected]<sponsor%[email protected]>ARSlist: > "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
