I have a requirement to protect a ‘Margin’ field on a form from Sales Reps.
I will have to use a level of encryption, as any Rep with half an idea would find this value in Doc Properties.
So I have experimented with Secret Fields, this obviously hides the field from anyone without the Key.
This seems like the right solution, although by adding this key, it also removes edit rights to the rest of the fields on the Form!!! not so good.
Of course this is because the Encryption is at Form level and not Field level.
So I’m really stuck, I thought that it would not be an issue to protect just one or two fields on a Form and continue to allow normal operation of the rest of the Form, how wrong am I!!!
So this must come up all the time???
What would you normally recommend???
I would really appreciate any help that anyone could give me.
I’m an admin not a dev, so my apologies in advance if this is a lame idea, but have you considered putting the secured field in a subform and not loading the subform if the user isn’t part of a specified access group/role/ACl level?
I haven’t tried anything like this, so there are probably better solutions.
But how about storing the “confidential” information in a different document that is pulled in and displayed on the form if that person has reader access to the other document?
Form 1
Name
Employee ID
Addresss
City
State/Province
…
tmpSalary
docReaders
docAuthors
Form 2
Employee ID
Salary
docReader
docAuthor
tmpSalary displays is loaded by a DBlookup. If they don’t have “access” to the document - them you set tmpSalary null and hide it. I would make tmpSalary a computed for Display field so it doesn’t save with the document.
If the person is also allowed to edit tmpSalary then you write it back whenever they save and the value has been changed. Assuming they are listed as a docAuthor, if not then you don’t update the second document.
Forget my previous comment, I was on a completely wrong trip.
If parts of the document must be editable by all, and other parts only be visible to some, storing the info in different documents is indeed the way to go.