Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Form descriptions


Portal form description


FieldMandatoryDescription
TitleNInternal portal title.
Path NameN

Specify a URL suffix to use in a portal URL. For example, if you type portal, the instance URL for this portal will be

<your_instance_url>/portal.

This value should be unique and not used by other portals.

LogoNSpecify a portal logo appearing in the page header.
FaviconNSpecify a portal favicon appearing favicon appearing in the tab header.
SCSS variablesNDefine the portal-specific SCSS classes developed to customize the portal.
SCSS stylesNDefine the portal-specific SCSS styles developed to customize the portal.
ActiveNSelect this checkbox to make the portal active or inactive.
Login PageNSpecify a login page for the portal, selecting a preferred one from the dictionary (you can skip this step ; you and get back to it later after you create the necessary pages).
Home PageNSpecify a home page for the portal, selecting a preferred one from the dictionary (you can skip this step and get back to it later after creating the necessary pages).
404 PageNSpecify a 404 error page for the portal, selecting a preferred one from the dictionary (you can skip this step and get back to it later after creating the necessary pages).
Footer ContainerNSpecify a portal footer selecting a preferred one from the container list (you can skip this step and get back to it later after creating the necessary containers).
Header ContainerNSpecify a portal header selecting a preferred one from the container list (you can skip this step and get back to it later after creating the necessary containers).



Portal page form description


FieldMandatoryDescription
TitleNSpecify a page title.
DescriptionNSpecify a page description.
Path NameY

Specify a URL suffix to be used in a portal URL. For example, if you type page, and the portal suffix typed earlier is portal, the URL for this page will be

<your_instance_url>/portal/page.

Options tab. This tab is responsible for the page template configuring.
Dynamic Link NameNThe page title to use in the breadcrumbs and the sidebar menu.
Dynamic Page TitleNSpecify variables to generate titles depending on the loaded content.
ActiveNSelect this checkbox to make the page active or inactive. When active, you can use this page to create other pages on its basis.
PublicNSelect this checkbox to make this page visible for unauthorized persons. In fact, when this checkbox is selected, the page is for public access, so use it cautiously.
Use for Home PageNSelect this checkbox to use this page as a home page (a page you want users to see when they sign in).
Use Portal HeaderNSelect this checkbox to use this page as a portal header.
Use Portal FooterNSelect this checkbox to use this page as a portal footer.
Styles tab. This tab is responsible for page customizing.
SCSS VariablesNDefine the page-specific SCSS variables customizing the page. The variables defined there override the ones defined on the portal level (in the SCSS variables field of the Portal table).
SCSS StylesDefine the page-specific SCSS styles customizing the page. The styles entered there to override the ones defined on the portal level (in the Portal table's SCSS styles field).
Background ImageNAttach an image to use as a background for your page. The maximum size of the image is 20 Mb.
Background ColorNSelect the page background color. These colors are preconfigured and stored in the Colors (sys_color) dictionary. To add a custom color different from the existing one, please contact your vendor.



Portal node form description


Field

Mandatory

Description

PortalNSpecify a portal (a record created earlier) to define a structure with this portal node.
Parent Node IDNSpecify a parent node ID. This ID is used as a high-level element for menus and breadcrumbs.
Page IDNSpecify a page containing a template to define a structure with this portal node.
Item TableNSpecify the table containing the portal items. For example, it can be the Article (article) table.
Item Parent ColumnNSpecify the column in the Item table related to the parent category to assign a parent category. For example, if the Article table has been chosen as the item table, you can select the KB Category (knowledge_base_category) column as an item parent category column.
Category Item ConditionN

Specify a condition that must be met to display a category item. Use a Condition Builder to build complex AND/OR filters for this. You can also define a sorting there by any preferable field.

For example, you need to display only published Knowledge Base articles sorted by the publication date. In this case, please complete the state below (please keep in mind that in this example, Item Table should be equal to Article):

  1. In the Category Item Condition field, click the funnel icon to call the Condition Builder.
    1. In the Field field, select State
    2. In the Operator field, select is
    3. In the Value field, select Published.
  2. Click Sort.
  3. In the field that appeared, select Order.
  4. Select the preferred sorting order (ascending or descending).
  5. Close the Condition Builder. The condition is saved.

Item PageNA template of the item specified in the Page ID field.
Path NameN

Specify a URL suffix to be used in a portal URL. For example, if you type page, and the portal suffix typed earlier is portal, the URL for this page will be

<your_instance_url>/portal/page.

ActiveNSelect this checkbox to make this portal node active or inactive. 
PublicNSelect this checkbox to make this page visible for unauthorized persons. In fact, when this checkbox is selected, the page is for public access, so use it cautiously.
Enable Dynamic NodesNSelect this checkbox to enable or disable the possibility of the dynamic nodes resizing.
Category TableNSpecify the table containing the portal item categories. For example, it can be the KB Category (knowledge_base_category) table.
Category Parent ColumnNSpecify a column in the Category table related to the parent category to assign a parent category for a category. For example, if the KB Category table has been chosen as a category table, select the Parent KB Category (parent_knowledge_base_category).
Category ConditionNSpecify a condition that must be met to display a category. Use a Condition Builder to build complex AND/OR filters for this. You can also define a sorting there by any preferable field.


Page container form description


Field

Mandatory

Description

NameNSpecify a container name.
PageNSpecify a reference page for this container.
CSS Class NamesNSpecify CSS classes for the container. Classes defined there override classes defined on upper levels (for the page or the portal).
Background ImageNAttach an image to use as a background for your container. The maximum size of the image is 20 Mb.
Background ColorNSelect the container background color. These colors are preconfigured and stored in the Colors (sys_color) dictionary. To add a custom color different from the existing one, please contact your vendor.
OrderNEnter a number that will define the container order in a template. Items are sorted in ascending order.
Fixed WidthNSelect this checkbox to turn the container indent on and off.
ActiveNSelect this checkbox to make a container active or inactive.


Page row form description


ActiveSelect this checkbox to make a row active or inactive

Field

Mandatory

Description

Page СontainerNSpecify a page container for this row.
CSS Class NamesNSpecify CSS class names customizing the elements view located on this row. Classes defined there override classes defined on upper levels.
ActiveNSelect this checkbox to make a row active or inactive.
OrderNEnter a number that will define the row order on a page. Rows are sorted in ascending order.


Page

СontainerNSpecify a page container for this row.

Page column form description


Field

Mandatory

Description

Page RowNSpecify a previously created row for this column.
CSS Class NamesNSpecify CSS class names customizing the elements view located on this row. Classes defined there override classes defined on upper levels.
Extra-Small DevicesN

Enter a number from 0 to 12 that will define the width of the column (for example, if there are two columns in a row with width values 4 and 8, respectively, then the width of one of them will be equal to 1/3 of a page, and another one’s width will be equal to 2/3 of that page).

This parameter is responsible for portal view in browsers in extra small devices (phones less than 768px).

Small DevicesNThis parameter is responsible for portal view in browsers in small devices (tablets 768px and up).
Medium DevicesNThis parameter is responsible for portal view in browsers in medium-size devices (desktops 992px and up).
Large DevicesN

This parameter is responsible for portal view in browsers in large devices (large desktops 1200px and up).

ActiveNSelect this checkbox to make this column active or inactive.
OrderNEnter a number that will define the column order in a row. Columns are sorted in ascending order.


Widget instance form description


Field

Mandatory

Description

WidgetNSpecify a widget configured earlier (choose it from the Widget (sys_widget) dictionary).
Page Column IDNSpecify an ID of the column on some page for applying these settings.
Option Schema ValuesN

This field allows changing some output data for specified widgets. Specify clarifying options in JSON format. For example below, the empty selection performed against the Employee table.

ActiveNSelect this checkbox to make this widget instance active or inactive.
PublicNSelect this checkbox to make this widget visible on the portal page.
OrderN

This field specifies the order of widgets location in a portal column.

Fill in this field with the integer number to display the widgets by increasing this field's valuefield value

When displaying a simple single widget in a column, the order value does not matter.


Widget option form description


Portal configuration guide

To configure a Self-Service Portal related to your instance, you need to create its structure first. Generally, the procedure of portal set up and configuration looks as follows:

  1. Create Portal records. 
  2. Create Pages, containing information about the portal pages.
  3. Create Portal Nodes, entities allowing to bind portals and portal pages.
  4. Create Page Containers, allowing building the structural view of a page through columns and rows.
  5. Create Page Rows, dividing the container into rows.
  6. Create Page Columns, dividing rows into proportionally customizable columns.

Portal structure graphically may be represented as shown below.

Advice

When following these steps and creating portal components, it is highly recommended to create them out of the Related Lists area of the higher-level objects instead of creating "from scratch". For example, after creating a portal page, you can create a related container for this page right away.

Creating portal components using the related objects structure provided will help to implement the portal structure above. 

Setting up a Portal

Creating portal


To create a single portal, please complete the steps below:

  1. Navigate to Portal Structure → Portals.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.

Portal form fields

Title

Mandatory

Description

TitleNInternal portal title.
Path NameN

Specify a URL suffix to use in a portal URL. For example, if you type portal, the instance URL for this portal will be

<your_instance_url>/portal.

This value should be unique and not used by other portals.

LogoNSpecify a portal logo appearing in the page header.
FaviconNSpecify a portal favicon appearing in the tab header.
SCSS variablesNDefine the portal-specific SCSS classes developed to customize the portal.
SCSS stylesNDefine the portal-specific SCSS styles developed to customize the portal.
ActiveNSelect this checkbox to make the portal active or inactive.
Login PageNSpecify a login page for the portal selecting a preferred one from the dictionary (you can skip this step you get back to it later after you create necessary pages).
Home PageNSpecify a home page for the portal selecting a preferred one from the dictionary (you can skip this step and get back to it later after you create necessary pages).
404 PageNSpecify a 404 error page for the portal selecting a preferred one from the dictionary (you can skip this step and get back to it later after you create necessary pages).
Footer ContainerNSpecify a portal footer selecting a preferred one from the container list (you can skip this step and get back to it later after you create necessary containers).
Header ContainerNSpecify a portal header selecting a preferred one from the container list (you can skip this step and get back to it later after you create necessary containers).

Creating pages


The portal page is a template for other pages, so it is very important to configure it carefully.

To create a page template, please complete the steps below:

  1. Navigate to Portal Structure → Pages.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.
FieldMandatoryDescription
TitleNSpecify a page title.
DescriptionNSpecify a page description.
Path NameY

Specify a URL suffix to be used in a portal URL. For example, if you type page, and the portal suffix typed earlier is portal, the URL for this page will be

<your_instance_url>/portal/page.

Options tab. This tab is responsible for the page template configuring.
Dynamic Link NameNThe page title to use in the breadcrumbs and the sidebar menu.
Dynamic Page TitleNSpecify variables to generate titles depending on the loaded content.
ActiveNSelect this checkbox to make the page active or inactive. When active, you can use this page to create other pages on its basis.
PublicNSelect this checkbox to make this page visible for unauthorized persons. In fact, when this checkbox is selected, the page is for public access, so use it cautiously.
Use for Home PageNSelect this checkbox to use this page as a home page (a page you want users to see when they sign in).
Use Portal HeaderNSelect this checkbox to use this page as a portal header.
Use Portal FooterNSelect this checkbox to use this page as a portal footer.
Styles tab. This tab is responsible for page customizing.
SCSS VariablesNDefine the page-specific SCSS variables customizing the page. The variables defined there override the ones defined on the portal level (in the SCSS variables field of the Portal table).
SCSS StylesDefine the page-specific SCSS styles customizing the page. The styles entered there override the ones defined on the portal level (in the SCSS styles field of the Portal table).
Background ImageNAttach an image to use as a background for your page. The maximum size of the image is 20 Mb.
Background ColorNSelect the page background color. These colors are preconfigured and stored in the Colors (sys_color) dictionary. To add a custom color different from the existing, please contact your vendor.

Creating portal nodes


Portals have a tree-like architecture made of:

  • Portal nodes, also known as portal maps, are massive structural components defining layouts of portals, categories, and pages through the Portal Page field.
  • Categories and items are the pages that bind together child objects basing on some features. Categories are any structures based upon parent/child relationships, e.g., Knowledge Base with categorized Articles in it. Portal Nodes help us to implement ready-to-use structures into the structure of a portal.

To create a portal node, please complete the steps below:

  1. Navigate to Portal Structure → Portal Nodes.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply changes.

Field

Mandatory

Description

PortalNSpecify a portal (a record created earlier) for which you are defining a structure with this portal node.
Parent Node IDNSpecify a parent node ID. This ID is used as a high-level element for menus and breadcrumbs.
Page IDNSpecify a page containing a template for which a structure should be defined with this portal node.
Item TableNSpecify the table containing the portal items. For example, it can be the Article (article) table.
Item Parent ColumnNSpecify the column in the Item table related to the parent category in order to be able to assign a parent category. For example, if the Article table has been chosen as the item table, then you can select the KB Category (knowledge_base_category) column as an item parent category column.
Category Item ConditionN

Specify a condition that must be met to display a category item. Use a Condition Builder to build complex AND/OR filters for this. You can also define a sorting there by any preferable field.

For example, you need to display only published Knowledge Base articles sorted by the publication date. In this case, please complete the state below (please keep in mind that in this example, Item Table should be equal to Article):

  1. In the Category Item Condition field, click the funnel icon to call the Condition Builder
    1. In the Field field, select State
    2. In the Operator field, select is
    3. In the Value field, select Published.
  2. Click Sort.
  3. In the field appeared, select Order.
  4. Select the preferred sorting order (ascending or descending).
  5. Close the Condition Builder. The condition is saved.

Item PageNA template of the item specified in the Page ID field.
Path NameN

Specify a URL suffix to be used in a portal URL. For example, if you type page, and the portal suffix typed earlier is portal, the URL for this page will be

<your_instance_url>/portal/page.

ActiveNSelect this checkbox to make this portal node active or inactive. 
PublicNSelect this checkbox to make this page visible for unauthorized persons. In fact, when this checkbox is selected, the page is for the public access, so use it cautiously.
Enable Dynamic NodesNSelect this checkbox to enable or disable the possibility of the dynamic nodes resizing.
Category TableNSpecify the table containing the portal item categories. For example, it can be the KB Category (knowledge_base_category) table.
Category Parent ColumnNSpecify a column in the Category table related to the parent category in order to be able to assign a parent category for a category. For example, if the KB Category table has been chosen as a category table, select the Parent KB Category (parent_knowledge_base_category) there.
Category ConditionNSpecify a condition that must be met to display a category. Use a Condition Builder to build complex AND/OR filters for this. You can also define a sorting there by any preferable field.

Creating page containers


Page container is a main structural page unit. After creating, split a container with columns and rows.

To create a page container, please complete the steps below:

  1. Open a page created earlier for which you need to create a container.
  2. Scroll down to the Related Lists area and click on the Page Container tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply changes.

To obtain the available containers list, please navigate to Portal Structure → Page Containers.

In this page, you can also create a page container from scratch; for this, please follow the steps above starting from step 3.

Page container form fields

Field

Mandatory

Description

NameNSpecify a container name.
PageNSpecify a reference page for this container.
CSS Class NamesNSpecify CSS classes for the container. Classes defined there override classes defined on upper levels (for the page or for the portal).
Background ImageNAttach an image to use as a background for your container. The maximum size of the image is 20 Mb.
Background ColorNSelect the container background color. These colors are preconfigured and stored in the Colors (sys_color) dictionary. To add a custom color different from the existing, please contact your vendor.
OrderNEnter a number that will define the container order in a template. Items are sorted in an ascending order.
Fixed WidthNSelect this checkbox to turn the container indent on and off.
ActiveNSelect this checkbox to make a container active or inactive.

Creating page rows


A page container can be divided into rows, which, in turn, can be divided into columns.

To create a page row, please complete the steps below:

  1. Open a page container for which you need to create a row.
  2. Scroll down to the Related Lists area and click on the Page Row tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply changes.

To obtain the available rows list, please navigate to Portal Structure → Page Rows.

In this page, you can also create a page row from scratch; for this, please follow the steps above starting from step 3.


Page row form fields

Field

Mandatory

Description

ActiveNSelect this checkbox to make a row active or inactive.
CSS Class NamesNSpecify CSS class names customizing the elements view located on this row. Classes defined there override classes defined on upper levels.
OrderNEnter a number that will define the row order in a page. Rows are sorted in an ascending order.
Page СontainerNSpecify a page container for this row.

Creating page columns


To create page columns, please complete the steps below:

  1. Open a page row for which you need to create a column.
  2. Scroll down to the Related Lists area and click on the Page Column tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply changes.

To obtain the available columns list, please navigate to Portal Structure → Page Columns.

In this page, you can also create a page column from scratch; for this, please follow the steps above starting from step 3.

Portal column form field

Field

Mandatory

Description

Page RowNSpecify a previously created row for this column.
CSS Class NamesNSpecify CSS class names customizing the elements view located on this row. Classes defined there override classes defined on upper levels.
Extra-Small DevicesN

Enter a number from 0 to 12 that will define the width of the column (for example, if there are two columns in a row with width values 4 and 8 respectively, then the width of one of them will be equal to 1/3 of a page, and another one’s width will be equal to 2/3 of that page).

This parameter is responsible for portal view in browsers in extra small devices (phones less than 768px).

Small DevicesNThis parameter is responsible for portal view in browsers in small devices (tablets 768px and up).
Medium DevicesNThis parameter is responsible for portal view in browsers in medium-size devices (desktops 992px and up).
Large DevicesN

This parameter is responsible for portal view in browsers in large devices (large desktops 1200px and up).

ActiveNSelect this checkbox to make this column active or inactive.
OrderNEnter a number that will define the column order in a row. Columns are sorted in an ascending order.

Widgets


A widget is a small interactive application containing the server and client logics. It sends, receives and processes events through the client and server controllers. The SimpleOne widgets can be added to forms as well as to portal pages.

To know more about widgets, please refer to the Widgets section of this documentation.

Creating a portal widget


To configure a widget structure on your portal, you need to create a widget first, an application implementing some logic, server and/or client.

To create a widget, please follow the steps described in the Create a New Widget article.

Creating portal widget instance


To place a widget on a portal page, use Widget Instances. These elements help to define a specific location for the widget according to the portal column specified and to customize the widget options with the option schema.

To create a widget instance, please complete the steps below:

  1. Open a page column for which you need to create a widget instance.
  2. Scroll down to the Related Lists area and click on the Widget Instance tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply changes.

To obtain the available widget instances list, please navigate to Portal Structure → Widget Instances.

In this page, you can also create a widget instance from scratch; for this, please follow the steps above starting from step 3.


Widget Instances form fields

Field

Mandatory

Description

WidgetNSpecify a widget configured earlier (choose it from the Widget (sys_widget) dictionary).
Page Column IDNSpecify an ID of the column on some page for which these settings should be applied.
Option Schema ValuesN

This field allows changing some output data for specified widgets. Specify a clarifying options in JSON format. On example below, the empty selection performed against the Employee table.

ActiveNSelect this checkbox to make this widget instance active or inactive.
PublicN

Select this checkbox to make this

widget visible on the portal page

page visible for unauthorized persons. 

Note

In fact, when this checkbox is selected, the page is for the public access, so use it cautiously.


OrderN

This field specifies the order of widgets location in a portal column.

Fill in this field with the integer number to display the widgets by the value of this field increases. 

When displaying a simple widget in a column, the order value does not matter.

Creating a portal widget option


A portal widget option allows to define, for example, logic differences for similar widgets, also it allows to narrow down the selection criteria and solve other related tasks.

To create a widget option, please complete the steps below:

  1. Open a widget instance for which you need to create a widget instance.
  2. Scroll down to the Related Lists area and click on the Portal Widget Option tab.
  3. Click New and fill in the fields.
  4. Click Save or Save and Exit to apply changes.

To obtain the available widget options list, please navigate to Portal Structure → Widget Options.

In this page, you can also create a widget option from scratch; for this, please follow the steps above starting from step 3.

Widget Options form fields

Field

Mandatory

Description

PortalNSelect a previously created portal record from the list.
Widget InstanceNSelect the previously created widget instance from the list to bind options it. 
Option Schema ValuesN

Specify widget instance clarifying options in JSON format. These options allow transmitting values of the variables defined in the widget body for the different contexts (different widget instances).

Info

After you have defined these options as described above, they are available in the options global object.
For example, the options specified in the Widget Options:


Code Block
languagejs
themeEclipse
titleOption Schema Values
linenumberstrue
{
  "itemView": "SP%20View%20Only",
  "tsGroupId": "158983234712988195"
}

should be used in Template this way:

Code Block
languagexml
themeEclipse
titleTemplate
linenumberstrue
<search tsGroupId=options.tsGroupId searchQuery="{data.search}"
  onChange="s_widget_custom.search(arguments[0]);"
  searchUrl="/portal/search_result" showTitle="true" size="lg"
  placeholder={data.placeholderMessage} itemPage ="record" itemView=options.itemView>





Table of Contents
absoluteUrltrue
classfixedPosition
printablefalse