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___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
