UI pages

UI pages can be used to create and display forms, dialogs, lists and other UI components.

Use UI pages as widgets on dashboards. To find the UI pages, navigate to System UI > UI Pages.

This functionality requires a knowledge of HTML or Jelly.

Figure 1. UI page form
The UI page form provides the following fields:
Table 1. UI page
Field Input Value
Name Name used to invoke the page via a URL (must not contain spaces).
HTML Main component of the page, and it defines what will be rendered when the page is shown. It can contain either static XHTML or dynamically generated content defined as Jelly, and it can call script includes and UI Macros.
Client Script Client-side JavaScript that runs in the browser (e.g. functions called by buttons, etc.). It is intended to handle any client-side processing needed, for example setting focus to a field, or other interactive DHTML features after a page is loaded. Ultimately, a UI page's Client Scripts are deployed to the browser within a <script/> tag, so it could be defined within the page's HTML field to achieve the same effect. Using the Client Script field instead to define these scripts makes things much more tidy and readable though, and it keeps the Jelly and HTML from becoming unmanageable.
Processing Script Script that runs on the server when the page is submitted. This is useful if your page has a form (defined with the <g:ui_form/> or <g:form/> tags).
Related lists on the form view:
Versions Shows all versions of the UI page.

A UI page can be secured by creating an ACL with the following parameters:

  • Type: ui_page
  • Operation: read
  • Name: name of the UI page to be protected
For details on creating an ACL rule, see Create an ACL rule.