Skip to main content

Data and interactions

Data-based widgets use a Data source saved in the User View. A source can be reused by multiple widgets within the same view.

Source types​

Environment​

Uses a pre-configured connection made available by the administrator. This is the recommended choice when the same connection must be centrally governed.

Manual​

Allows registering a protected connection directly in the view, when this option has been enabled by the administrator.

The screen allows saving, validating, revoking, or deleting the connection. Reserved values are not shown after saving. For Oracle, you must indicate whether the database name represents a SID or a Service name.

Semantic Model​

Uses fields and measures from a published and accessible Semantic Model. You can:

  • automatically follow the last published version;
  • keep the current version;
  • select dimensions, columns, and measures via checkboxes;
  • customise the alias for each field, initially equal to the field name;
  • review differences when the model publishes a new version.

Create a relational source​

  1. Select Data and then Private data sources.
  2. Enter a recognisable name.
  3. Choose the connection type.
  4. Select an authorised connection.
  5. Use Test connection.
  6. Load the available catalog; the animated indicator confirms that reading is in progress.
  7. Configure the query.
  8. Save and use Preview data. The preview can be closed with its respective command and is automatically closed when switching to another source.
  9. Associate the source with the selected widget.

The catalog shows all schemas containing readable tables or views, up to 500 objects per single schema.

If loading exceeds the server's maximum time, the Editor shows an explicit message: retry, and if the problem persists, contact the administrator indicating the time of the attempt.

With an SAP HANA connection, the catalog shows the tables, views, and columns visible to the configured user in the connection. The selected objects can be used in the Query Builder and in Preview data. If an expected object does not appear, check with the administrator the permissions assigned on the database.

Query Builder​

The Query Builder allows configuring a read without writing SQL. Available options include:

  • starting schema and table;
  • dimensions and columns;
  • measures and aggregations;
  • aliases;
  • joins;
  • conditions organised into AND/OR groups;
  • sorts;
  • optional row limit.

Verify the Preview after every significant modification, especially when joins or nested conditions are present.

Custom SQL​

The Custom SQL mode accepts read queries exclusively. Use declared parameters instead of concatenating values entered by users.

Switching from the Query Builder to Custom SQL, Sybot generates syntax consistent with the selected connection. For SAP HANA, identifiers are delimited with double quotes; a manually modified query remains under the user's control.

The editor allows:

  • formatting the query;
  • declaring parameters and initial values;
  • using parameters in view filters;
  • verifying the result in Preview.

Disallowed queries are rejected with a message; do not attempt to bypass the controls.

Associate data to widgets​

In the widget's Data and visualisation panel:

  1. select the source;
  2. choose dimension, category, or hierarchy; the trends show entity_name.field_name in alphabetical order;
  3. select the measures to display;
  4. configure aggregation and format;
  5. check the result in Preview.

Settings of a single widget do not modify the definition of the shared source.

When data are loading, each widget shows an animated indicator in the centre above the text Loading…. The indicator remains visible until the request is completed; with LIVE sources, the wait also depends on the response times of the queried system.

Ordering a chart​

For each chart, you can choose a default ascending or descending sort order on the category or on one of the displayed measures in the Editor. This is the initial order used in Preview and the published view; when the chart uses a hierarchy, the category sort order follows the displayed level.

During consultation, open the three-dot menu or the chart's context menu and select Sort order. You can temporarily apply a different order or select View default. The temporary choice does not modify the User View and is lost upon reloading the page.

In pie and donut charts, configured colours are associated with the category value. Changing the sort order modifies the arrangement of categories, but not their colour: the visual correspondence therefore remains stable.

Category colours and images​

Charts use an extended standard palette, editable from the Properties panel. In pie, donut and bar charts, you can replace the colour of a category with an image chosen from the View's Image Catalogue.

Image and colour are alternatives:

  • selecting an image disables the colour and the related fx command of the same category;
  • during asset loading, no provisional colour is shown;
  • removing the image makes the colour configuration available again;
  • for each image you can choose Fill, Contain or Repeat.

Verify in Preview that the cropping and readability of the image are adequate to the size and shape of the chart elements.

Filters​

Filters are available for:

  • category;
  • free value;
  • date range;
  • numeric range.

Each filter can be linked to one or more target widgets. The Active filters and Reset filters widgets make user selections visible and cancellable.

When Category filter uses a source derived from a Semantic Model, the filter is applied as a model field: Sybot therefore uses the relationships defined in the model to reach the target widgets fed by the same model, even if their respective sources select different fields.

In the Properties panel, Category selection allows you to choose between:

  • Single, to apply a value at a time;
  • Multiple, to open a dropdown with checkboxes and apply up to one hundred values together.

The dropdown summary indicates how many values are selected. The Active filters widget shows them in the same filter and Reset filters removes them in a single operation. The dropdown does not filter itself: after the first selection, other compatible categories remain available to add further checkboxes.

The Advanced filters panel, when enabled in view properties, collects the page's filterable fields even without a dedicated widget.

Widget interactions​

Charts and tables can send a selection to other widgets.

Examples:

  • selecting a bar to filter a table;
  • choosing a row to show its detail in a drawer;
  • using a hierarchy to move from a general category to a more specific level;
  • showing or hiding a group of widgets via Widget visibility.

Selection is an interface context and does not replace the authorization checks performed by Sybot.

In the Data table, single selection occurs by clicking directly on the row and does not show radio buttons. Multiple selection instead maintains the checkboxes, useful for verifying which rows participate in a mass action.

Maps​

The Cluster point map uses geographic coordinates and automatically groups points during zoom and resizing.

The Choropleth map colours areas based on an aggregated value. Default geographic scopes are available; for specific needs, a compatible custom map can be used. Presets recognise geographic codes and names in both Italian and English. Thresholds are configured via limit, label and colour selector; only the last one can be without an upper limit.

Always verify in Preview that geographic keys, coordinates and thresholds correspond to the available data.

Workflow widgets​

Workflow widgets allow, based on permissions:

  • to start a Workflow;
  • to pass static parameters or values of the selected record;
  • to perform an action on one or more records;
  • to display status, progress and logs;
  • to stop an active execution;
  • to update other widgets after completion.

For widgets that start a Workflow, the Editor loads the configured parameters in the Workflow, excluding those of file type. You can:

  • set a default value directly in the widget properties;
  • enable fx to calculate the default from available filters and contexts;
  • choose whether to show the parameters panel before starting and in Preview;
  • leave the panel disabled to use the configured defaults and mappings directly.

When enabled, the panel appears as a compact overlay: the user can control and edit editable values in a single step. In Preview, the panel shows the configuration result but does not start the Workflow. Protected values are not stored in the View; leaving them empty maintains the Workflow's protected default.

Before publishing:

  1. select the authorised Workflow;
  2. configure defaults, formulas or parameter mappings;
  3. add confirmation text for relevant actions;
  4. check the parameters panel in Preview;
  5. test start, error and stop from the published version;
  6. verify behaviour with a non-owner user.

Diagnostics​

When a source fails, the view displays a safe message and, if available, a reference to communicate to the administrator.

Check:

  • that the source is still active;
  • that the Semantic Model is published;
  • that required parameters have a value;
  • that the user has the necessary projects and roles;
  • that the data structure has not changed.