no kidding! Have to look into all 3 production servers and the QAs and Devs! Now I know what I will be doing for the next few days :o(
Thank you, Pascale Boyer Remedy Developer Daimler Trucks North America MP9 Portland, OR 503-745-6569 [email protected] Sent by: [email protected] 10/06/2009 01:01 PM Please respond to [email protected] To [email protected] cc Subject Re: Resolved: Anyone had issues after patching 7.0.1 to patch 008? ** Took me better part of a day to figure it out when we came up against it after the patch came out....ended up going through our system and updating the permissions on TONS of forms :) From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, October 06, 2009 1:56 PM To: [email protected] Subject: Resolved: Anyone had issues after patching 7.0.1 to patch 008? ** You are a genius!!!! I did not checked the other fields, it was on the status field, one of the searched on field. Thank you so very much, Pascale Boyer Remedy Developer Daimler Trucks North America MP9 Portland, OR 503-745-6569 [email protected] Sent by: [email protected] 10/06/2009 12:45 PM Please respond to [email protected] To [email protected] cc Subject Re: Anyone had issues after patching 7.0.1 to patch 008? ** Ah, yes...I think I saw this in 7.1 Patch 5 or 6....but they finally figured out that they weren't enforcing row level permissions in some situations. If you look on the form that's having the search performed on it you will likely find that the only people that have access to field 1 are submitter and assignee....add public to that and you will find the extra where clause pulled off....basically...before that patch they weren't ensuring that the person querying the records had access to them....they fixed it.... From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, October 06, 2009 1:37 PM To: [email protected] Subject: Anyone had issues after patching 7.0.1 to patch 008? ** Hi all, We patched our server, email engine and midtier to patch 008 last Saturday. Ever since, some of our Set Fields actions and menu aren't working properly. The SQL being sent to the DB by the system is adding this to the where clause: Where ((c2 = $USER$ OR c4 = $USER$)) AND ....... We did not add this, Remedy is being kind enough to do it on its own. Now of course this is creating major issues and breaking many workflow. We have BMC trying to figure this out, but I was wondering if any of you ever seen this? If we replace the workflow with direct SQL, the problem disappear. ARS 7.01 now unfortunalty on patch 008 MSSQL 2005 OS:Win 2003 100% home grown apps Thank you, Pascale Boyer Remedy Developer Daimler Trucks North America MP9 Portland, OR 503-745-6569 If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
