In this article I implement the Navigator and Dynamic View Panel controls of the XPages Extension Library in a similar way to the navigator and views in a frameset of a lotus database open using the lotus client.
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:
The question is “what is the difference between the two cases?”.
- 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”.
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.
The Form Table and Form Layout Row controls allow you to easily implement a form with the fields and their labels.
In this post I use these two controls to convert the form “Document” to xpage in a database that inherits from the template Doc Library – Notes & web (8.5).
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
The result of the validation if negative can be shown on the page from the controls “Display Error” and “Display Errors”.
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.
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:
Displaying errors in xpages
During the development of a lotus application with XPages is very useful to show the runtime errors on the XPages, to enable this feature check the “Display XPage runtime error page” under the tab XPages in Application Properties as shown below: