Whoa. After seeing that last email in print it appears that I am disparaging Axton. Nothing could be further from the truth. I was trying to be a "Dr. Jerry Hathaway" ( "That was yesterday, what did you do for me today?") Sorry if it sounded dismissive.
John J. Reiser Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Reiser, John J Sent: Wednesday, March 14, 2007 5:24 PM To: [email protected] Subject: Re: Restrict a join record to the $USER$ Axton, You're the best. (Today anyway ;) I tried other fields and couldn't set their permissions so I didn't even attempt that on Field ID 1. That did it. Of course now I get to abandon my slick Table control panel addition that holds the survey reviewer list and opens the join using the selected table entry AL Buoyant Solutions' table walking tutorials. Thanks again. John J. Reiser Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Wednesday, March 14, 2007 5:11 PM To: [email protected] Subject: Re: Restrict a join record to the $USER$ Ah, but you can set the permissions on the eid of the join (the one that contains the two eid's separated by a pipe). So long as you bring in the fieldid (2 or 4) from the form that contains the value you want to use for access, you are golden. Axton On 3/14/07, Reiser, John J <[EMAIL PROTECTED]> wrote: > Thank Axton, > Gave me some food for thought. > > The eid of the joins, however, takes the permissions of the underlying > Request IDs so if the Survey RequestID has Public so does the join. > > Maybe I'll just give them a DO form with a menu that performs "Get my > Open Surveys" And hook it with the Assigned To field of the Reviewer > portion of the join. > Thanks again, > > > > John J. Reiser > Software Development Analyst > Remedy Administrator/Developer > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - > paraphrased by me > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Axton > Sent: Tuesday, March 13, 2007 8:26 PM > To: [email protected] > Subject: Re: Restrict a join record to the $USER$ > > A couple of things for public to be able to view the data in the join > (as I understand it): > - both forms must have Public permission (visible or hidden) > - the entryid on both forms must have public or submitter (if the > submitter is the person completing the survey) > - if you want to restrict access on the join, then make sure either > fieldid 4 or 2 matches the person completing the survey, then assign > that as a permission group to the request id field > - for your managers to view records in the join, make sure the join > eid has the 'manager' permission group > > Axton > > On 3/13/07, Reiser, John J <[EMAIL PROTECTED]> wrote: > > Hello Listers, > > > > ARS 6.3 Patch 21 > > SQL Server 2000 > > Windows 2000 SP4 > > > > I am trying to restrict the records in a join form by only allowing > > the $USER$ to access records marked for the current account. > > > > Is this a variation of row-level locking? > > > > The Join is the "survey" form and the "reviewer" form. Many > > reviewers will see a particular survey when assigned to them. Will > > the access permissions on the Reviewer form affect the records seen in the join? > > I have created the join on the survey's Request ID to a > > SurveyRequestID field on the reviewer form. > > The reviewer form gets a new record for each survey/username to be > > reviewed. The Helpdesk Supervisor creates the record when she wants > > to > > > send completed surveys to the Tier 2 person and/or their manager for > > review (atta-boys or tsk-tsk's). > > > > The primary audience are the managers. The receive a MidTier link > > and when they log in we want then to see Surveys for their people, > > that > are > > newly received. But they may also want to see an old survey, so we > > will provide a state field for them to select previous records > > already > > > "reviewed". > > > > I hope there is enough info here to make this understood. > > > > Thanks in advance. > > > > > > John J. Reiser > > Software Development Analyst > > Remedy Administrator/Developer > > Lockheed Martin - MS2 > > The star that burns twice as bright burns half as long. > > Pay close attention and be illuminated by its brilliance. - > > paraphrased by me > > > > > > ____________________________________________________________________ > > __ _________ UNSUBSCRIBE or access ARSlist Archives at > > www.arslist.org ARSlist:"Where the Answers Are" > > > > ______________________________________________________________________ > __ > _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
