Customizing Error Pages

Documentation home 

 

 

The Verj.io server contains a number of error pages which are presented to the end user when runtime errors occur. These pages are designed to be customized to meet the requirements of different customers. The pages are located within the top level directory of the Verj.io web application – at userdata/apps/<appname>/webapp.

 

File name

Displayed when...

Comments

ufs_authentication_error_page.htm

Authentication error occurs: HTTP 401 error.

Applies only if authentication of new users is enabled and the user has not signed on prior to accessing the Verj.io form.

ufs_authorisation_error_page.htm

Authorisation error occurs: HTTP 403 error.

Applies only if authentication of new users is enabled. This page appears when the end user does not have access to the requested resource.

ufs_error_message.htm

A form failure is detected by the Verj.io system e.g. form design error, external system not available etc., and a form on error event is not specified.

The html in this file will be included in an html page generated by the server. The file should not include <html>, <body> and <head> tags, or corresponding closing tags.

 

If the Production Mode server property is not checked, detailed error messages will additionally be displayed. Otherwise detailed error messages will not be displayed.

ufs_error_page.htm

A catastrophic error has occurred e.g. system or application software failure.

 

ufs_licence_expired_page.htm

The Verj.io license has expired.

 

ufs_licence_invalid_page.htm

The Verj.io license is invalid.

This can be caused by a number of factors e.g. :

1.      The underlying hardware on which the license is based has changed e.g. a MAC address.

2.      The license file has been modified.

ufs_licence_maxusers_page.htm

The maximum number of runtime users allowed by the license has been exceeded and access has been denied.

See Help --> Licence to display the maximum number of runtime users configured in the license.

ufs_timeout_page.htm

A timeout occurs part way through a form.

The timeout period (maximum time between receiving data from a client browser) is set using the Server Admin Application.

ufs_invalid_state_page.jsp

A request is received to display a page for a form which is no longer in memory. Probably, this is caused by the user clicking the browser back or forward button to a page that can no longer be displayed.

 

Click here for more details.

When back button support is enabled for a form, display of this page can be a normal situation and does not result in termination of the user’s application. The user can return to their working form by reversing their action – usually by clicking the browser forward button.

 

The JSP supplied with the Verj.io system displays system text 614. This is a multi-lingual text that can be configured. For more complex changes, the JSP code can be changed.