Re: Users - Person Information

[Candace DeCou]

** David – here are some answers for you: Should there be a record in the User form for every record in the shr:people form? (Is this a company decision?)   Not necessarily – A user record is created whenever you assign a Remedy license to someone.  This is not available to you if you are creating a People record directly from the Help Desk case.  If you are using the Configuration Manager, however, then a separate tab for licensing becomes available when you set up a People record and, if you do assign them a license, then there is workflow that pushes from SHR:People to create a User record.  So, for example, where I work, we have say 1000 People records but only about 300 User records.  This is more a function of whether the people in the system need access via a license or whether they are being set up for information purposes.  If you do workflow logging when creating a user from Configuration Manager where you have added a license you will see the push to the User form; otherwise, no license – no user record.   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?)   If you think your system is incapable of handling 2 tables with 15000 records each, then you should probably have your DBA take a look, but in general no, this shouldn’t be a problem.   David – hopefully by answering these two questions, it also answers #3 and #4 for you.  Bottom line – do your users need licenses?  If yes, then use Configuration Manager to set up the People record; if no, then use the People record available from the Help Desk case or also use Configuration Manager but don’t assign any licenses to them.   Hope this helps. J Candace DeCou           From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of David Yearsley Sent: Tuesday, November 07, 2006 8:25 AM To: arslist@ARSLIST.ORG Subject: Users - Person Information   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___ ***************************** This message contains information from Silicon Valley Bank, or from one of its affiliates, that may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify the sender immediately by telephone or by replying to this transmission. This message may include indicative rate information relating to one or more products offered through Silicon Valley Bank, or affiliated broker-dealer, SVB Securities. Rates and yields shown are provided for informational purposes only, are not guaranteed, and are subject to market conditions and availability. Nothing in this communication shall constitute a solicitation or recommendation to buy or sell a particular security. Columbia Cash Reserves, Columbia Treasury Reserves, Columbia Institutional Cash Reserves, SVB Securities Liquid Reserves, SVB Securities Institutional Liquid Reserves and SVB Securities Horizon Shares are offered through SVB Securities, a registered broker- dealer and non-bank affiliate of Silicon Valley Bank. Investments in these products require the involvement of a licensed representative of SVB Securities. Investment products offered through SVB Securities are not insured by the FDIC or any other Federal Government Agency, are not deposits of or guaranteed by Silicon Valley Bank or its affiliates, and may lose value. __20060125_______________________This posting was submitted with HTML in it___