Common configuration
The configuration common for all portlets.
Last updated
Was this helpful?
The configuration common for all portlets.
Last updated
Was this helpful?
All portlets must have a name and a unique identifier.
Name: the name of the portlet
Unique identifier: unique string to identify this portlet.
Auto-refresh: enables the portlet to refresh the data every SS:second
If data has changed in the columns, the table will not refresh until the changes have been saved or cancelled
Exportable: enables a button to export the data as a Microsoft Excel File (.xlsx)
Available for table portlet
Auto hide header: click to hide the header in the portlet
Database source uses a connector to fetch data to the portlet. Select the connector in the drop-down query and write the select statement in the space below the connector. The database type is visible at the top-right above the statement space, as is the expand icon (F11), which can be clicked to get a larger statement space.
When the select statement has been written, press the Execute button to make the select result available in the continued configuration.
Listeners enable the portlet to listen for events sent by other portlets to execute specified commands. Specify which portlet the commands should be triggered from by clicking in the From field. Select from the list of the available portlet's unique identifier. Click New if the portlet is to listen to more than one portlet. If using listeners, remember to adjust the data source query.
The following events are available:
On Row Selection
On Refresh
On Filter
Show rows when On Row Selected is empty: tick this box if the table portlet is listening to a portlet, but should show all data if no command is given—that is if no row has been selected in the commanding portlet. This option is only available for Oracle connectors.
On Filter event will be sent when filtering data by a Filter portlet when a filter is applied. The listening portlet will react to the filter and show appropriate data.
The event will be sent when a portlet is refreshed, either manually or automatically, and refresh listening portlets.
When selecting a row or item, this event will be sent to allow portlets to listen to this specific data.
In Style, the user can set the color for portal title and add a color for a user-defined header stripe. The header stripe is visible between the table title and header sections.
Click on the color box to select the desired color.
Workflow data source fetches data to the portlet by executing specified flow studio workflows. Read more about how to work with workflows by clicking the link below.
The workflow data source fetches data, as the name implies, from a workflow.
If the workflow already has been created, select it from the drop-down. The workflow can be opened by clicking the Open button.
To create a new workflow, click the New button. Enter the workflow name, select if the workflow is to have paging and/or filtering, and click Create to save the workflow in the Studio. Click Open to launch the Studio and modify/finalize the workflow.
When a workflow is created from the Portal, the workflow will be automatically generated with Input and/or QuerySetting as start input data.
Input: enter the data or columns to be sent when communicating between two portlets, for example columns like ID and Value.
Query Settings: this contains necessary information for filtering, pagination, and sorting (only when using pagination and filtering).
Once the workflow elements have been added and finalized, configure the End Step to send data back to the Portal. The two important values that need to be sent are:
TotalCount: the calculated total count (only when using pagination and filtering).
Single table variable: table variable with data that can be used by the Portal.
To add output variables, open the End Step and tick the boxes for the output variables required to be sent to the Portal.
