# 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”

How to access to a control connected to a lotus field using javascript

In this post I test how to access via javascript to the following controls connected to a lotus field:

  • Edit Box: a control for entering a single line of data
  • Hidden Input: a control for hiding data to the user

A Hidden Input control is not such as an Edit Box control with “Visible” unchecked (or with property rendered set to False) because an invisible Edit Box control is not rendered in the page, not even in the html code with an attribute type=”hidden”. Continue reading “How to access to a control connected to a lotus field using javascript”

The Form Layout Column control of the Extension Library

The Form Layout Column control allow you to place the various controls (such as Form Layout Row) on multiple columns.
In the post The Form Table and Form Layout Row controls of the Extension Library I built a xpage with two Form Layout Row controls at different lines, using two Column Layout Form controls you can place the two Form Layout Row on two different columns on the same line. Continue reading “The Form Layout Column control of the Extension Library”

Validation of an Edit Box control in the XPages

In the XPages the “Edit Box” controls have some settings that allow you to perform simple validations.
These settings are under the label “Validation” of the control and depend on the value of “Display Type” under the label “Data”; in the figure you can see a screenshot of the validation of an Edit Box control of type String
validation

The result of the validation if negative can be shown on the page from the controls “Display Error” and “Display Errors”. Continue reading “Validation of an Edit Box control in the XPages”

Buttons for a view in a Custom Control

There are standard buttons that are often added to a view that perform the basic functions (new, delete, refresh) that usually you put in a view.
The code in this post is a Custom Control you can add to a XPage bound to a lotus view to insert the buttons New, Delete and Refresh.
This is also an example about how to pass values from a XPage to a Custom Control using the Custom Properties and the object compositeData.
Continue reading “Buttons for a view in a Custom Control”

Buttons for a form in a Custom Control

There are standard buttons that are often added to a form that perform the basic functions (edit, save, close) that usually you put in a form.
The code in this post is a Custom Control that you can add to a XPage connected to a lotus form to place the buttons Edit, Save and Close.
In the XPage under the label “Data” configure “Data sources” to the form lotus and under the label “XPage” set the “Next Page” as follows:


Continue reading “Buttons for a form in a Custom Control”