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
As Guest commented on Oct 8th 2020, 01:47 ... you can set hide/when formulas in the content of the Richtext field.
But I would like to ask, why is this possible and which use case is targeted here?
Does a "user" really need to ability to enrich his content with hide / when formulas at all? For example: are there any people out there who want to send mails with hide / when formulas in their mail body?
If we get rid of this "option" for the user, then there is no reason why the hide / when preset of the form should be prevented from working correctly.
use a subsection, otherwise even your end user can override it if they change the rich text in the field.
Right. The only (fairly) safe way to hide a rich text field is by putting it inside a section which hides the title when open and then put the hide-when on the section. That has the advantage that there are not embedded hide formulas inside the rich text, thus preventing issues such as this. Unfortunately, the @Getfield("Itemname") = "" still may not work. (I'm not sure. I don't use that with rich text.) But at least the hide-when on the section will override any hide-whens inside the rich text.
First of all, it would be good to distinguish the hide when formula of the item in the design independently from the hide when formulas in the front end richtext item.
I think it is important to be able to hide a richtext item if it has no content. For most fields this works with @Getfield("Itemname") = "". Unfortunately this do not work with richtext items.
This is somewhat more challenging than it might seem, as every paragraph could have different hide-when formulas or flags, and just overwriting them all could be a very bad thing. Additionally, the same rich text field could be displayed with more than one form (often due to a view's form formula, but sometimes because forms are switched as part of the workflow.
With our Midas LSX, for example, you can selectively turn on and off hide-when formulas or change them programmatically, and still customers have to be careful. I can think of a couple of our customers who change the hide-when formula when the form is switched (using Midas), but they do so with matching logic so that they don't overwrite a hide-when formula or flag that came from somewhere else, not the original form.
It might be better to request a) better programmatic control over hide-when flags and formulas, and/or b) an action that will impose the form's hide-when on every paragraph of a rich text field as a manual action, but not an automatic one.