Extended integration options of GBS AppDesigner
In the last newsletter, we explained the operation of dynamic controls. These enable access to other IBM Notes databases from a form created using GBS AppDesigner.
In these Tips and Tricks, we will show you how to create fully functional applications with GBS AppDesigner. This now includes the creation of views in addition to the existing feature for the development of your own forms. These views display the documents created using the forms, and allow navigators to be configured to enable view switching.
Shows the user interface in the standard system, including the administration navigator and the available views to the left of the documents.
Alternatively, the views can be displayed above the actions, as shown in figure 2.
The decision as to whether switch views is on the left or at the top is made by the administrator in IBM Notes Client via the XPage settings configuration document. The application name is also defined at this point.
The standard GBS AppDesigner application features a range of standard views and navigators. They are of a general nature and can be used effectively independently from the current application. However, there is the option, as shown in figure 1, of dispensing with all standard navigators (except the administration). All views created in the GBS AppDesigner application can be managed in the administration tab, under the "Views" option (see figure 4). The navigators that the developer wants to make available to users can also be configured here. In contrast to forms, views are entered in the database as individual IBM Notes design elements. This provides advantages in terms of performance, since the index for the views can be entered by the server before the user has even opened the view. Correspondingly, there is an option of editing views via an IBM Notes developer using IBM Designer. Although IBM Notes design elements are created, users that create views and navigators via the web browser are not required to have designer rights in the ACL database.
Views are just as simple to create as forms. In most cases, no programming knowledge is necessary. The name and fields of a form are the basis for the content of a view. The selection formula for a view, i.e. the contents (documents) that are to be included, must first be determined. The simplest case is the display of documents created on the basis of a form. If required, the documents found can be defined further (e.g. due to a status or editor).
The number of columns is defined via "Define columns of view". Depending on the selection, a configuration line for each column will be displayed underneath. Formulas can also be provided here, as long as no concrete field has been selected (e.g. in the second column in figure 5). The last revision date in a process is not the last entry in the $Revisions field that contains the revision history. After the last revision, an automatic agent completes each process.
If the completion date of the last editor is displayed, the last but one entry must be selected, using the formula @Subset(@Subset($Revisions;-2);1). (Brief explanation: the processing sequences run from the inside to the outside. The last two entries are first restored with @Subset and the parameter -2, and then another @Subset and parameter 1 to restore the first entry of the result).
Navigation revision can also be started from the Administration tab as shown in figure 4. Up to 15 navigation tabs can be configured, each with up to 15 entries. The programming of actions or webpage requests is not yet possible with the current version. In this respect, the configuration of a navigator is very simple since all views created in the application are always provided for selection.