Right, but this makes the COMPANY value no longer atomic.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Friday, June 29, 2007 2:11 PM To: arslist@ARSLIST.ORG Subject: Re: Multitenancy in a Large Enterprise Yes. You will need to define each entity that should be hidden from others as a Company - that is the level where row-level locking of records occurs. Acme - Widgets - Testing and Acme - Widgets - Research must be separate Companies. In order to move tickets between companies, you need ticket transfer companies (we are using one for the entire campus) that the support group members in both organizational companies have been granted access to. There have to be public groups within that transfer company to act as way-stations for transient tickets; otherwise the support staff in a given company cannot see the other company, or any of the groups in it, or any of the tickets assigned to the other company/group (unless the Requester is public - see last line next para). Note that we are not giving ANYBODY unrestricted access, and that the ability to find and "see" a ticket does not necessarily allow you to move it around unless you take ownership of it first. Each operational company has a "public" group in the ticket transfer company for incoming tickets. Support staff in other companies have been given access to the ticket transfer company, which allows them to see (and assign to) all of the public groups in the transfer company for all of the other separate companies. The receiving company can move the ticket into their internal company group queue, and it will still be visible to the originating requester/company based on who the requester is and who the owner group is. No one outside the assigned and owner companies will see it - unless....... the ticket was opened for a Customer who is a member of a customer company that ALL operational company members have access to. If the ticket was opened for a public customer, it is NOT hidden at all - everyone with access to the customer company can see it. We are trying to do it all with no custom code (except on the back end, where we will import people from LDAP into the customer company). We have to hand-manage all of the ~25 operational companies and the 300 IT staff within them. They ALSO appear in the customer Company, but with their LDAP login name. Christopher Strauss, Ph.D. Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/helpdesk/ ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Friday, June 29, 2007 1:20 PM To: arslist@ARSLIST.ORG Subject: Multitenancy in a Large Enterprise ** Has anyone attempted to implement multitenancy in a large, complex enterprise? Suppose I have a very large company called Acme Incorporated, and let's say Acme actually consists of multiple quasi-independent subsidiaries-Widgets, Sprockets, and Gizmos. Let's say Widgets, Sprockets, and Gizmos were each independent companies that were recently acquired by Acme. So Acme's structure looks like this: Acme Widgets Sprockets Gizmos Now each subsidiary has independent business units-Research, Development, Testing, and Contracting. So now Acme looks like this: Acme Widgets Research Development Testing Contracting Sprockets Research Development Testing Contracting Gizmos Research Development Testing Contracting OK, so far, so good. Here's the rub-Acme does not want each independent business unit to be able to see the others' tickets. In other words, Widgets' Research unit cannot see tickets assigned to Widgets' Testing unit and vice versa...unless, that is, Widgets' Research unit wants to "throw the ball over the fence" to Widget's Testing. According to the ITSM documentation, multitenancy can only be effected at the company level...so my question is, can multitenancy be implemented in the way I'm describing without any code modifications? Norm __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"
