Re: On-the-fly permissions in Attachment field
>From the client you can tab to the attachment field and then use SHIFT+F10 to access the menu and use the arrow keys to Add, Delete, Display, Save to Disk and View. In the Mid-Tier the they are regular buttons and you can just tab right to them. On a side note I just tried to put a box over an attachment field and could not. I didn't have the option to Bring to Front when I had the box behind the attachment field. I even tried to trick it by placing the box over a character field and the attachment field which gave me the Bring to Front button but it still was not in front of the attachment field, only the character field. Can this still be done in ARS 7.0.01 p004 (admin tool is also p004)? Jason -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: Friday, November 30, 2007 5:11 AM To: arslist@ARSLIST.ORG Subject: Re: On-the-fly permissions in Attachment field That would set the focus to the field. But normally you right-click an attachment to access it. Or is there an alternate method? Dwayne Martin James Madison University Original message >Date: Thu, 29 Nov 2007 10:05:41 -0800 >From: Jason Miller <[EMAIL PROTECTED]> >Subject: Re: On-the-fly permissions in Attachment field >To: arslist@ARSLIST.ORG > >Ah the go old transparent box over a field method. This doesn't prevent them >from using the tab key to navigate behind the box though. > >-Original Message- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin >Sent: Thursday, November 29, 2007 4:33 AM >To: arslist@ARSLIST.ORG >Subject: Re: On-the-fly permissions in Attachment field > >Thanks, Carey and Jason. Both are good ideas that I'll check into. > >I also got an off-line suggestion from Gary Opela that said: > >". . . if they can only add an attachment by right-clicking the field, try >putting a transparent box on top of the attachment field and then >show/hiding it depending on the user. I know it's hokey, but it should >work." (quoted with his permission) > >To which I replied: "Thanks for the suggestion. I should have mentioned, >that I want Public to be able to read, just not change the attachments." > >Is there some reason why attachment fields can't be made read-only? > >Dwayne Martin >James Madison University > > Original message >>Date: Wed, 28 Nov 2007 20:42:40 -0800 >>From: Jason Miller <[EMAIL PROTECTED]> >>Subject: Re: On-the-fly permissions in Attachment field >>To: arslist@ARSLIST.ORG >> >>Another options is to use an attachments form and not use an attachment >>field directly on the form but a table that allows you to interact with the >>attachment record. Now the attachment has its own record you have complete >>control over the read/write security of the file using row level >permissions >>and workflow. >> >>Stephen Heider created a attachments form and a utility that will add your >>attachments from the original form to the new attachments form (I don't >>remember if it deletes the attachment from the original form or just copies >>it). Check out the ARS_CreateAttachmentsForm application in the downloads >>section on http://arswiki.org/projects/dotnetutil. >> >>Jason >> >>-Original Message- >>From: Action Request System discussion list(ARSList) >>[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black >>Sent: Wednesday, November 28, 2007 2:58 PM >>To: arslist@ARSLIST.ORG >>Subject: Re: On-the-fly permissions in Attachment field >> >>Dwayne, >> >>I would think that a Join of A and B would be a better option than >>using read-only/read-write display properties of the client. ( That by >>the way: the display property is not a real security feature.) The >>join could inherit the Assignee from Form B as the Assignee for the >>join and the "Assignee" group could be granted change access to the >>field. >> >>( Hope that makes sense. Hope that Helps) >> >>-- >>Carey Matthew Black >>Remedy Skilled Professional (RSP) >>ARS = Action Request System(Remedy) >> >>Love, then teach >>Solution = People + Process + Tools >>Fast, Accurate, Cheap Pick two. >> >> >>On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: >>> Hello Everyone, >>> >>> We have a Form A with Attachment fields. >>> >>> Form B is a sub-file to Form A. >>> >>> We want anyone who is an Assignee in a Form B subfile entry, to be able >to >>
Re: On-the-fly permissions in Attachment field
That would set the focus to the field. But normally you right-click an attachment to access it. Or is there an alternate method? Dwayne Martin James Madison University Original message >Date: Thu, 29 Nov 2007 10:05:41 -0800 >From: Jason Miller <[EMAIL PROTECTED]> >Subject: Re: On-the-fly permissions in Attachment field >To: arslist@ARSLIST.ORG > >Ah the go old transparent box over a field method. This doesn't prevent them >from using the tab key to navigate behind the box though. > >-Original Message- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin >Sent: Thursday, November 29, 2007 4:33 AM >To: arslist@ARSLIST.ORG >Subject: Re: On-the-fly permissions in Attachment field > >Thanks, Carey and Jason. Both are good ideas that I'll check into. > >I also got an off-line suggestion from Gary Opela that said: > >". . . if they can only add an attachment by right-clicking the field, try >putting a transparent box on top of the attachment field and then >show/hiding it depending on the user. I know it's hokey, but it should >work." (quoted with his permission) > >To which I replied: "Thanks for the suggestion. I should have mentioned, >that I want Public to be able to read, just not change the attachments." > >Is there some reason why attachment fields can't be made read-only? > >Dwayne Martin >James Madison University > >---- Original message >>Date: Wed, 28 Nov 2007 20:42:40 -0800 >>From: Jason Miller <[EMAIL PROTECTED]> >>Subject: Re: On-the-fly permissions in Attachment field >>To: arslist@ARSLIST.ORG >> >>Another options is to use an attachments form and not use an attachment >>field directly on the form but a table that allows you to interact with the >>attachment record. Now the attachment has its own record you have complete >>control over the read/write security of the file using row level >permissions >>and workflow. >> >>Stephen Heider created a attachments form and a utility that will add your >>attachments from the original form to the new attachments form (I don't >>remember if it deletes the attachment from the original form or just copies >>it). Check out the ARS_CreateAttachmentsForm application in the downloads >>section on http://arswiki.org/projects/dotnetutil. >> >>Jason >> >>-Original Message- >>From: Action Request System discussion list(ARSList) >>[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black >>Sent: Wednesday, November 28, 2007 2:58 PM >>To: arslist@ARSLIST.ORG >>Subject: Re: On-the-fly permissions in Attachment field >> >>Dwayne, >> >>I would think that a Join of A and B would be a better option than >>using read-only/read-write display properties of the client. ( That by >>the way: the display property is not a real security feature.) The >>join could inherit the Assignee from Form B as the Assignee for the >>join and the "Assignee" group could be granted change access to the >>field. >> >>( Hope that makes sense. Hope that Helps) >> >>-- >>Carey Matthew Black >>Remedy Skilled Professional (RSP) >>ARS = Action Request System(Remedy) >> >>Love, then teach >>Solution = People + Process + Tools >>Fast, Accurate, Cheap Pick two. >> >> >>On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: >>> Hello Everyone, >>> >>> We have a Form A with Attachment fields. >>> >>> Form B is a sub-file to Form A. >>> >>> We want anyone who is an Assignee in a Form B subfile entry, to be able >to >>add/change/delete attachments in Form A. >>> >>> You could make an ordinary field read-only, then On Display, you could >>check to see if the User was in the subfile, and if so, make the field >>read-write. But I don't see any way of making Attachments read-only. >>> >>> Any suggestions? >>> >>> (ARS 7.1, RH Linux server, Oracle 10.2 db) >>> >>> Dwayne Martin >>> James Madison University >> >>___ >_ >>___ >>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" > > >___ >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" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: On-the-fly permissions in Attachment field
Ah the go old transparent box over a field method. This doesn't prevent them from using the tab key to navigate behind the box though. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin Sent: Thursday, November 29, 2007 4:33 AM To: arslist@ARSLIST.ORG Subject: Re: On-the-fly permissions in Attachment field Thanks, Carey and Jason. Both are good ideas that I'll check into. I also got an off-line suggestion from Gary Opela that said: ". . . if they can only add an attachment by right-clicking the field, try putting a transparent box on top of the attachment field and then show/hiding it depending on the user. I know it's hokey, but it should work." (quoted with his permission) To which I replied: "Thanks for the suggestion. I should have mentioned, that I want Public to be able to read, just not change the attachments." Is there some reason why attachment fields can't be made read-only? Dwayne Martin James Madison University Original message >Date: Wed, 28 Nov 2007 20:42:40 -0800 >From: Jason Miller <[EMAIL PROTECTED]> >Subject: Re: On-the-fly permissions in Attachment field >To: arslist@ARSLIST.ORG > >Another options is to use an attachments form and not use an attachment >field directly on the form but a table that allows you to interact with the >attachment record. Now the attachment has its own record you have complete >control over the read/write security of the file using row level permissions >and workflow. > >Stephen Heider created a attachments form and a utility that will add your >attachments from the original form to the new attachments form (I don't >remember if it deletes the attachment from the original form or just copies >it). Check out the ARS_CreateAttachmentsForm application in the downloads >section on http://arswiki.org/projects/dotnetutil. > >Jason > >-Original Message- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black >Sent: Wednesday, November 28, 2007 2:58 PM >To: arslist@ARSLIST.ORG >Subject: Re: On-the-fly permissions in Attachment field > >Dwayne, > >I would think that a Join of A and B would be a better option than >using read-only/read-write display properties of the client. ( That by >the way: the display property is not a real security feature.) The >join could inherit the Assignee from Form B as the Assignee for the >join and the "Assignee" group could be granted change access to the >field. > >( Hope that makes sense. Hope that Helps) > >-- >Carey Matthew Black >Remedy Skilled Professional (RSP) >ARS = Action Request System(Remedy) > >Love, then teach >Solution = People + Process + Tools >Fast, Accurate, Cheap Pick two. > > >On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: >> Hello Everyone, >> >> We have a Form A with Attachment fields. >> >> Form B is a sub-file to Form A. >> >> We want anyone who is an Assignee in a Form B subfile entry, to be able to >add/change/delete attachments in Form A. >> >> You could make an ordinary field read-only, then On Display, you could >check to see if the User was in the subfile, and if so, make the field >read-write. But I don't see any way of making Attachments read-only. >> >> Any suggestions? >> >> (ARS 7.1, RH Linux server, Oracle 10.2 db) >> >> Dwayne Martin >> James Madison University > >___ _ >___ >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" ___ 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"
Re: On-the-fly permissions in Attachment field
Re "(I don't remember if it deletes the attachment from the original form or just copies it)"the utility does not delete or alter any of the existing attachment fields. After the conversion is complete and users are using the attachments form and your new workflow then the ARS developer may choose to delete the attachment fields to free up space. Stephen Remedy Skilled Professional -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason Miller Sent: Wednesday, November 28, 2007 11:43 PM To: arslist@ARSLIST.ORG Subject: Re: On-the-fly permissions in Attachment field Another options is to use an attachments form and not use an attachment field directly on the form but a table that allows you to interact with the attachment record. Now the attachment has its own record you have complete control over the read/write security of the file using row level permissions and workflow. Stephen Heider created a attachments form and a utility that will add your attachments from the original form to the new attachments form (I don't remember if it deletes the attachment from the original form or just copies it). Check out the ARS_CreateAttachmentsForm application in the downloads section on http://arswiki.org/projects/dotnetutil. Jason -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Wednesday, November 28, 2007 2:58 PM To: arslist@ARSLIST.ORG Subject: Re: On-the-fly permissions in Attachment field Dwayne, I would think that a Join of A and B would be a better option than using read-only/read-write display properties of the client. ( That by the way: the display property is not a real security feature.) The join could inherit the Assignee from Form B as the Assignee for the join and the "Assignee" group could be granted change access to the field. ( Hope that makes sense. Hope that Helps) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: > Hello Everyone, > > We have a Form A with Attachment fields. > > Form B is a sub-file to Form A. > > We want anyone who is an Assignee in a Form B subfile entry, to be able to add/change/delete attachments in Form A. > > You could make an ordinary field read-only, then On Display, you could check to see if the User was in the subfile, and if so, make the field read-write. But I don't see any way of making Attachments read-only. > > Any suggestions? > > (ARS 7.1, RH Linux server, Oracle 10.2 db) > > Dwayne Martin > James Madison University ___ 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" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: On-the-fly permissions in Attachment field
Thanks, Carey and Jason. Both are good ideas that I'll check into. I also got an off-line suggestion from Gary Opela that said: ". . . if they can only add an attachment by right-clicking the field, try putting a transparent box on top of the attachment field and then show/hiding it depending on the user. I know it's hokey, but it should work." (quoted with his permission) To which I replied: "Thanks for the suggestion. I should have mentioned, that I want Public to be able to read, just not change the attachments." Is there some reason why attachment fields can't be made read-only? Dwayne Martin James Madison University Original message >Date: Wed, 28 Nov 2007 20:42:40 -0800 >From: Jason Miller <[EMAIL PROTECTED]> >Subject: Re: On-the-fly permissions in Attachment field >To: arslist@ARSLIST.ORG > >Another options is to use an attachments form and not use an attachment >field directly on the form but a table that allows you to interact with the >attachment record. Now the attachment has its own record you have complete >control over the read/write security of the file using row level permissions >and workflow. > >Stephen Heider created a attachments form and a utility that will add your >attachments from the original form to the new attachments form (I don't >remember if it deletes the attachment from the original form or just copies >it). Check out the ARS_CreateAttachmentsForm application in the downloads >section on http://arswiki.org/projects/dotnetutil. > >Jason > >-Original Message- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black >Sent: Wednesday, November 28, 2007 2:58 PM >To: arslist@ARSLIST.ORG >Subject: Re: On-the-fly permissions in Attachment field > >Dwayne, > >I would think that a Join of A and B would be a better option than >using read-only/read-write display properties of the client. ( That by >the way: the display property is not a real security feature.) The >join could inherit the Assignee from Form B as the Assignee for the >join and the "Assignee" group could be granted change access to the >field. > >( Hope that makes sense. Hope that Helps) > >-- >Carey Matthew Black >Remedy Skilled Professional (RSP) >ARS = Action Request System(Remedy) > >Love, then teach >Solution = People + Process + Tools >Fast, Accurate, Cheap Pick two. > > >On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: >> Hello Everyone, >> >> We have a Form A with Attachment fields. >> >> Form B is a sub-file to Form A. >> >> We want anyone who is an Assignee in a Form B subfile entry, to be able to >add/change/delete attachments in Form A. >> >> You could make an ordinary field read-only, then On Display, you could >check to see if the User was in the subfile, and if so, make the field >read-write. But I don't see any way of making Attachments read-only. >> >> Any suggestions? >> >> (ARS 7.1, RH Linux server, Oracle 10.2 db) >> >> Dwayne Martin >> James Madison University > > >___ >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" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: On-the-fly permissions in Attachment field
Another options is to use an attachments form and not use an attachment field directly on the form but a table that allows you to interact with the attachment record. Now the attachment has its own record you have complete control over the read/write security of the file using row level permissions and workflow. Stephen Heider created a attachments form and a utility that will add your attachments from the original form to the new attachments form (I don't remember if it deletes the attachment from the original form or just copies it). Check out the ARS_CreateAttachmentsForm application in the downloads section on http://arswiki.org/projects/dotnetutil. Jason -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Wednesday, November 28, 2007 2:58 PM To: arslist@ARSLIST.ORG Subject: Re: On-the-fly permissions in Attachment field Dwayne, I would think that a Join of A and B would be a better option than using read-only/read-write display properties of the client. ( That by the way: the display property is not a real security feature.) The join could inherit the Assignee from Form B as the Assignee for the join and the "Assignee" group could be granted change access to the field. ( Hope that makes sense. Hope that Helps) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: > Hello Everyone, > > We have a Form A with Attachment fields. > > Form B is a sub-file to Form A. > > We want anyone who is an Assignee in a Form B subfile entry, to be able to add/change/delete attachments in Form A. > > You could make an ordinary field read-only, then On Display, you could check to see if the User was in the subfile, and if so, make the field read-write. But I don't see any way of making Attachments read-only. > > Any suggestions? > > (ARS 7.1, RH Linux server, Oracle 10.2 db) > > Dwayne Martin > James Madison University ___ 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"
Re: On-the-fly permissions in Attachment field
Dwayne, I would think that a Join of A and B would be a better option than using read-only/read-write display properties of the client. ( That by the way: the display property is not a real security feature.) The join could inherit the Assignee from Form B as the Assignee for the join and the "Assignee" group could be granted change access to the field. ( Hope that makes sense. Hope that Helps) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Nov 28, 2007 3:05 PM, Dwayne Martin <[EMAIL PROTECTED]> wrote: > Hello Everyone, > > We have a Form A with Attachment fields. > > Form B is a sub-file to Form A. > > We want anyone who is an Assignee in a Form B subfile entry, to be able to > add/change/delete attachments in Form A. > > You could make an ordinary field read-only, then On Display, you could check > to see if the User was in the subfile, and if so, make the field read-write. > But I don't see any way of making Attachments read-only. > > Any suggestions? > > (ARS 7.1, RH Linux server, Oracle 10.2 db) > > Dwayne Martin > James Madison University ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
On-the-fly permissions in Attachment field
Hello Everyone, We have a Form A with Attachment fields. Form B is a sub-file to Form A. We want anyone who is an Assignee in a Form B subfile entry, to be able to add/change/delete attachments in Form A. You could make an ordinary field read-only, then On Display, you could check to see if the User was in the subfile, and if so, make the field read-write. But I don't see any way of making Attachments read-only. Any suggestions? (ARS 7.1, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
