What of notification actions that use the user default notification mechanism based on the login name? This may present notification issues if a person is not in the user form. The email engine does not (by default) cross reference any form other than the User form.
Axton Grams On 11/7/06, Rick Cook <[EMAIL PROTECTED]> wrote:
** David, Basic difference is that if the user will log on to Remedy for anything, they need a login/pw, which means a User record. If they will only call the Help Desk, they only need a people record for reporting and convenience purposes. One would generally not want to have all of one's people in the User form, as performance can be an issue. Rick On 11/7/06, David Yearsley <[EMAIL PROTECTED]> wrote: > ** > > ITSM 6.0 > ARServer 6.00.03 > > We are in the process of expanding our use of Remedy ITSM suite and have several questions. If you add someone from the "Configuration Manager" there is a record created in both the user and shr:people form. If you add someone from a helpdesk ticket the only record created is in the shr:people form. (Unless something we changed is preventing the user record creation.) We have researched the questions below and have conflicting viewpoints. We just want to find a general idea of how other organizations are handling this issue. > > Questions: > > 1. Should there be a record in the User form for every record in the shr:people form? (Is this a company decision?) > > > 2. If we decide to have all shr:people information in the user are there any issues? (Is this a performance problem - We have 15000 people?) > > > 3. If a User Record should be created from when a person is added from a Help Desk ticket, does anyone know what programming creates the user record? (Ours could be missing. I have been checking the logs and cannot find any programming that would create a user record.) > > > 4. Is there a best practices for determining who should be in the User form and the People form?__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
