something inherently wrong with new / existing Requesters
When a requester is not recognized the service application will by default add them to the requesters list. Good? not so sure.
Editing the requester in admin does not really mean anything as if the display no longer matches, another entry is created for the user.
I just tested this send an email, service desk adds it, I change the display name, send another. Service desk creates another.
What I'm asking is why the application goes by display rather than email address. Would this not cut down on populating double entries. It's idiocy to try and clean this up. I've use this for only a week and my clean setup has already turned into something irritable.
Or maybe I'm not looking at the settings correctly?
Editing the requester in admin does not really mean anything as if the display no longer matches, another entry is created for the user.
I just tested this send an email, service desk adds it, I change the display name, send another. Service desk creates another.
What I'm asking is why the application goes by display rather than email address. Would this not cut down on populating double entries. It's idiocy to try and clean this up. I've use this for only a week and my clean setup has already turned into something irritable.
Or maybe I'm not looking at the settings correctly?