About the Original Author

Recent articles by this author

In this simple tutorial the developer will be shown how to build a simple XPage Mobile application from an existing Domino database. Using the familiar Discussion template based application , we take the user on their first steps to creating an XPages Mobile web experience.

With Domino 8.5.3 and the IBM XWork Server the XPages Extension Library can be deployed using a UpdateSite database (updatesite.ntf). This makes it easier to deploy or update the XPages Extension Library without the need to manually copy the plugins in each Domino Server. This NSF based OSGi ...

This is the slidedeck from the AD116 XPages Extension Library, Making Application Developemnt Even Easier session presented at Lotusphere 2011. This session will help and show you how the Extension Library will change the way you do App development, and save you time and resources along the ...

As already mentioned in this article (http:www10.lotus.comlddddwiki.nsfdxWhatsNewin852forXPagesdisableValidation) a new validation enhancement has been added to XPages in R852. It's an option that allows you to disable validation and save data at the same time. And this is a short ...

Here is a list of the new XPages features and enhancements, some big, some small, that are in IBM Lotus Notes Domino 852. It's an A to Z with one-liners (a little rough now, some with placeholders - we will get to those in time), with links to existing articles and blog posts.

Here is a list of the new XPages features and enhancements, some big, some small, that are in IBM Lotus Notes Domino 852. It's an A to Z with one-liners (a little rough now, some with placeholders - we will get to those in time), with links to existing articles and blog posts.

Here is a list of the new XPages features and enhancements, some big, some small, that are in IBM Lotus Notes Domino 852. It's an A to Z with one-liners (a little rough now, some with placeholders - we will get to those in time), with links to existing articles and blog posts.
So here goes...

Accessibility

ARIA Support

As of release 8.5.2, most XPages controls contain a role property which is accessible by clicking All properties on the Properties tab. This property is a literal string or a computed value that returns a string.

to describe the structure of the Web page, such as headings, regions, and tables (grids)

Properties

to describe the state widgets are in, such as "checked" for a check box, or "haspopup" for a menu.

to define live regions of a page that are likely to get updates (such as stock quotes), as well as an interruption policy for those updates—for example, critical updates may be presented in an alert dialog box, and incidental updates occur within the page

for drag-and-drop that describe drag sources and drop targets

Roles, States & Properties
An ARIA role is set on an element using a role attribute.

For example,

1: <li role="menuitem">Open file…</li>

ARIA provides a collection of accessibility states and properties which are used to support platform accessibility APIs. Changes in states or properties will result in a notification to the assistive technology, which may alert the user that a change has occurred.

Java Agents in XPiNC

XPages in the Notes Client, Release 8.5.2, supports calling Java Agents to run locally on the Notes Client. Previously, only Agent.runOnServer() was supported where the NSF containing the XPages application and Java Agent were stored on a Domino Server.

Ajax

Partial Refresh Timeout

Prevent Filtering

Prevent-filtering property (TypeAhead preventFiltering property). The typeahead *always* automatically filters the entries based on the first characters sent by the browser, which prevent some use cases from working. For example, where you would like to show results from the first character on the second word. This new property prevents this filtering.

CKEditor

CKEditor - new default rich text editor to XPages. This is the new default Rich Text Editor for 852, though if you need to switch back to using the previous dojo editor, there is an option here to do so.

This editor permits the embedding of images, tables, links and emoticons.

You can adjust the toolbar that is rendered. With the rich text control in focus, click the Dojo tab and add an attribute (dojoAttributes property) named toolbarType with a value of Slim, Medium (default), or Large.

You can revert to the Dojo rich text editor. With the rich text control in focus, click the Dojo tab and specify the Dojo type (dojoType property) as ibm.xsp.widget.layout.RichText. Alternatively you can apply a theme to the entire application, for example:

1:

2: <!-- Rich Text -->

3: <control>

4: <name>InputField.RichText</name>

5: <property>

6: <name>dojoType</name>

7: <value>ibm.xsp.widget.layout.RichText</value>

8: </property>

9: ......

10: </control>

Controls

Editbox autocomplete

Support for the "autocomplete" attribute on the EditBox to help manage the setting and changing of passwords.

Data Sources

databaseName

Better server name support in the database Name attribute. This allows the database to be deployed on different servers and run on the client, XPiNC, without having to update the databaseName property for each NSF deployed to each server.

Soft Deletes

Soft deletes support enhancement.

Designer

"Pretty" Panels

Most if not all of the 'pretty' panels have been enhanced. The widely used properties from the 'All Properties' tab have now been promoted to the more user friendly panels. See the Data panel for the View Panel control.

Source

Drag and drop to the Source pane.

Lots of other stuff...

Discussion Template

The Discussion template has gotten a further update in 852 so that it performs better and has a better user experience.

Documentation

For Release 8.5.2, the XPages user's guide in the product documentation has been revised. It now includes reference topics for all controls and properties. The overview and other material has also been redrafted. Work is on going to improve this guide.

Dojo

Upgrade

Upgraded to Dojo 1.4.3 for the server and XPiNC. The server install will also include a further upgrade to 1.3.x to Dojo 1.3.3.

Type and Attributes

Dojo Type and Attributes added to more controls (including scriptBlock)

dojoForm

Support for dojoForms (dojoForm="true")

Events

onClientLoad

onClientLoad Event. Its now possible to add scripts in the events to be executed when the page is submitted or this panel or some containing panel is partial updated.

Extensions API

Some are calling this XPages, The Next Generation, and this feature is one of the main, if not the main highlight for XPages in 852.

Global Objects

Two new Global Objects for Server Side JavaScript, sessionAsSigner (open a session using the signer rights) and sessionAsSignerWithFullAccess(open a session using the signer rights, while giving it full access to the data)

sessionAsSigner

Assigns credentials based on the signer of the of XPages design element. The session is restricted by the application's ACL and the security tab of the server's Domino Directory entry.

sessionAsSignerWithFullAccess

Assigns credentials based on the signer of the of XPages design element and allows full administrative access to the application's data. The signer must have the right to such access or the session is not created.

Base Resource

HTML5 Base resource support - pageBaseUrl property renders as a base tag in the header. The &lt;base&gt; tag specifies a default URL and\or a default target, for all elements with a URL.

Infrastructure

OSGi Framework

The runtime has switched over to use the OSGi framework. All the XPages libraries (which are under xsp/nsf/lib in 851) have being moved to the OSGI framework under the shared eclipse location.

Miscellaneous

New complex-type "loaded" property

New support has been added for the loaded attribute to complex types. This will allow for a way to conditionally define a complex objects like a dominoDocument on an XPage.

OneUI

oneuiv2

A new version fully available - oneuiv2. Try out these new themes: oneuiv2, oneuiv2_green, oneuiv2_gold, oneuiv2_metal and oneuiv2_red.

Pagers

Last Page

Allows for the calculating of the Last page in a data collection for the Pager. In 851, there is a restriction on the number of pages the Pager will display. This is because of associated performance hit (this is still the case with this new property). However, customers have asked for an option to calculate this regardless. The 'alwaysCalculateLast' property, new to 852, allows you to do just that.

Performance

Further enhancements in the Java back-end classes help XPages perform better.

Repeat Control

Allow Zero Rows

Repeat Control enhancements - "xsp.repeat.allowZeroRowsPerPage". This option may be useful when you need to compute the number of rows to display as there may be situations where no rows should be displayed but the Repeat control should still render.

Security

Java Agents in XPiNC

XPages in the Notes Client, Release 8.5.2, supports calling Java Agents to run locally on the Notes Client. Previously, only Agent.runOnServer() was supported where the NSF containing the XPages application and Java Agent were stored on a Domino Server.

XPages ECL to Permissions updated to include more Java Permissions

In V851 of XPages, security for executing Java code in XPages in the Notes Client was very restricted. For XPages V852, the Java Permissions managed by the XPages ECL settings have been broadened to be similar to the set of Java Permissions allowed by Java Agents and to bring a level of equivalence between Java Permissions allowed for XPages on Domino Server (Unrestricted) and XPages in the Notes Client. For example, in V851 the ECL Network permission only covered the Java SocketPermission, now it covers NetPermission and other related Java network permissions.

Public Access

Public Access enables users to view (or create and edit) documents in cases where the user has not been explicitly granted access as either a reader or author of a particular document.

Up to now XPages applications were prevented from running if the user accessing the application only had the ability to read and write to Public Access documents. Now, in XPages Release 8.5.2, application designers can make XPages design elements available to Public Access users by setting the "Available to Public Access users" property in the Security sections of the Properties tab for an XPage.

Once an XPage has been made available to Public Access users, the user will only see

documents

that have been created from a form which the "Available to Public Access users" property set and

also contain a text field named $PublicAccess with a value of 1

contents of views

that have the "Available to Public Access User" property set in the access control options for the view (and only those documents that are available to Public Access users will appear in the view).

Managed Beans

Referencing a Managed Bean from JavaScript now supported in XPiNC. This fixes a bug where a Managed Bean, first referenced in JavaScript (which triggered the creation of the Bean) caused a security exception. The workaround was to first have this Managed Bean referenced and created as a DataSource (referencing the Bean from then on was fine). This bug is now fixed.

Single Copy XPage Design (SCXD)

Redirect XPages design elements to other databases.

XPages treats each NSF as a separate J2EE module, running in its own environment and loading its own objects. This ensures the complete isolation of each NSF. But, in some cases, a set of NSFs may share the exact same XPages, for example, MailBox databases or Quickr places.

Although the one NSF module works by having all the databases inheriting from the same template, it is not optimal in term of server resources as the same objects (design elements, java classes...) are read independently from each NSF, and retained in memory. This is also not optimal from a browser standpoint, as the same resources (.js, .css...) are coming from different URLs, which makes the browser caching less efficient.

The solution is to store the XPages design elements (XPages, Custom Controls, CSS, client/server JS libraries, themes) in a single NSF. Then, each database instance can point to the common "template" database through a new database property available in Designer.

Right Click on the Application in Designer and select Application -> Properties. Select the XPages tab and navigate to Performance section.

At runtime, XPages will read this information and if Single copy XPages design is enabled, it will then use the XPages related design elements from the "template" database instead of the current database.

View Filtering

Start Key

Very much like 'keys', startKey allows you to filter the view to start at a certain value.

Multi-level category

This is an addition to categoryFilter that allows you to filter a view by the category and then the sub-category.

View Last Page

XPages developers now have a option in the Pager control to calculate the last page in a view, so that a user can go directly to that page without having to scroll though all intervening pages. Note that there is a performance penalty for calculating the last page.

Views and View Panel

Clickable View Column Header Icons

NotesXspViewEntry.setSelected()

XPages in the Notes Client (XPiNC) Integration

Running Agents in XPiNC

XPages in the Notes Client, Release 8.5.2, supports calling Java Agents to run locally on the Notes Client. Previously, only Agent.runOnServer() was supported where the NSF containing the XPages application and Java Agent were stored on a Domino Server.

Related to Agents, and new in V852, the following NotesAgent methods are supported: NotesAgent.run, NotesAgent.runWithDocumentContext, and NotesAgent.runOnServer. Note that when run locally in the Notes Client, security is based on the client ECL settings for the signer of the agent.

New Tab\Window management support

New for Lotus Notes and Domino Designer 8.5.2 is the ability to optionally open XPage links and documents in a separate window or tab within the Notes client. This behaviour is specified at application design time and is set using the 'Window behavior' property in the user interface. The example below is for a Link.

The 'Window behavior' property has three possible values:

Use default

Open in same window and tab

Open in new window or tab (per Client preference)

Option #1 is the default value for all design elements so the behavior of existing XPages applications will not change. The 'per Client preference' mentioned here is the 'Windows and Themes -> Window Management' preference. This preference has the following three options and if option #3 above is selected, then this preference will be used to determine Window behavior.

Open each document in its own window

Open each document in its own tab

Group documents from each application on a tab

The 'Window behavior' property can be set on the following XPages design elements, and are listed in hierarchical order. Each child element will inherit its parent's behavior by default, unless the child is explicitly changed. So take care when setting this property at the Server or Application level.

Notes client

Server

Application

XPage

View

Link

These new properties will be ignored by Notes 8.5.1 clients.

New Replica option

This menu option now available when an app is launched in XPiNC.

Open in Designer option

Menu option now available for a XPages app is launched in XPiNC

XULrunner upgrade

XulRunner in XPiNC has been upgraded to 1.9x, which is equivalent to Mozilla 3.x.

window.close() support

Adds the ability to Close a Window from a Client Side JavaScript event. Needs window.open() for window.close() to work.
For example, create two XPages, b01.xsp and b02.xsp.
On b01 add a button, and add a client side event to open a new window for b02.