Just tested and the users without the proper permissions still see the field (with no data in it) whether the allow any user to submit is checked or not.
Lisa ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa Sent: Wednesday, November 10, 2010 1:30 PM To: arslist@ARSLIST.ORG Subject: Re: Change Display of a field to "Edit Masked" ** LJ, How on earth do you REMEMBER all this stuff? :) I just checked and the box is NOT checked and the users without permissions still see the field. Maybe it's the other ways around? (if it IS checked, then they don't see the field or the data?) I'm going to test it. Lisa ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Wednesday, November 10, 2010 12:52 PM To: arslist@ARSLIST.ORG Subject: Re: Change Display of a field to "Edit Masked" ** Lisa, If I'm not mistaken...it's been awhile since I verified....if the field has 'allow any user to submit', then it's visible to all users...if not, then it's only visible to users that have permission to the data....if the box is checked, but they don't have access to the data, it shows them the field, but shows it blank I seem to remember that being the case at least. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Kemes, Lisa Sent: Wednesday, November 10, 2010 10:36 AM To: arslist@ARSLIST.ORG Subject: Re: Change Display of a field to "Edit Masked" ** Thanks a bunch Thad! I'll also need to create workflow to see what permissions the user has and throw that into a temp field to determine if they have proper permissions or not. And just to throw in a kicker, the fields that the customers with the proper permissions see has Assignee permissions on it, so that means that if you DON'T have permissions, I WILL have to hide field (not really a big thing, but just more workflow). Fields with Assignee permissions still allow those without the proper permissions see the field, they just don't see the data. Would really like to be able to just change the display of the field (and also have it not be reportable). That would have been nice. If display is masked out, why would it be reportable? Weird.... I'm sure there's a reason. It's just display, the data is still underneath. I'll probably use this in the future..... Just fyi - I will need to do this on 6 fields....ugh.... Lisa ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Thad Esser Sent: Wednesday, November 10, 2010 11:29 AM To: arslist@ARSLIST.ORG Subject: Re: Change Display of a field to "Edit Masked" ** Lisa, Depending on how much effort you want to put into this requirement, how about this: Pre-conditions: You have a data field, "Field A" that has appropriate access permissions set. Requirement: You want to let users without permissions to that field know that it has data, but you can't let them see the data, even through reporting. Implementation: Create a display only field, "Field B". Locate it on top of Field A and make it hidden. Disable the change flag. Read only seems like a good idea, but not necessary. There's no need to set the display type to "edit masked" (see next steps), but you can if you'd like. Create a filter that fires on Get Entry Run If: 'Field A' != $NULL$ Action 1: Set Fields, set Field B = LPAD( "", LENGTHC($Field A$), "*") note: you could just set it to a fixed number of asterisks if you didn't want the user to know how long the data is. Using the LPAD function duplicates the edit masked functionality. Create an active link that fires On Display and only for the non-privileged users, with actions that hide Field A and show Field B. Actually... the non privileged users shouldn't be able to see Field A anyway, so you shouldn't have to hide it. This solution is fairly simple for one field, but if you have a lot of fields, it could get cumbersome. Anyway, since you hadn't received any other options, I thought I'd throw this one out there. Thad Esser Remedy Developer On Tue, Nov 9, 2010 at 10:02 AM, Kemes, Lisa <lisa.ke...@tycoelectronics.com<mailto:lisa.ke...@tycoelectronics.com>> wrote: ** Nevermind. With Edit Masked, a customer can still create a report and gather this data. Not sure I want them to do that! :) Lisa ________________________________ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Kemes, Lisa Sent: Tuesday, November 09, 2010 12:57 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Change Display of a field to "Edit Masked" ** There is no way via workflow to change a form display from Edit to Edit Masked if the customer does not have the proper permissions is there? I'd like the customer to see that there is data in the field, but I want it masked. If the customer has access to the field, I was them to see the data. I don't think there is, but just wanted to make sure.... Lisa Kemes AR System Developer Tyco Electronics 717-810-2408 tel 717-602-9460 cell lisa.ke...@te.com<mailto:lisa.ke...@te.com> _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
