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. You can also create simple AngularJS applications using UI pages.
The UI page form contains the following fields:
| Field | Description |
|---|---|
| Name | Name used to invoke the page via a URL \(must not contain spaces\). |
| Application | Displays the current application scope. |
| Description | The description of the UI page and what it’s used for. |
| Direct | Select this check box for a direct UI page \[sys\_ui\_page\]. A direct UI page doesn't include the common HTML, CSS, and scripts. This setting requires adding custom CSS and JavaScript to use in the page. |
| HTML | Main component of the page where you define what is rendered when the page is shown. It can contain either static XHTML, dynamically generated content defined as Jelly, or call script includes and UI Macros.Note: If GlideRecord/GlideDBQuery is used instead of GlideRecordSecure, a security recommendation message displays. |
| Client Script | Include client-side JavaScript that runs in the browser, such as functions called by buttons. It’s intended to handle any client-side processing needed, like setting focus to a field or other interactive DHTML features after a page is loaded. Client scripts for the UI page are deployed to the browser within a ` |