That seemed the most obvious solution - I just wondered if anyone had done it and had success, i.e., not found serious flaws in it where it would break something else.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Feliciano, Ferdinand, A (Rocky) Sent: Tuesday, May 13, 2008 3:27 PM To: arslist@ARSLIST.ORG Subject: Re: Field 112 control in ITSM 7 Create a workflow on modify that will set the value of field 112 to $group1$ + $group2$ + $group3$. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Tuesday, May 13, 2008 1:19 PM To: arslist@ARSLIST.ORG Subject: Field 112 control in ITSM 7 It has become evident that the ITSM 7 application does not, in fact, implement multi-tenancy properly, only a faint shadow of it. We had been led to believe in all of our discussions with engineers at two different UserWorlds (and had not been able to disprove it in testing) that the permissions of an Incident would be modified to reflect the customer, current owner, and current assigned group throughout the life cycle of the request. This is not, in fact, what is taking place, OOTB, at least not once you have patched through 007. The only permissions being posted to the incident are those of the customer - one group id in field 112. Has anyone had to supplement the ITSM 7 application with workflow that dynamically and explicitly adds group information to field 112 for the assigned support group and the owner group, and removes it as the incident changes assignment/ownership? If not, I guess I will be inventing it from scratch - this HAS to work. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" NOTICE: This e-mail (and any attachments) may contain PRIVILEGED OR CONFIDENTIAL information and is intended only for the use of the specific individual(s) to whom it is addressed. It may contain information that is privileged and confidential under state and federal law. This information may be used or disclosed only in accordance with law, and you may be subject to penalties under law for improper use or further disclosure of the information in this e-mail and its attachments. If you have received this e-mail in error, please immediately notify the person named above by reply e-mail, and then delete the original e-mail. Thank you. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
