Not really.. You do not need to modify existing OTB code. But add a little utility to create this information.
You can design a self registration process, that uses some sort of a unique key to register such as maybe a billing account number or something like that so that for a particular managed service, a customer cannot create more than 1 account unless off course you want to give them that ability. And in the self registration process, you need to create a couple of filters, one that pushes into people form, and the other into people permissions group form, to give them the permissions they require to use SRM. Its as simple as that. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of SUBSCRIBE ARSLIST theReel Sent: Monday, January 20, 2014 6:25 AM To: arslist@ARSLIST.ORG Subject: Re: Why do service requests require a Login ID? Thanks for the reply Jason, I probably should have mentioned that I work for a Managed Services company so not all our customers would have access to SRM and we would get new users calling us every day - so we can't link to AD or anything like that to ensure everyone already has an account. So it may be a case that we will have to modify the create Person workflow so that it also creates a Login ID for each new user. That brings it own issues - of trying to assign the correct permissions etc. 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"
