Another thing you can do to get away from using public is setup a companies like Global Support, Region 1 Support, West Coast Support. Add these permission to field 112 of your company records. You would then assign certain people to those regional support groups. This would help you from using the Public setting and give you the desired menu options you are looking for. You could then setup workflow to manage this.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Andrew C Goodall Sent: Thursday, July 28, 2011 2:44 PM To: [email protected] Subject: ITSM multi tenancy - customer company vs operating company needs ** ITSM 7.5.01 We are a fairly large enterprise and use multi-tenancy to control access to multiple operating companies' data. So we do not give any one unrestricted access to control access to the different operating companies. However, our associates from both companies - particularly our central Service Desk work with multiple customer companies and have to open incidents for those customers. BMC support is telling us that we would have to add all those hundreds of customer companies to every ones access restrictions for that company to show up on the customer selection. In our current environment, I have a workaround where we add public to those customer company records - but this is not sustainable long term. I was hoping this would have changed in 7.6.04 but it does not, so all I can do is open an RFC L Does anyone else have this issue with the inflexibility of access restrictions between different company types, i.e. needing operating companies separate but customer companies open and public? Does anyone else recommend a solution? I'm currently adding public manually. But I'm thinking of adding a filter to push this on submission of Customer Type Company. Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com <http://www.jcp.com/> | The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
