Mark, You could always put in a FILTER (note that it is a FILTER not an active link to provide full protection) to return an error if this user is ever assigned as a contact (or assignee or whatever else you want to make sure you prevent this user from being) and that provides the prevention you need for the operation you don't want to allow.
If you make this person a "support staff" person rather than a member of a company, that may go a long way to eliminating them from being in menus and other things on fields. Another thing to consider. This keeps them out of being locked into "one company" if you have a multi-tenant environment. Doug From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Roger Justice Sent: Wednesday, January 08, 2014 1:28 PM To: [email protected] Subject: Re: User account but no people record ** There are many reasons to create a service account People record. You must have a People Record to create the Incident. Remember the name can be From External System. You could then create a simple AL that will not allow an Incident to be created by a submitter that is not allowed, this will work since you will control the submitter of the Incident created from the external system. -----Original Message----- From: Brittain, Mark <[email protected]> To: arslist <[email protected]> Sent: Wed, Jan 8, 2014 3:53 pm Subject: Re: User account but no people record ** Hi Joe, If I create a People record then someone can manually create an Incident using this non-person as the contact. Does not matter which status I select on the People record, it still shows. Can’t have that. Mark From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]?>] On Behalf Of Joe D'Souza Sent: Wednesday, January 08, 2014 3:49 PM To: [email protected]<mailto:[email protected]> Subject: Re: User account but no people record ** I highly doubt you could achieve what you want to do without having to break a lot of things as to how they were designed to work out of the box. Is it possible – sure its only an issue of messing around with permissions, yada yada yada.. Is it recommended? Maybe not. I have not thought this problem out after reading your email, but there is a small chance that you might break some things with multi tenancy or something like that. The cleaner way would be to create the people record with necessary supporting records in the people permission group form.. What is it that you’ll wish to gain by not having the people record to me present? Cheers Joe ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Brittain, Mark Sent: Wednesday, January 08, 2014 3:37 PM To: [email protected]<mailto:[email protected]> Subject: User account but no people record Hi All, In ITSM 7.6.04, I am implementing a web service where an external ticket system would send a request to the Incident Interface Create form, create an Incident and turn the Incident Number back to the originating ticket system. All of that is pretty straight forward. The question I have is about setting up the user account. There won’t be any updates or queries allowed. I could set this up in the People form but don’t want this account to appear as a Company Contact. Can I just set up the account on the User form with a read only license and Incident Submitter permission? I could probably just try this but thought I would check with the group first in case there any not so obvious snags to this approach. Thanks Mark Mark Brittain Remedy Developer ITILv3 Foundation, Continual Service Improvement NaviSite, Inc. – A Time Warner Cable Company [email protected]<mailto:[email protected]> Office: 315.634.9337[cid:~WRD000.jpg] Mobile: 315.882.5360[cid:~WRD000.jpg] [cid:[email protected]] ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "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"
<<inline: ~WRD000.jpg>>
<<inline: image001.gif>>
