Tree structures allow managing The tree structure allows you to manage nested hierarchical structures of items, such as the portal header menu and card structure, more effective and easiercards. This functionality is intended to reduce work efforts spent on the portal structure configuration. The point is that nested portal items can now items can be managed through a special tree-like structure, making this process easier and more effective.
Using tree structures, you can create a node hierarchy Use the tree structure to create a node hierarchy with any predefined nesting level that allows easily implementing you to implement the navigation structure on a portal.
Note |
---|
It is recommended to recreate portal elements (headers and cards) using the tree structures structure if you are using the customized ones. Otherwise, you the errors may face faults occur in the portal headers or card structure functioningheader or cards functionality. |
A scheme below illustrates the functionality work principles:
Image Removed
Tree structures in brief
Image Added
To configure a tree structure from scratch, follow the steps below:
- Configure a node type.
- Configure a tree structure.
- Create a node itself and configure its attributes.
Create a node type
To create a node type, please complete the steps below:
- Navigate to Tree Structures → Node Types.
- Click New and fill in the fields.
- Click Save or Save and Exitexit to apply the changes.
Node type Type form fields
Field | Mandatory | Description |
---|
Name | Y | A Specify a node type name (for example, "Portal Card"). |
RE Modelmodel | N | Specify a record extension extented model responsible for the final object view and behavior. |
Need URL | N | By selecting Select this checkbox , you can to define that all objects using this node type will require the URL specification. |
Create a new tree
To create a new tree, please complete the steps below:
- Navigate to Tree Structures → Trees.
- Click New and fill in the fields.
- Click Save or Save and Exitexit to apply the changes.
Tree form fields
Field | Mandatory | Description |
---|
Name | Y |
Descriptive Specify a descriptive tree name. |
Available |
Node Typesnode types | Y | Select node types to use within this structure |
from the Node Types dictionary You You can select more than one item. |
Maximum |
Nesting Levelnesting level | Y | Specify an integer number responsible for the hierarchy maximum level. |
Active | N |
By selecting , you can make active or inactive Create a node
To create a node, please complete the steps below:
- Navigate to Tree Structures → Trees.
- Open a tree record in for which you need to create a node.
- Scroll down to In the Related Lists area, select the Simple Node related list tab.
- Click New and fill in the fields.
- Click Save or Save and Exitexit to apply the changes.
Info |
---|
To create a node from scratch, please complete the steps below: - Navigate to Tree Structures → Nodes.
- Click New and fill in the fields.
- Click Save or Save and Exitexit to apply the changes.
|
Excerpt |
---|
Node form fields Field | Mandatory | Description |
---|
Title | Y |
|
Node Specify the node title. This field can be populated in any language supported by the platform. | Tree | Y | Select a previously created tree containing information about the structure. Tip |
---|
You can use the "out-of-the-box" tree. It is called Portal Header Menu and is stored in the Tree (simple_tree) table |
| Active | N |
|
By selecting , you can a the node active or inactive. |
|
TreeSelect a previously created tree containing information about the structureEnter a number to define the node order. The nodes are sorted in ascending order. | General tab |
---|
|
fields Criteria the User Criteria defining the user criteria defining user access to this node (a card or a 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 the separate criteria do not protect them. | Node |
|
Typetype | N | Specify a node type by choosing from the previously created ones. | Nesting |
|
Levellevel | Y | Node nesting level. This field is populated automatically. This parameter shows on which nesting level this item is located |
|
at. | Parent | N | Specify a parent item if you are implementing a structure with some nesting levels, like this: Code Block |
---|
language | text |
---|
theme | Eclipse |
---|
title | Structure |
---|
| * Parent item 1
** Child item 1
** Child item 2
** Child item 3
* Parent item 2
** Child item 4
** Child item 5 |
| Extra |
---|
|
attributes Attributes tab |
---|
This tab appears if the used node type has the RE model specified, and the Need URL attribute of the node type is enabled. | URL | Y | |
|
an a 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): Info |
---|
Absolute URL: https://instance.example.com/portal/profile Relative URL: /profile |
|
|
Tip |
---|
After creating When a node that allows creating child nodesis created, you can do this right from its record form. For this, please complete the steps below when you are done and have saved the form:create child nodes for it. To do so, complete the following steps: - In Scroll down to the Child nodes related list, click New.
- Click New and fill Fill in the fields as described above.
- Click Save or Save and Exitexit to apply the changes.
|