Using friendly URLs | HCL Digital Experience
You can associate friendly URLs with portal pages and labels. You and your users can use these friendly URLs to access specific portal pages or labels by using a human readable path, which is easy to remember.
Before you begin
For a friendly URL to work for a specific page, you must
define a friendly URL name for every page or label in the path of
the portal page hierarchy that leads to that page. You can do this
in the page properties. Friendly URLs take the following general form:
http://host_name:port_number/PortalServer_root/portal/page_id/[!ut/p/encoded_portal_suffix]
The page_id
portion of the friendly URL is made
up of the friendly URL names of all pages in the path of the page
hierarchy. This path begins at the content root and ends with the
page for which you want to give your users a friendly URL.Example:
You have a portal page that is named Products in
the user interface and has a friendly URL name
products
.
Under this Products page you have another page, which is named Appliances and
has a friendly URL name appliances
.
To access the Appliances page, users can type
the following friendly URL into the browser address field: http://www.example.com:10039/wps/portal/products/appliances
About this task
Note: When
you define friendly URLs within a virtual portal, consider the name
restrictions. For more information, read Human readable URL mappings
for virtual portals.
Procedure
- To open the Manage Pages portlet, click the Administration menu icon. Then, click .
- Locate the page for which you want to configure a friendly URL.
- Click the Edit Page Properties icon.
- In the field Friendly URL name, type the friendly name for the page.
- Click OK to save your changes.
- Repeat this procedure for every page or label in the path of the portal page hierarchy that leads to the target page.
What to do next
To make up the full HCL Digital Experience URL, the portal appends a suffix to that friendly URL. This suffix represents the current state of the page and its components. Some scenarios require short and fully human readable URLs that omit the state information. For information about how to configure short stateless URLs see Using friendly URLs without state information.