HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Ok, based on your feedback changing the status of this idea from "already exists" back to "Needs review"
This feature does NOT exist. The majority of the apps I develop are web-based apps. We don't use encrypted fields, because most of those clients do not want to deal with maintaining private keys and Notes IDs when Notes clients don't exist. However, I can see this desired when you have a mixed use environment. If I want to hide data, I have to make sure I structure the design of the app so that "private" data are in embedded views in "child" docs. That way I can use Readers and Authors field. However, clients don't always want that structure/model of child documents and they don't understand when you say, that's they way it is unless you want keys. They all want their cake-and-eat-it-too. I don't "need" this feature, but the feature would be useful to me, and it's disingenuous to say that it "already exists".
I guess if you want to hide stuff in this manner without the limitations of using encryptions keys, you could build a more complex system that saves off the field data you want to hide to another form or a profile document and then remove the fields from the saved document. When the document is opened for viewing or editing again retrieve the field content from the secondary source(s) and repeat the exercise when the document is saved again..
WRONG TAG! THIS FEATURE DOES NOT EXIST!
If the user can open and edit the document, the user would be able to decrypt those fields as well, and thus they would show in the propertybox. Encryption does not help here.
At is simplest, an additional checkbox on the field properties (advanced tab) "Box Properties only viewable by Manager access"
Encryption keys - not only the limitations already given but having to managing them!
Encryption has its limitations:
- mixed environments: encryption is not fully supported in browsers
- you cannot use multiple encryption keys on one document (e.g. encrypt section depending on user role)
- it can get tricky if data must be available depending on the data on the document
This request is not primarily intended for high security applications. Avoiding that people have direct access to data in 'hidden' fields just helps to not confuse/mislead users.
Therefor I do not agree that this feature 'already exist'. Thomas, can you please remove that tag?
Using simple hide options on a form is not a security feature. If you want to prevent users from getting access to specific data in document, you can do that by using encrypted fields.
See https://www.ibm.com/support/knowledgecenter/de/search/encrypting%20documents%20and%20fields?scope=SSVRGU_9.0.1