Service Portal pages are one of the entities used for structuring content. It consists of containers and rows, which, in turn, consist of columns. Manage page layouts, and you will reach the best user experience. For more information about portal structure, please refer to the Creating a Self-Service Portal article.
You should consider portal structure first before configuring because a portal set up incorrectly may not work abnormal. So it is recommended to work through portal structure carefully in advance. |
Portal pages are divided by containers implementing the page layout. Containers are divided into rows. Typically, container contains a single row, but there can be more than one row. Rows are divided into columns. Specify the number of columns for a row depending on your needs.
To divide a column in a rows, please refer to the Columns section of the Creating a Self-Service Portal article.
You can reuse portal pages provided by vendor basing on them as templates. This workaround allows to speed up the page developing process since you do not need to develop it from scratch. |
To create a page from scratch, navigate to Portal Structure → Pages and fill in the form as described in the Creating a Self-Service Portal article.
You can configure your page layout responsive to various device screen sizes. By default, four main screen sizes are supported:
To implement the responsive page layout, please complete the steps below:
If the width is not specified, then the column takes up all the row width available (the same behavior as if the max value 12 was specified). If more than one column are used and the width is not specified, then the columns share the row space equally. |
Example
You created row with 2 columns in it. Your desired display conditions are as follow:
Device class | Display condition |
---|---|
Desktop | Columns and content in them should be of equal width |
Phones | Column 1 should take up 2/3 of the screen, column 2 should take up the rest. |
Small laptops | Column 1 should take up 1/3 of the screen, column 2 should take up the rest. |
Tablets | Column 1 should take up 1/3 of the screen, column 2 should take up the rest. |
Implementation
Specify values in the Large Devices, Medium Devices, Small Devices and Extra-Small Devices fields for the Columns record forms as shown below:
Large Devices (lg size) | Medium Devices (md size) | Small Devices (sm size) | Extra-Small Devices (xs size) | |
---|---|---|---|---|
Column 1 | 6 | 4 | 4 | 8 |
Column 2 | 6 | 8 | 8 | 4 |
"12" is the maximum multiplier value for all columns in a row. In other words, columns multiplier sum (if there are more than one column in a row) cannot exceed 12. For example, three columns can have multipliers (4,4,4), or (5,5,2), or any other combination which is 12 in sum. If the multipliers sum exceeds 12, then the column moves to the new line. |
Portal header contains menu structure consisting of menu groups and items used for quick access to necessary business functionality ((for example, Service Catalog, or "My Tasks" (list of tasks a user is assigned to)). Portal header implements Tree Structures functionality, so it can be easily reconfigured.
In the cases below, we consider that you have fully configured and functional portal structure. You can use vendor-provided portal pages and other items as a sample. Copy them and build your own portal basing on them, it may speed up the process. |
To customize portal headers (that is, to add or delete items) in the most convenient way, please complete the steps below:
Portal header menu form fields
Field | Mandatory | Description | |
---|---|---|---|
Title | Y | Specify an item title to display in the header. | |
Active | Select this checkbox to make this item active or inactive. If the checkbox is not selected, the header item is not displayed. | ||
Tree | Y | In this field, specify a reference to the previously created tree containing node structure of the portal header menu.
| |
Order | Y | Specify an integer number to arrange items in the header. | |
General tab fields | |||
Access criteria | N | Specify the User Criteria defining user access to this node (card or header element). If no criteria selected, then all users are allowed to use this element and its sub-elements as long as they are not protected by separate criteria. | |
Node type | N | Specify a node type by choosing from the previously created. | |
Nesting level | Y | Node nesting level. This field is populated automatically. This parameter shows on which nesting level this item is located at. | |
Parent | Y | Specify a parent item if you are implementing a structure with some nesting levels, like this:
| |
Extra attributes tab | |||
URL | Y | Specify an URL for an item. In this field, you can specify either absolute or relative URL (relative to the current portal referring to the tree to which the current node is assigned): Absolute URL: https://instance.example.com/portal/profile Relative URL: /profile |
On the screenshots below, you can see a simple example of creating a catalog item.
Portals allow deep control of their behavior. The header main menu helps to implement this control and it is one of the navigation anchors for users.
To configure a portal header menu, please complete the steps below:
A page can be opened by default, as a homepage, when a portal is referenced by its URL accompanied with the portal suffix (for example, https://instance.example.com/sp). This page, generally, contains major information for a wide range of users.
The 404 error page should be opened when some broken link has been opened during the navigation session.
You need to create a page first before completing these steps. Also, you can reuse the pages delivered by the vendor. |
To set a page as a home page for a portal, please complete the steps below:
To set a page as a default 404 error page, please complete the steps below: