I don't have the answer to your question however we moved from only IT and certain business users having User records (our older system) to all employees and affiliates having User records so SRM can be used by everybody. To us it just made sense that we want them authenticated so we added them. This solves issues we have always have had with trying to work with unauthenticated users (having to ask them their username, employee ID, etc.).
Jason On Fri, Jan 17, 2014 at 9:12 AM, SUBSCRIBE ARSLIST theReel <[email protected] > wrote: > Hi Guys, > > We have a customer who has a few managers that use the SRM Request portal > to submit/view requests and also view tickets raised by other users via the > Busniess manager console. > > Not all of this customers users have login Ids for Remedy. 90% submit > calls via phone and only a select few access Remedy via the SRM portal. So > 90% have people profiles but no User profile/Login ID. > > When the "Create Service Request on Submit" rule is enabled and an > Incident/Change is created for a person that does not have a Login ID you > get the warning > "Login ID is missing for the registered user. An incident will be created > but the request will not be created because Login ID is required. (ARWARN > 45459) " > > Question is: why does the Service Request need a Login ID? Surely any > relationship to a person should be done via the People ID. Has anyone came > accross this before or have any solutons? > > Thanks > Tony > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
