Page Information
Return to Portal Editor
Use the Page Information tabs to manage portal pages and other items in the portal navigation, including viewing and modifying page information, adding and deleting parameters, viewing page source code, establishing page security, and specifying additional navigation options.
Renaming a Page
If you created or have permissions to manage a portal page, you can rename the page.
Be aware that renaming a page affects all members in the portal as this action alters the page itself, not only your view. Renaming a page changes the display name for the page and the page navigation item. It does not change the page URL; any pretty URLs using the old name remain valid.
Even when page drafts are enabled, renaming a page takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the new page name can be seen by page viewers.
To rename a page that you created or have permissions to manage:
Entering or Changing a Page Description
If you created or have permissions to manage a page, you can change the description of the page. The new description is shown at the top of the page information settings.
Even when page drafts are enabled, changing a page description takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the new page description can be seen by page viewers.
To enter or change the description for a page that you created or have permissions to manage:
- On the Summary tab, enter or modify the text in the Description field. The new description is shown at the top of the page information settings.
Showing or Hiding a Page in the Portal Navigation
If you created or have permissions to manage a portal page, you can control whether or not that page is shown in the portal navigation. A page is added to the portal navigation when it is first published. If you hide a page, it is removed from the portal navigation for all portal viewers, but is still available in the portal editor to edit and manage.
To show or hide a page in the portal navigation for all viewers:
Setting Page Behavior for a Specific Page When No Page Variant Exists
Page variants are alternative views of an existing page for specific device groups to target specific device size and characteristics. The base page and the page variant have the same URL, security, parameters, and so on.
When using a device (such as smart phones, tablets, and desktop browsers) in a device group that does not have a page variant defined, and the device group is not the default device group for the portal, the page fallback setting determines how to render the page when it is viewed on that device. This behavior is set for all pages in a portal in the portal administration, but you can override the portal-level setting for an individual page, as described here.
This setting is honored based on the following rules:
-
If the request is from a device in the default device group for the portal, then the default (base) page will be displayed no matter what is set for Page Fallback. The default setting always overrides the Page Fallback setting.
Note:
This means that even if there is a page variant for the device group, the default (base) page will be displayed.
-
If the request is from a device that is not in the default device group for the portal, then:
-
If there is a page variant for that device group, the page variant is displayed on the device.
-
If no page variant exists for the device group, then the Page Fallback setting is used by the device:
-
To set the fallback behavior for a page when displayed on a device in a device group that does not have a page variant defined, and the device group is not the default device group for the portal:
Adding or Modifying Page Parameters
Page parameters allow communication between components and the pages that contain them by providing a means of storing values for passing to page components that have been configured to consume them.
For example, imagine a page that contains stock ticker and stock news components. You want the ticker and the news components to both consume the same parameter value so that they both show information for the same company.
Even when page drafts are enabled, changing page parameters takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the effect of new page parameters can be seen by page viewers.
Note:
If you change a page parameter value, the new value is immediately saved. You cannot revert back to the prior value. Therefore, take note of parameter values before you change them in case you want to set them back to their original values.
To add or modify page parameters:
Viewing and Modifying Page Source Code
The Source tab for a selected page enables you to view, search, and edit the source code for the page. If there is draft for the current page, the source is for the draft. If there is no page draft, then the source is for the published page.
Even when page drafts are enabled, changing page source code takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the effect of page source code changes can be seen by page viewers.
You can view and modify the source code for a page on two tabs:
-
The Page tab shows the underlying JSF (
.jspx
) file that defines the page layout and style. -
The PageDef tab shows the
.xml
file that defines the parameter definitions and task flow and data control bindings for the page.
To view the source code for a page:
Setting Page Security
By default, the pages you create in a portal are viewable by all portal members. In the Home portal, the personal pages you create are accessible only to you and the system administrator.
You can use page access settings to enable others to work with your portal pages and personal pages, and to remove that access. When you grant Create
permission on a page, those granted this permission can create subpages.
When you grant access to one of your personal pages in the Home portal to another user, they must deliberately show the page in their view. The user must take this step for each session because shared pages are not automatically shown on login.
Even when page drafts are enabled, changing page security takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the effect of new page security is implemented.
You may want to open a page to many users, but limit the exposure of a particular page component. To accomplish this, you can set the component's Access properties to hide the component, or specify more granular visibility by role or user, or by using an EL expression.
To specify security settings for a page:
Setting Navigation Properties and Display Options for a Page
You can specify various properties and display options for page navigation items to determine their appearance and behavior when the portal navigation is rendered.
Even when page drafts are enabled, changing page properties takes effect immediately on the published page, regardless of whether or not the page has a pending draft. In other words, you do not need to publish the page draft before the effect of new properties are implemented.
To set navigation properties or display options for a page navigation item: