If the form's fields should have public access I would check the other fields (Submitter, Assignee, ...) and make sure they only have public (or something else) as well. In the Admin tool select Groups, then the Submitter Group. Pick the Field tab and select the form. Remove Submitter from all fields. Then without closing the popup choose the Assignee group and do the same.
We had a similar issue and found we had to remove the Submitter and Assignee groups from ALL fields on a form for the system to stop adding the extra SQL on a query. Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, October 06, 2009 2:48 PM To: [email protected] Subject: Re: Anyone had issues after patching 7.0.1 to patch 008? ** The forms do not have row level access. C1 (request ID) is set to Public on both side. The one initializing the search and the one being searched on. 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 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
