We thought about that approach - imposing an artificial hierarchy over the companies, which all sit at an equal level, but have not elected to do it (we think it will slow users of the interface down if they already know who all of the companies are, unless we use a custom pull-right hierarchical menu to access the data). The bottom line is that row-level locking is located at the Company level. Any need to move it to the Organization or Department level would require a fundamental change to the ITSM 7 application.
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 Pierson, Shawn Sent: Friday, June 29, 2007 2:19 PM To: arslist@ARSLIST.ORG Subject: Re: Multitenancy in a Large Enterprise ** When you go into a company's configuration, on the Advanced tab you can set up multiple tiers for the companies, although I'm not sure what that does. If you have ITSM 7 installed, go to the Application Administration Console, select one of the companies you created, and click "View". Look at the Advanced Configuration tab, and try seeing what the Multi-tiered Menu Structure does. You might be able to use it to group the individual companies below into what appears to be one organization though that, but since I've never tried it I don't know how useful it would be. If that is sufficient, you could create the 12 companies like below and then combine them in the Menu Structure Tier 1. -----Original Message----- 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 2:13 PM To: arslist@ARSLIST.ORG Subject: Re: Multitenancy in a Large Enterprise ** That would make the value no longer atomic. That's not acceptable per my requirement. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Payne, George Sent: Friday, June 29, 2007 1:48 PM To: arslist@ARSLIST.ORG Subject: Re: Multitenancy in a Large Enterprise Ok...maybe I'm being a little too simplistic here, but why don't you just set up the following 12 "companies": Widgets Research Widgets Development Widgets Testing Widgets Contracting Sprockets Research Sprockets Development Sprockets Testing Sprockets Contracting Gizmos Research Gizmos Development Gizmos Testing Gizmos Contracting This should keep you from custom coding. Gp George Payne Assistant Director, User Services Information Technology Services University of Texas at Austin 512.232.7513 _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Friday, June 29, 2007 1:32 PM To: arslist@ARSLIST.ORG Subject: Re: Multitenancy in a Large Enterprise There is no way to do this without custom coding. However, it can be done. We are currently doing this exact thing for a customer utilizing dynamic groups. We are doing it a level above where you are asking for it but there is no reason it couldn't be done further down the tree. _____ 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___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ The information in this e-mail, and any files transmitted with it, is intended for the exclusive use of the recipient(s) to which it is addressed and may contain confidential, proprietary or privileged information. If you are not an intended recipient, you have received this transmission in error and any use, review, dissemination, distribution, printing or copying of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of the erroneous transmission by reply e-mail, immediately delete this e-mail and all electronic copies of it from your system and destroy any hard copies of it that you may have made. Thank you. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"