All, ARS & ITSM 8.1 Windows 2008 SP2 Oracle 11 Multi-Tenancy by Operating Company; all share a single Customer Company
The customer wants NO people records created by support staff. Our People Records (CTM:People) are created and updated using ARDBC, Vendor Form and Escalations to normalize the data. If there is no People Record, techs are to check Active Directory and check to see why a Remedy record is not available. AD is updated, which updates Remedy. I have set the permission group for Support Staff to Foundation > Contact People User as this is the minimum to allow Support Staff to be able to relate CIs to records. But this permission group also gives Support Staff the capability to add new People Records. Any ideas how to stop new People Records? In particular, from the Incident form if a tech cannot find the record when submitting a new ticket. My work around is to query for new People records and delete them - this doesn't stop the records from being created. Thank you, Sandra Hennigan Remedy Developer _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
