I would definitely download and install patch 007 to ITSM 7.0.03 - ON DEVELOPMENT FIRST, and make sure that it does not affect anything that you have in production, or circumvent any customizations. I came up with pages of post-patch 007 actions that I had to perform, where patch 007 had reactivated workflow that I had disabled and replaced with custom, or updated disabled workflow so that I had to carry that update into my custom objects. It also wiped out Incident Patch 9002, so I had all of that ready in a post-patch action checklist when I applied 007 to the production server. I can hardly wait to do that all again at the end of the month or in July, after patch 008 comes out.
I have had some "permission errors" on the Problem Investigation module, specifically Known Errors, but these may have been resolved by adding a global assignment rule for Problem Management. Most of these applications require a LOT of configuration, not all of it documented, before they work at all. As I said, I have yet to put my toes in the water on Change Management... it's coiled up on my server like a water moccasin, waiting to strike. BTW, I haven't heard anyone else chime in with "patch 007 to Change Management fixed my problem(s), so I don't know if any sites have applied it and seen improvement. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Bilinski, John Sent: Friday, June 13, 2008 11:47 AM To: arslist@ARSLIST.ORG Subject: Re: Question: Permission Issues with Infrastructure Change Management 7.x ** I know this much, that I am on Change Management v7.0.3. As for the patch level, that is a little tricky because I had an issue that I discovered when I tried to install the data Management Tool where the Data Management Tool installer could not find the patch level of any of my ITSM installed applications. I called Remedy Support and they were like don't worry about it and sent me a shared properties record to import into the Share Application Properties form so the installer would read patch level 6. Because of this I can't really tell you what patch I am on. Are you suggesting to download the Change management patch 7? I thought it was only on patch 6? These error are not good because I know how the Permissions structures are in Change 7 and these error just don't make sense. I will download and try to install it unless you have run into permission errors on Incident or Problem that are like this? Thanks. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of strauss Sent: Friday, June 13, 2008 12:33 PM To: arslist@ARSLIST.ORG Subject: Re: Question: Permission Issues with Infrastructure Change Management 7.x ** Just out of curiosity (I have not started the process of configuring Change Management on our system yet - was too busy getting IM, SLM, RKM, and Kinetic Request implemented, and still have PM to go), are you on patch 007 of the ITSM 7 application? Patch 007 consisted _primarily_ of fixes to Change Management, so I would not want to even attempt to configure and test it at a lower patch level. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Bilinski, John Sent: Friday, June 13, 2008 11:15 AM To: arslist@ARSLIST.ORG Subject: Question: Permission Issues with Infrastructure Change Management 7.x ** I am running into some permission issues while I am testing Change Management 7x. For example I created a user "chgmanager". This user has is in the proper support groups and has the proper functional roles as a Change Manager and Change Assignee. But when I open certain change Requests I am getting this error: "ARERR [332] You do not have write access (at create time) to field : 179 ARERR [333] You have no access to field : 7" then a second error: "ARERR [313] Data types are not appropriate for relational operation:" Field ID:7 is The Status* field but I cannot find 179. What makes me confused is that the Status* field is General Access. What gives? Also when I go to another existing Change Request to update it when I save the change it gives me this error: "ARERR [330] You do not have write access to field : Address" Here are the Permission groups my "chgmanager" user belongs to: Asset Viewer Infrastructure Change User (Fixed) Contact Location Admin Contact organization Admin Contact People User DSL Viewer AR Permissions: Floating AR User License. Access Restrictions: Unrestricted Access Has anyone seen these permission errors before? Is there a white paper on Access controls for ITSM that gives the low-down on permissions and access? Thanks. John Bilinski Operations Services Staff JCON Help Desk 202-305-3202 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
