How do you handle the employee base & location base? Do you have to duplicate these data sets?
________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Roger Justice Sent: Friday, April 09, 2010 2:25 PM To: [email protected] Subject: Re: Segregating HR & IS/IT data ** Multi-tenancy is the easiest way. You could create new Supprt Groups the HR use field 112 to limit who can see the record and review the workflow that will allow a group member the see the entry. You will have the insure on these records that the unrestricted group is not one of the entries in field 112. -----Original Message----- From: Pargeter, Christie :CO IS <[email protected]> To: [email protected] Sent: Fri, Apr 9, 2010 4:10 pm Subject: Segregating HR & IS/IT data ** We are looking at adding our HR Help Desk to using ITSM on the same server. But we wanted to keep the incident & change tickets segregated. But we don't really want to do multi-tendency if we don't have to. The 2 desks have the same employee & location bases we just don't want them to see each other's tickets. How have other companies handled this? ARS 7.1 p 6 ITSM 7.0.3 p 9 Window 2003 MS SQ 2005 IIS/Tomcat RKM 7.2 p 2 MidTier 7.1 p 6 ________________________________ Christie Pargeter Legacy Health IS - Programming SR Technical Analyst [email protected] 1120 Building tel: 503-415-5149 _attend WWRUG10 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
