# vs $ in the computed expressions in the xpages

In the xml code of the xpages the computed expressions begin with the character “#” or with the character “$”, ie they are one of the following types:

  • value=”#{[language]:[expression]}”
  • value=”${[language]:[expression]}”

where [language] is the name of the language, for example javascript and [expression] is the expression to compute.

The question is “what is the difference between the two cases?”. Continue reading “# vs $ in the computed expressions in the xpages”

Hidden fields in a lotus form open with a browser

In a lotus form you can hide the fields enabling the check box “Hide paragraph from Web browser” in the window of the properties of the field but in this way the field is not generated as a hidden field, i.e. a html tag input with attribute type=”hidden” is not generated and you can’t access to its value from a browser, for example using javascript.
This is a different behavior from that one using a lotus client where you can still access to the hidden fields using lotusscript and formula language. Continue reading “Hidden fields in a lotus form open with a browser”

Hiding a rich text field

Hiding a rich text field with a formula “Hide paragraph if formula is true” does not work as with other fields.
In fact the contents of rich text field can retain the same property “Hide paragraph if formula is true” when it is saved even if this property was modified with a notes client designer.
This situation occurs when the rich text field is the first element of a row or a cell of a table.
To set the new property for a rich text field, type a space or other element before the rich text field.