# Changelog – Current version: v14.2.5

## 2026-04-09 – Changelog \[v14.2.5] <a href="#id-20260226-changelog-v14.2.2" id="id-20260226-changelog-v14.2.2"></a>

* Alarm Statistics: Fix for reliable forwarding to the alarm history for the default time range from the frequency and duration table.

## 2026-03-30 – Changelog \[v14.2.4] <a href="#id-20260226-changelog-v14.2.2" id="id-20260226-changelog-v14.2.2"></a>

* Alarm Statistics: Fix for forwarding to the alarm history from the frequency and duration table.
* Alarm Statistics: Translation of the alarm text column in the frequency and duration table.

## 2026-03-07 – Changelog \[v14.2.3] <a href="#id-20260226-changelog-v14.2.2" id="id-20260226-changelog-v14.2.2"></a>

* Note: No functional changes, only adjustments to the container registry/build pipeline.

## 2026-02-26 – Changelog \[v14.2.2] <a href="#id-20260226-changelog-v14.2.2" id="id-20260226-changelog-v14.2.2"></a>

* In the alarm history, the keyword search has been expanded to include the asset name.
* In alarm statistics, “Alarm Message” and “Priority” have been added to the alarm frequency table; additionally, an incorrect forwarding from statistics to history has been fixed.
* In general, the sorting of the tag list was corrected according to the configured category order.
* In Engineering, a permission issue was fixed where users in the list could incorrectly gain access to the “Engineering” navigation item.
* In the API, the update of CalculationRules was corrected
* In the database, the rebuild of the escalation matrix for escalation target updates was corrected; additionally, a new MQTT ACL is automatically created when an MQTT account is created.
* Note (security / backward compatibility): The legacy endpoints `/xovis/*` and `/niagara/*` are automatically redirected to the protected endpoints under `/apps/<app>/api/...` .

The following bug fixes were made in this version:

## 2025-12-16 - Changelog \[v14.2.1]

### **Digital Twin – Public and user-specific Digital Twins**

The new public and user-specific [-> Digital Twins](/collection/english-v14/documentation/digital-twin.md) are here. Similar to the well-known [→ Public Dashboards,](/collection/english-v14/documentation/dashboard/global-dashboards.md) Digital Twins can now be provided for the entire project or used individually per user. This allows Digital Twins to be managed centrally while still being flexibly adapted to different user needs.

When creating a Digital Twin, two variants can be distinguished:

* **User:** The Digital Twin is visible only to the respective user.
* **Project:** The Digital Twin is visible to all users in the project.

Only the creator can edit or delete public Digital Twins.\
Digital Twins can still be copied specifically to other users, and the visibility status can also be changed later.

### **Further changes and fixes:**

* The [image](/collection/english-v14/documentation/widgets/predefined-widgets/image.md) and the [iframe](/collection/english-v14/documentation/widgets/predefined-widgets/iframe.md)widget were revised and visually improved.
* The size of downloaded analysis images has been improved.
* A bug in alarm counting in charts and in the reporter was fixed.
* The performance of alarm SSE events has been improved.
* The [-> Sankey diagram](/collection/english-v14/documentation/widgets/predefined-widgets/sankey-diagram.md) now supports displaying [CUSUM data](/collection/english-v14/academy/aggregations-in-eliona.md#kumulativzahler-cumulative-counter).

## 2025-08-18 – Changelog \[v14.2.0]

We are pleased to **present Eliona v14.2.0** — an update with new features, optimized interfaces, and targeted improvements in the areas of *Script Engine*, *Dashboard*, *Asset Management*, *Escalation Management*, *Analytics* and *Audit Trail*.\
With this version, script creation becomes more convenient, view configuration becomes more flexible, and escalation handling as well as tracking of changes in the system becomes even more transparent.

[→ Link to the full changelog v14.2.0](https://deploy.eliona.io/helm/changelogs/v14.2.txt)

### **Autocomplete and view switching in the Script Engine**

The *Script Engine* now supports rudimentary autocomplete for Python scripts. During input, matching functions, methods, and variables are automatically suggested, which makes development easier and reduces typing errors.

<div align="left"><figure><img src="/files/101ff6b41c3855f37c51567e527bf77a4bee9b18" alt="" width="305"><figcaption></figcaption></figure></div>

Additionally, a switch between the general view (*General View*) and the pure code view (*Code View*) has been integrated—ideal for switching between a clear display and a focused programming mode as needed.

<div align="left"><figure><img src="/files/d44c469687d2792010c51d2327350784c8088488" alt="" width="163"><figcaption></figcaption></figure></div>

{% content-ref url="/pages/22d3868e275c5107ec0cd6df53a069bfd12708a3" %}
[Configure scripts](/collection/english-v14/documentation/engineering/script-engine/configure-scripts.md)
{% endcontent-ref %}

### **Reporter download in the link widget**

In the *Link Widget* a report can now be selected as the download target. When a user clicks the link, the stored report is automatically downloaded—quickly and directly from the dashboard without detours.

<div align="left"><figure><img src="/files/5ebb99ce6391cc9b338fbfb8f9f25baa8448864c" alt=""><figcaption></figcaption></figure></div>

{% content-ref url="/pages/4d9a7aede8de0c5602693e490fcf48561990bd66" %}
[Links](/collection/english-v14/documentation/widgets/predefined-widgets/links.md)
{% endcontent-ref %}

### Column configuration and advanced status options for assets

In the *Asset Management* a flexible column configuration is now available, allowing the displayed information to be customized individually. In addition, non-monitored status boxes can be hidden to make the view clearer.&#x20;

{% content-ref url="/pages/3e77762dc49311586d659dc628a0022299f06eec" %}
[Assets](/collection/english-v14/documentation/assets.md)
{% endcontent-ref %}

### Advanced escalation configuration and new layout

<div align="left"><figure><img src="/files/f7f818baa36d0d764371f62c8dd233ed97d2a36d" alt="" width="563"><figcaption></figcaption></figure></div>

The escalation management has been extensively revised and now offers both a new, clearer layout and additional filtering options. With the new configuration option, alarms can be combined in a targeted way to make notifications more efficient. Alarms with certain tags—for example *High Prio* — can be excluded from the combination so that they continue to escalate individually. Thresholds can also be defined, for example that when 100 incoming alarms arrive within 10 seconds, only a single escalation message is sent instead of 100 individual messages. This significantly reduces notification floods and provides a clearer overview in alarm handling.

{% content-ref url="/pages/e6e1b849067aba2b868e1a38313521a652c84a2c" %}
[Group escalations](/collection/english-v14/documentation/alarms-rules-and-escalations/escalations/group-escalations.md)
{% endcontent-ref %}

### **Use reporting period in Analytics**

<div align="left"><figure><img src="/files/53122cb52eacb875ba7d91e2db6a098ce00d4231" alt="" width="271"><figcaption></figcaption></figure></div>

For embedded analyses in reports, the period defined in the report can now be applied directly. Previously, the period stored in the analysis itself was always used. This new option provides more flexibility and consistency, as analyses automatically take the context of the report into account.

### **Expanded Audit Trail**

The *Audit Trail* has been supplemented with several previously missing entities in order to track changes and activities even more completely. Events are now also recorded for:

* project roles
* system roles
* tags
* scripts
* escalations
* asset type attributes
* asset types
* wayfinding buildings
* projects

This means that everything is now fully logged, making a complete history and even more precise tracking of all system changes possible.

{% content-ref url="/pages/f5220317cebe05f4004dc13a757cb3c7b4e4eb32" %}
[Audit Trail](/collection/english-v14/documentation/settings/audit-trail.md)
{% endcontent-ref %}

## 2025-06-24 – Changelog \[v14.1.0]

We are pleased to *Eliona v14.1.0* to present—an update with numerous improvements in the areas of analysis, security, and system stability. Aggregated data can now be used system-wide, for example in the *Digital Twin* and in rule chains. With the new method *Time Weighted Average* more accurate evaluations over time periods are possible. Two-factor authentication (TOTP) significantly increases access security, and optimized event handling ensures reliable processing of all events—even in the event of temporary disruptions. In addition, evaluations can now be shared and used across projects as global analytics and reports—just like the familiar *Public Dashboards*.

[→ Link to the full changelog v14.1.0](https://deploy.eliona.io/helm/changelogs/v14.1.txt)

### Use aggregated data everywhere – now also in the Digital Twin

In the *Digital Twin* as well as in the *floor* aggregated values can now be used. This extension allows the visualization of historical and summarized data directly in the building context. Aggregations such as average, minimum, or maximum are available—ideal for analyzing conditions over time periods.

![](/files/18a0533eb1d5055adbd16d15d5d2bf61c3227bd1)

[→ Use aggregations in the Digital Twin](/collection/english-v14/documentation/digital-twin.md#einen-wert-verknupfen)

### Two-factor authentication with TOTP

Security has been further strengthened: with the new TOTP (Time-based One-Time Password) mechanism, an additional authentication step can now be activated. This option significantly increases access security to sensitive project data.

Setup is done directly in the **user settings** of your own profile. Once you are logged in, you can activate two-factor authentication there and connect a TOTP-compatible authentication device (e.g. Google Authenticator or Authy).

{% content-ref url="/pages/a4e23a0a95a8e12ef004f189c027784d5aee156f" %}
[Set up 2FA in Eliona](/collection/english-v14/academy/set-up-2fa-in-eliona.md)
{% endcontent-ref %}

### Global analytics and reports

The new *global analytics and reports* are here! As with the well-known [→ *Public Dashboards* ](#public-dashboards)you can now also provide your evaluations across the project. This makes it possible to manage dashboards, charts, and reports centrally and make them visible to everyone involved in the project.

When creating an analysis or a report, a distinction can be made between “User” and “Project”:

* **User**: The analysis is visible only to you personally.
* **Project**: The analysis is visible to all users in the project and is marked with a **blue dot** .

Only the creator can edit or delete global analytics.\
Analyses can still be copied specifically to other users, and the visibility status can also be edited afterward.

{% hint style="info" %}
&#x20;If an analysis is to be used in the *analysis widget* , we recommend using a **global analysis** . Only this guarantees that all users with access to the dashboard can also see the analysis.
{% endhint %}

[→ *Use analysis widget*: *Display analysis directly in dashboards*](/collection/english-v14/documentation/widgets/predefined-widgets/analytics.md)

{% content-ref url="/pages/321e1153562898651ddd5486b491a2e3660a960c" %}
[Global analytics and reports](/collection/english-v14/documentation/analytics-and-reports/global-analytics-and-reports.md)
{% endcontent-ref %}

### Time comparison in Analytics – New offset function

With the new *offset*option in Analytics, time periods can now be compared directly—for example, today with yesterday or current data with values from the previous year. This makes it even easier to analyze trends, seasonal fluctuations, or operational behavior.

The option is available directly in the analysis configuration and significantly expands the comparison options.

[→ *Use the offset function in Analytics*](/collection/english-v14/documentation/analytics-and-reports/use-analytics.md#offset-funktion-in-analytics-verwenden)

### Rules with aggregations

Rules can now be created based on aggregated attributes (average, minimum, maximum). This makes it possible to define conditions that are not based on individual values, but on time-series evaluations—ideal for monitoring that responds to trends instead of individual events.

<figure><img src="/files/9343f9888f608c0b3ac59fa020403184fe197311" alt=""><figcaption></figcaption></figure>

[→ Create rule with aggregation](/collection/english-v14/documentation/alarms-rules-and-escalations/rules/create-a-rule.md#details)

### New aggregation method: Time Weighted Average (TWA)

With the new aggregation method *Time Weighted Average* (time-weighted average), values can be calculated more realistically over time periods—especially when values do not change continuously.

In contrast to the normal *average*, in which all values are weighted equally, TWA takes into account **how long a particular value was active**. A value that remains constant for most of the period influences the average more strongly than short-term outliers.

**Example:**\
If the value “1” is written at the beginning of an hour and the value “60” is written once shortly before the end of the hour, the classic *average* (1 + 60) / 2 = **30,5**calculates.\
TWA, however, takes into account that the “1” was active for almost the entire hour—the result is then realistically around **2**.

This method is especially useful for:

* Slowly changing sensor values
* Energy or temperature curves with sudden peaks
* Context-sensitive measurement data where the duration of a state is decisive

[→ *Use TWA aggregation in Eliona*](/collection/english-v14/academy/aggregations-in-eliona.md#zeitgewichteter-durchschnitt-time-weighted-average-twa)

### Redesign of the attribute display in the asset

The attribute sidebar in the asset has been redesigned as a dialog. The new layout offers a better overview, clearer separation of information, and easier navigation through attribute details.

### **More reliable event processing in the frontend**

Event processing in the *Eliona*frontend has been further optimized to work reliably even under difficult network conditions. Unstable connections, browser tabs in the background, or local restrictions previously caused events in the client not always to be displayed immediately.

With the new architecture, Eliona automatically detects when no more events are being received in the **browser** and restarts local processing on its own. In addition, fallback polling is used to reliably deliver missed or delayed events to the client—without having to manually reload the page.

***

## 2025-05-15 – Changelog \[v14.0.5]

The following bug fixes were made in this version:

* A bug in alarms when forwarding asset attributes to alarm messages was fixed.
* A problem saving escalation targets was fixed in escalations.
* On the homepage, elements are now hidden if a user does not have the corresponding permissions.
* In rule chains, a problem in the alarm node that could occur for assets without subtype input attributes was fixed.

## 2025-04-25 – Changelog \[v14.0.4]

In this hotfix, a bug in the rule chain component “Day Schedule” was fixed, which caused schedules within rule chains not to run correctly.

## 2025-04-24 – Changelog \[v14.0.3]

In this version, several minor bug fixes and optimizations were made:

* In alarm statistics, the tag filter was expanded and now supports logical AND and OR combinations for more precise analysis.
* A problem in the Smart Assist menu, where the progress element crashed when the heap provider was missing, was fixed.
* In the Analytics component, unnecessary reloading of alarm data was suppressed to improve performance.
* A bug when exporting asset data was corrected so that data export now works reliably again.
* When using Smart View via a ShortURL, the user is now correctly logged out when their session has expired.
* The updating of aggregated data in the Smart Assist menu has been improved.

## 2025-04-23 – Changelog \[v14.0.2]

With this hotfix, a bug in rule management was fixed where pausing or starting multiple rules at different levels at the same time did not work correctly.

## 2025-04-22 – Changelog \[v14.0.1]

In this hotfix, a more stable server file hoster for the Monaco editor was integrated to avoid loading problems and ensure reliable display of the editor.

## **2025-03-26 - Changelog\[v14.0.0]**

We are pleased to present Eliona v14.0.0 to you! This version brings [**TimescaleDB**](#einfuhrung-von-timescale-automatische-aggregationen-ohne-manuelle-konfiguration) for automatic aggregations without manual configuration, extended [**rule chains**](#erweiterte-regelketten-mehr-moglichkeiten-fur-automatisierungen) with new components and improved management of [**asset characteristics**](#asset-charakteristiken-uberarbeitet-vereinfachte-verwaltung-mit-templates).

With the new [**analysis widget**](#neues-analyse-widget-direkte-einbindung-von-analysen-in-dashboards-und-smart-views) you can integrate analyses directly into dashboards and smart views, while [**job diagnostics**](#job-diagnostics-fur-eskalationen-detaillierte-nachverfolgung-von-notifications) enable detailed tracking of escalations. The [**trending configuration**](#neue-trending-konfiguration-fur-attribute) for attributes improves the storage of historical data, and new [**system settings**](#erweiterte-systemeinstellungen-verbesserte-speicherverwaltung) provide more control over storage and processing options.

In addition, [**Twig templates**](#twig-templates-in-eliona-flexible-nachrichtenerstellung) for flexible message creation have been integrated, the [**Smart Assist menu**](#uberarbeitung-des-smart-assist-menus) has been revised, and a [**broker configuration page**](#neue-konfigurationsseite-fur-den-eliona-broker) has been added for secure management of MQTT connections. [External alarms](#alarme-regeln-aus-externen-quellen-jetzt-klar-erkennbar) and rules are now clearly identifiable, and [obsolete structures](#legacy-strukturen-bereinigt) have been removed to make Eliona future-proof.

[-> Link to the full changelog v14.0](https://deploy.eliona.io/helm/changelogs/v14.0.txt)

### Introduction of Timescale – Automatic aggregations without manual configuration

With this version, Eliona introduces **TimescaleDB** a powerful time-series database specifically optimized for processing large amounts of time-dependent data. This provides **automatic aggregations in real time** without needing to configure them individually for each attribute.

<figure><img src="/files/853b4da29c1aa85fabd61a83b002605fc1c1a6d7" alt="" width="375"><figcaption></figcaption></figure>

The introduction of Timescale significantly improves performance and enables efficient processing of large data volumes. Aggregations are now calculated dynamically and are immediately available in dashboards, Smart Views, Analytics, and rule chains. Manual configuration is completely eliminated, which means the **Asset Editor** as well as all **pipeline settings** have been removed.

With this change, the use of aggregated values is made much easier, as calculations are performed directly in the system and no additional settings are required. Further information on using the new aggregations is available in the corresponding documentation:

{% content-ref url="/pages/0def57698128881e162e5f36480bced52dbf1ec8" %}
[Aggregations in Eliona](/collection/english-v14/academy/aggregations-in-eliona.md)
{% endcontent-ref %}

### **Extended rule chains – More possibilities for automations**

The **Rule Chain Engine** has been extensively expanded:

* New **building blocks**, e.g. **Script Node**, to execute scripts from the **Script Engine** .
* **Notes** can now be added within the rule chain.
* **Live data display** within the rule chain so current values can be seen directly.\
  These extensions make rule chains more powerful and enable **even more flexible automation**.

<figure><img src="/files/f1f79672ed515fe0c912ea29014f9a92056387da" alt=""><figcaption></figcaption></figure>

### New analysis widget – Direct integration of analyses into dashboards and Smart Views

The new **analysis widget** makes it possible to display existing analyses directly in dashboards and Smart Views. It takes over the complete configuration of the selected analysis and allows flexible adjustment of the time range without changing the original data.

<figure><img src="/files/c0311d8b7e943eaf9c83fc66fbb2e375c1d7fcc0" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/6927cd5de563fc4f60c823400cdc1ba9e98759c9" %}
[Analytics](/collection/english-v14/documentation/widgets/predefined-widgets/analytics.md)
{% endcontent-ref %}

### Job Diagnostics for escalations – Detailed tracking of notifications

The new **job diagnostics**page enables detailed analysis and monitoring of escalated notifications. It shows which notifications were triggered, via which providers they were escalated, and to which recipients they were sent. It also provides insight into the status, history, and possible delivery problems.

This feature helps administrators monitor the sending process, trace escalation chains, and identify problems early. Via the **job diagnostics** you can navigate directly to the associated alarm or ticket.

<figure><img src="/files/ab3ae0c684b7a2e513c063a4f2316827dd54d941" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/c723128bb4b5cb13fae369e3d52e7edd03e37167" %}
[Job diagnostic](/collection/english-v14/documentation/alarms-rules-and-escalations/escalations/notification-provider/job-diagnostic.md)
{% endcontent-ref %}

### **Asset characteristics revised – Simplified management with templates**

The configuration of asset characteristics was repetitive and confusing and had some bugs. With the new version, the bugs have been fixed and predefined **asset characteristic templates** can now be created and applied to asset templates in just a few clicks. This makes management easier and significantly reduces manual effort.

<figure><img src="/files/519444e739e5ec485759d079618500d977dd3fd7" alt="" width="563"><figcaption></figcaption></figure>

{% content-ref url="/pages/79b0ab8d11308fa5374c0a6e9a222f0709c58655" %}
[Create a new asset characteristic template](/collection/english-v14/documentation/assets/asset-modeling-create-templates/create-a-new-asset-characteristic-template.md)
{% endcontent-ref %}

### **Pause or start multiple rules at the same time**

In rule management, multiple rules can now be paused or started at the same time. This makes controlling automated processes easier and enables efficient management of rule chains. [-> Pause or start multiple rules at once](#mehrere-regeln-gleichzeitig-pausieren-oder-starten)

<figure><img src="/files/bfcfac2ab15647949d3136e11d080d550e149466" alt="" width="362"><figcaption></figcaption></figure>

### **Alarms visible in analysis charts & floor widget**

Alarms can now be visualized directly in analysis charts and displayed in the floor widget. This improves the overview and makes it easier to evaluate alarm events in the context of data analysis and building representation. [-> Show alarms in the analysis](/collection/english-v14/documentation/analytics-and-reports/use-analytics.md#alarme-in-der-analysis-anzeigen)

<figure><img src="/files/ed32208ff8e85f8776ce638525265b29a37ecc97" alt="" width="563"><figcaption></figcaption></figure>

### **Redesign of the booking widget**

In the booking widget, when selecting an asset, all existing bookings can now be displayed and managed. This provides a better overview and more efficient management of booking times.

<figure><img src="/files/a69e20e426d9f86f0bf370048858116dd3cafce5" alt="" width="360"><figcaption></figcaption></figure>

{% content-ref url="/pages/a5de30c8da9c29ac8736417ea5a670c5b474cef8" %}
[Booking](/collection/english-v14/documentation/widgets/predefined-widgets/booking.md)
{% endcontent-ref %}

### **Twig templates in Eliona – Flexible message creation**

Eliona now supports **Twig.js** for the dynamic creation of message templates. This enables flexible customization of **alarm, ticket, and email templates** with conditional statements, loops, and variables. These can also be used in **yAxis and legend templates** to customize chart labels.&#x20;

{% content-ref url="/pages/8894b3c86580a6b6b9cdac807e96502026afb725" %}
[Twig templating in Eliona](/collection/english-v14/academy/twig-templating-in-eliona.md)
{% endcontent-ref %}

### **New trending configuration for attributes**

In the **Asset Template** can now define whether historical data should be stored for attributes. There are two options:&#x20;

<div align="left"><figure><img src="/files/910ce5c67dec345c3d1f335b83f846b5c1bbb455" alt="" width="563"><figcaption></figcaption></figure></div>

* **On Change:** Values are stored only when they change.
* **Always:** Every incoming value is stored.\
  This setting enables more efficient management of **trend data** and reduces unnecessary storage.

{% content-ref url="/pages/0f2ce7ea5f2d76c610ea31d0b49825a8533707e9" %}
[Create a new template](/collection/english-v14/documentation/assets/asset-modeling-create-templates/create-a-new-template.md)
{% endcontent-ref %}

### **Advanced system settings – Improved storage management**

With this version, additional options for managing storage times and data processing have been introduced:

* **Storage time log & storage time trend** – Enables more precise control over retention periods for logs and trend data.
* **Smart Batch Mode** – Optimizes storage and processing of large amounts of data.
* **Cold storage & storage time from** – Automatic archiving of older trend data to reduce storage space.

These new settings improve the efficiency of data management and enable more flexible control over storage strategies.&#x20;

{% content-ref url="/pages/6c1ae376f41b690d1ba72e137a02dfccb369896c" %}
[System](/collection/english-v14/documentation/settings/system.md)
{% endcontent-ref %}

### **Revision of the Smart Assist menu**

The Smart Assist menu has been revised to simplify the configuration of user permissions for Smart Views and slider groups. Users can now be assigned to specific views in a targeted way and their order can be adjusted via drag & drop.

<figure><img src="/files/03f644ba2770c93866679fa5b597f6cbf26871ba" alt="" width="563"><figcaption></figcaption></figure>

{% content-ref url="/pages/39e229bc08a50da974adfd392fec0aa81ab22b1a" %}
[Smart Assist](/collection/english-v14/documentation/smart-views/smart-assist.md)
{% endcontent-ref %}

### **Improvement of the PL/PgSQL Script Engine**

The Script Engine now supports the full PL/PgSQL syntax, including the use of variables within a **DO .........** block. This allows complex SQL scripts with **DECLARE**statements and structured workflows to be executed directly in Eliona.

{% content-ref url="/pages/ae3006d00437c0fb64d1c95e25af17ef0e3a554d" %}
[Write PL/PgSQL scripts](/collection/english-v14/documentation/engineering/script-engine/write-pl-pgsql-scripts.md)
{% endcontent-ref %}

### **New configuration page for the Eliona Broker**

A dedicated **Eliona Broker**configuration page has been added. Users can there **manage SSL certificates** and **set up user accounts for the broker**to improve the security and access management for MQTT connections.

{% content-ref url="/pages/0d6a954f1cab2dd1664d6e867dc9aa610409fff6" %}
[Eliona Broker](/collection/english-v14/connectivity-as-a-service/connect-devices-with-abb-buildingpro/connect-devices-via-mqtt/eliona-broker.md)
{% endcontent-ref %}

### **Extended link options in the Smart Assist menu**

The **Links widget** has been expanded and now allows links to be associated with **Smart Views**. When clicking a link, a predefined Smart View can be opened directly, making navigation within Eliona even more intuitive.

{% content-ref url="/pages/4d9a7aede8de0c5602693e490fcf48561990bd66" %}
[Links](/collection/english-v14/documentation/widgets/predefined-widgets/links.md)
{% endcontent-ref %}

### **Alarms/rules from external sources now clearly identifiable**

Alarms originating from **external systems** are now clearly marked in the alarm overview. This makes it immediately apparent whether an alarm was triggered by an **internal rule** or an **external source** . [-> External rules](/collection/english-v14/documentation/alarms-rules-and-escalations/rules.md#externe-regeln) <img src="/files/8c6dd5cfb6c19fd89910684e046bb740b88da8ac" alt="" data-size="line">

### **New filter option for alarm analyses**

The **Alarm statistics** has been expanded with a **tag filter** . This allows alarms to be analyzed specifically by certain tags, enabling even more detailed evaluations.

{% content-ref url="/pages/02df6c9b9a00d7231757f9eac9ffd6ccf392e5e5" %}
[Alarm statistics](/collection/english-v14/documentation/alarms-rules-and-escalations/alarms/alarm-statistics.md)
{% endcontent-ref %}

### **Legacy structures cleaned up**

The old legacy linking point has been removed. This eliminates outdated structures and configuration options in order to make the platform more efficient and future-proof.

***

## **2025-03-13 - Changelog\[v13.2.4 - v13.2.58]**

In these versions, several security vulnerabilities were fixed to improve the stability and security of the system.

## **2024-12-10 - Changelog\[v13.2.3]**

In ticket details, the names of attachments are now displayed. In addition, we fixed the following issues:

* The "Task Priority" column has been removed from the task list.
* Attachments can now be added without a comment.
* UI inconsistencies in ticket templates have been eliminated.
* A bug in the display of relative time in comments has been corrected.

## **2024-12-03 - Changelog\[v13.2.2]**

We fixed a bug where the project was not displayed correctly when authentication was performed via SSO. With this adjustment, the initial project authentication was moved to the backend to improve performance and security.

## 2024-10-24 - Changelo&#x67;**\[v13.2.1]**

We fixed an issue where the loading time in the asset details was noticeably increased when the *Device Simulator App* was not installed. With this fix, the page now loads much faster.

## 2024-10-17 - Changelog\[v13.2.0]

We are pleased to present the latest version of Eliona, which is equipped with numerous new features and optimizations. The most important new features include **rule chains**, which make it possible to create automated processes based on events or time triggers, as well as the **custom home page**, which can be adapted for each project.

In addition to these highlights, the update offers further exciting improvements such as the **report table widget**, a revised **input widget** and extended functions for **data entry and editing**, which make your daily work in Eliona even more efficient.

[-> Link to the full changelog v13.2](https://deploy.eliona.io/helm/changelogs/v13.2.txt)

### Migration from ADFS to SAML SSO

With this version, we recommend migrating the ADFS app to **SAML SSO** in order to take advantage of modern authentication. Detailed instructions can be found in the [->SAML SSO documentation](/collection/english-v14/apps/apps/saml-sso.md)[.](/collection/english-v14/apps/apps/saml-sso.md)

### **rule chains**

With this version, we introduce **rule chains** as a new feature. Rule chains make it possible to create automated processes based on events or cyclical triggers. This offers flexible control options for a wide range of applications, from monitoring to process optimization.

<figure><img src="/files/f633c7f1e51222ff994faa936bb20a61f1c48a82" alt=""><figcaption></figcaption></figure>

**Important functions**:

* **Event-based and cyclical triggers**: Define when a rule is triggered—based on a data event or at fixed intervals.
* **Automated actions**: Trigger alarms, create tickets, or send emails based on defined conditions.
* **Integration of conditions and operations**: Use comparisons, delays, and logical operators (AND/OR) to implement complex decision logic.

{% content-ref url="/pages/b8b0d247ff2ff86850ef111fa57a07018d6927e3" %}
[rule chains](/collection/english-v14/documentation/alarms-rules-and-escalations/rule-chains.md)
{% endcontent-ref %}

### **Home page**

With this version, you can now define a **custom home page** for each project. This page is shown first after login or when opening the project and provides a quick overview of important information and widgets. The home page contains a **project overview** with the created elements, direct access to the **project settings**, a **map** with the project location, and a **weather widget**that shows the current weather and forecast for the location.

In addition, you can activate the home page via the project settings and add new **elements to the home page** and configure existing elements to adapt the page to your specific requirements.

<figure><img src="/files/888fc2ff70002daaa6ac627c59299c053647f555" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/22b6e6df472e42603697cfb862757281cb18a17b" %}
[Home page](/collection/english-v14/documentation/systems-and-projects/home-page.md)
{% endcontent-ref %}

### **report table widget**

With this version, the **report table widget** was introduced, which makes it possible to display data from various assets in tabular form. You can aggregate data over defined periods and calculate sums or averages. The widget offers a flexible structure that allows columns to be configured individually and content such as text, date, or numerical data to be displayed. It is particularly well suited for detailed analyses of operating hours, consumption values, or other important metrics.

<figure><img src="/files/bcdc5fd8dc5375534b892f866f064d752cad34e3" alt="" width="563"><figcaption></figcaption></figure>

{% content-ref url="/pages/f499651f68f90c1885c7ab885c8465172561ddf3" %}
[Report table](/collection/english-v14/documentation/widgets/predefined-widgets/report-table.md)
{% endcontent-ref %}

### **Extended data entry and editing functions**

With this version, the functionality for data entry and editing has been significantly expanded. You can now easily add new data entries for attributes of an asset and save them directly in the system. Each entry is assigned a current timestamp to optimize data tracking. In addition, existing historical data can be edited via a simple pencil icon. This makes it easier to correct faulty or inaccurate data.

Another new feature is **bulk editing of data**. This makes it possible to set all records within a defined period to a new value. This is particularly helpful when devices supplied incorrect data during a certain period, as you can now correct it efficiently and quickly.

These functions significantly simplify and speed up data entry and maintenance, resulting in more precise and flexible data management.

{% content-ref url="/pages/a8265b90f2c48124808df5cbebb2da460828fdbc" %}
[Asset data](/collection/english-v14/documentation/assets/asset-data.md)
{% endcontent-ref %}

### **History function for calculations**

With this version, the **history**function has been introduced, which makes it possible to access historical values of attributes. You can now use earlier values of an attribute in calculations to analyze trends or track changes over time. The syntax allows specific past values to be retrieved by using a negative value for the parameter `back_step` for example `-1` for the last value or `-2` for the second-to-last one.

This new function offers a more flexible and detailed analysis of data over time periods and makes it easier to create complex calculation chains.

{% content-ref url="/pages/4d26cefc5e906124d2bc600bec44dba25af66506" %}
[Calculate values: the calculator](/collection/english-v14/documentation/more-functions/attribute-functions/calculate-values-the-calculator.md)
{% endcontent-ref %}

### **Redesign of the input widget**

The **input widget** has been completely redesigned and now offers a much more modern design as well as improved usability. The new version is visually more appealing and significantly more intuitive to use, which makes interaction and data entry much easier.

In addition, two new functions have been introduced:

* **Enabling symbols**: The symbols of the associated attributes can now be displayed directly to improve clarity.
* **Split vertically**: With this option, the input fields can be arranged not only below one another but also next to each other, providing a more flexible and compact display.

These improvements offer greater flexibility and make working with the input widget more efficient and user-friendly.

<div align="left"><figure><img src="/files/717f14105de05d8636f1f7d9626adbab0f4245ff" alt="" width="518"><figcaption></figcaption></figure></div>

{% content-ref url="/pages/e512c07ca4fe646f348dcc6b01c1151733b8c0f4" %}
[Inputs & switches](/collection/english-v14/documentation/widgets/custom-widgets/modules/inputs-and-switches.md)
{% endcontent-ref %}

### Revision of the floor widget

The **Floor widget** has been fundamentally redesigned and now offers significantly improved functions that make it more efficient and user-friendly to use. With the new button **"Add current polygons/POIs"** all objects placed on a floor, such as polygons or points of interest, can be added to the widget with a single click. This eliminates the need to add each object manually and thus saves valuable time during setup.

<div align="left"><figure><img src="/files/0c85763676f71c1274449301c4d06c16806c3399" alt="" width="267"><figcaption></figcaption></figure></div>

In addition, the option has been introduced to switch between two view modes: the **"Simple"** and the **"Status" view**. The simple view offers a clear overview of all placed objects, while the status view allows you to keep track of the current state of these objects. This is especially useful for situations where continuous monitoring is required.

<div align="left"><figure><img src="/files/658d0b844db3d0a1b763a1e246af484efaebef66" alt="" width="274"><figcaption></figcaption></figure></div>

With these new functions, managing floor objects is significantly simplified, which both increases efficiency and flexibility in using the widget.

{% content-ref url="/pages/3c77339c39eab3b645622388787453af76e575bf" %}
[floor](/collection/english-v14/documentation/widgets/predefined-widgets/floor.md)
{% endcontent-ref %}

### **Onboarding**

With this version, an **onboarding feature** has been introduced in Eliona. This new feature provides an interactive guide that gives users an introduction to the functions of various Eliona pages when they access them for the first time.

<div align="left"><figure><img src="/files/f1792c3a3558e239b9a0e296fc3e9f6200dbe14b" alt="" width="307"><figcaption></figcaption></figure></div>

{% content-ref url="/pages/074d3c968e6c7d41a9ef76434c0e4355565eb37f" %}
[Welcome to ABB BuildingPro: An interactive introduction](/collection/english-v14/getting-started/welcome-to-abb-buildingpro-an-interactive-introduction.md)
{% endcontent-ref %}

### **Data retention period and audit log**

With this version, it is now possible to set the **retention period** for data to up to **60 months** . On request, the retention period can even be set to **unlimited** . In addition, an **audit log limit** has been introduced to manage access to log data.

{% content-ref url="/pages/6c1ae376f41b690d1ba72e137a02dfccb369896c" %}
[System](/collection/english-v14/documentation/settings/system.md)
{% endcontent-ref %}

### **GAI in asset selectors**

From now on, the **GAI (Global Asset ID)** is displayed in all asset selectors. It is also possible to search assets specifically by GAI, which makes identifying and selecting assets much easier.

## 20240920 - Changelog \[v13.1.6]

In this hotfix, we fixed a bug that caused users without permission to **users in other lists** to be unable to select the default ticket recipient when creating a ticket.

## 20240905 - Changelog \[v13.1.5]

In this update, we made several improvements and bug fixes in the areas of **Navigation**, **Digital Twin** and **Tickets** implemented:

### **General**

The **Default navigation path** is now **role-dependent**. If a role does not have access to dashboards, the dashboard is no longer automatically loaded as the default view. Instead, the **next available sidebar path** is selected, to which the role has access.

### **Digital Twin**

It is now possible to change the **asset after creating the digital twin** .\
To do this, next to the digital twin click on  <img src="/files/af60cef220cd77fe655bb0060c8e22152fe857b6" alt="" data-size="line"> and then on<img src="/files/99ad241a457f785ab6d0b5418a9ccd7069618992" alt="" data-size="line"> Alternatively, the corresponding window can be opened directly in the digital twin itself via <img src="/files/e1a8f3377a3f3c74fd59401677d46028cac6ff07" alt="" data-size="line"> . In this window, the desired asset can then be specified.

<div align="center"><figure><img src="/files/23cab92bfcb0324e6cb333f521a16cad41afd332" alt="" width="375"><figcaption></figcaption></figure></div>

The **Size of links** can now be adjusted.\
To do this, there is a new option in the digital twin under the **gear icon** <img src="/files/3059686efde9d23ef7bb8e66d1f38fee423e45e1" alt="" data-size="line"> , **"Link size"**, where the relative size of all links can be set.

<div align="center"><figure><img src="/files/c19a5f780a83a51263132d2a2d1429170c484d59" alt="" width="375"><figcaption></figcaption></figure></div>

The **Image function** in the digital twin has been expanded with some useful options. From now on, images can be conveniently dragged directly from your folder to the desired location in the digital twin using **drag-and-drop** . Once an image has been selected, it is now possible to **rotate it** <img src="/files/f6c41bf2a13f6803f8393a90fa7641cbd1cffab2" alt="" data-size="line"><img src="/files/1c2f1ed3b6de6e4a921228d4a0321433da8254e7" alt="" data-size="line"> or change the **arrangement** of the images by moving the image **in front of** <img src="/files/aaee16f232400b725c5d11f5f11ec736d838954a" alt="" data-size="line"> or **behind** <img src="/files/c6b76230d61619e47b4f5a4bf352b82d7a7d3256" alt="" data-size="line"> other images.

A particularly helpful new feature is the option  <img src="/files/dab9136faf87953c698a9ac567e3e3a19debaa79" alt="" data-size="line">, which allows the position of an image to be fixed. If this option is enabled, the image can no longer be moved accidentally - instead, only the view is moved when you drag the image. This keeps the image position unchanged and unwanted shifts are a thing of the past.

<figure><img src="/files/37b76c87c1fd69ba6db75cc96866de5b0b6001d4" alt="" width="375"><figcaption></figcaption></figure>

It is now also possible to **selected elements** with the **Del-** or **Delete key** to delete them. In addition, **selected elements** by pressing the **Esc key** can be deselected again.

### **Tickets**

In the **Tickets** some **display issues** have been fixed that previously led to visual errors. Under certain circumstances, it was not possible to **tasks** to create, which has now been fixed. Tasks can now be created again without problems.

In the **permissions** for tickets there are now additional **settings** in the **project roles**. The permissions for the **ticket list view** and the **ticket details** are now managed separately. For the **ticket details** and **tasks** there are now options to distinguish between **manage**, **write** and **read** in order to enable more differentiated assignment of rights.<br>

<figure><img src="/files/1f50d344a5c8ed32519f50ba0407d1aa4bda0cb2" alt=""><figcaption></figcaption></figure>

## 20240808 - Changelog \[v13.1.4]

In this hotfix, we fixed a bug that caused the tooltip in the dashboard to be displayed in the wrong place when there were multiple trends.

## 20240801 - Changelog \[v13.1.3]

In this hotfix, we fixed performance issues that occurred with large datasets in dashboards, analytics, and smart views. These optimizations ensure that large datasets no longer cause any problems.

## 20240719 - Changelog \[v13.1.2]

In this hotfix, we fixed a bug that prevented asset characteristics from being added in the asset template.

***

## 20240718 - Changelog \[v13.1.1]

In this hotfix, we resolved several issues:

1. The transition from the old digital twin to the new digital twin design no longer causes any problems.
2. When clicking on a link, the data overview is now displayed by default instead of the configuration view.
3. Old images are now scaled correctly.
4. It is now possible to define the view when opening the digital twin by clicking on the gear icon and selecting "Save viewport as default".

<figure><img src="/files/df7481b1d3c2154437f99cf6365c757b625f1158" alt=""><figcaption></figcaption></figure>

In addition, we fixed a bug in the input widget that displayed the wrong placeholder.

***

## 20240710 - Changelog \[v13.1.0]

We are pleased to present the latest update of Eliona, version 13.1.0. This version brings a variety of new functions and improvements that further optimize your user experience and make your workflows even more efficient. From the new wayfinding function, which enables flexible navigation through your facility, to the ability to customize email subject lines for escalated emails, to comprehensive improvements in the digital twin - Eliona v13.1.0 offers numerous enhancements and improvements specifically tailored to your needs. Read on to learn more about the exciting new features this version brings.

### Full changelog

<details>

<summary>Changelog v13.1</summary>

\##\[v13.1.0] - 10.07.24

**### Added**

Dashboard/Smart view -> SBB widget ([✓ \[Discovery\] Create react app in Eliona](https://app.asana.com/0/1200252355215223/1206904986524061/f)) \[@sti]

Dashboard/Smart view -> Alarm widget -> Detailed Alarm List ([✓ 🔵 Detailed alarm list in widgets](https://app.asana.com/0/1200252355215223/1206055204586537/f)) \[@sti]

Dashboard/Smart view -> Heatmap Tracking widget -> ([✓ \[FE\] Heatmap Tracking Element](https://app.asana.com/0/1200252355215223/1206713603771616/f)) \[@nl]

Asset Details Form -> Associated ID -> new input style for ID\`s (<https://app.asana.com/0/1200252355215223/1207169605955829/f>) \[@sti]

Sidebar -> Alarm Icon -> now showing different color depending on highest prio ([✓ \[FE\] - Alarm-Icon menu item](https://app.asana.com/0/1200252355215223/1206938387815576/f)) \[@sti]

**Wayfinding -> Users can select starting building & starting point (**[**✓ \[FE\] Link to Wayfinding View** ](https://app.asana.com/0/1200252355215223/1207370026137796/f)**) \[@nl]**

Smartview -> add smartassist /sa link ([✓ FE - Link to "/sa", real Smart Assist](https://app.asana.com/0/portfolio/1199554442331824/workload/1207160155225062)) \[@rtu]

**Engineering -> Notification Provider -> Added subject field (**[**✓ 👁️ \[FE\] OMSswiss -> Escalation subject message**](https://app.asana.com/0/1200252355215223/1207355385048172/f) **) \[@jp]**

**Asset Details -> asset categories (SB-\[ADC]) \[@jp]**

**Asset Details -> added asset rating (asset\_rating) \[@lw]**

**### Changed**

Map -> Clicking on a list item no longer opens the asset page. Highlights the position of the asset instead ([✓ \[FE\] Polygon highlighting when selected](https://app.asana.com/0/1200252355215223/1207370336841290/f)) \[@nl]

Map -> Hides asset info drawer when search is opened and vice versa ([✓ 🔵 V12 - Storey Search](https://app.asana.com/0/1182566401713025/1207343569253346/f)) \[@nl]

General -> Disable selecting an attribute for disabled asset type attributes ([✓ \[FE/BE\] - Disabled asset type attributes, should be disabled in dashboard/analytics selects... ](https://app.asana.com/0/portfolio/1199554442331824/workload/1207370336841293)) \[@rtu]

Connection -> OPCUA set enable to default true in subscriptions \[@lwa]

Weather widget -> Updated design, color scheme support \[@nl] ([✓ \[FE, REDESIGN\] Weather Widget](https://app.asana.com/0/1200252355215223/1207371310735759/f))

Login -> encrypt pw to prevent clear text in request ([✓ \[FE\] - Blowfish algo for the frontend ](https://app.asana.com/0/portfolio/1199554442331824/workload/1207370934758896)) \[@rtu]

**Tickets -> enhanced tickets with templates and default user (digital\_ticketing) \[@lw]**

**Digital Twin -> reworked DT to use Infinity board & general design improvements (dt\_update) \[@lw]**

**### Fixed**

Engineering -> Asset modeling Open asset type details after creation (BR-2804) \[@rtu]

Map -> Storey config -> Added scrollbar to the form on small screens ([✓ Storey configuration not scrollable](https://app.asana.com/0/1187198351569417/1207419472179128/f)) \[@nl]

Widgets -> Alarm Widget -> added missing tags mode select to element ([✓ Alarm Widget filter by tagMode (and/or)](https://app.asana.com/0/portfolio/1199554442331824/workload/1207416263476113)) \[@rtu]

Settings -> Audit Trail -> added missing connection and app audit trail event types [✓ Audit Trail event types missing in FE](https://app.asana.com/0/1187198351569417/1207470514484119)) \[@rtu]

Asset -> Details -> fix removing geographical and functional references ([✓ Setting parent asset to empty](https://app.asana.com/0/portfolio/1199554442331824/workload/1207479477973053)) \[@rtu]

Map -> fixed counting of alarms on the displayed area ([✓ UBS - Alarm summary counts pois hidden behind the sidebar](https://app.asana.com/0/1187198351569417/1207415320822560/f)) \[@nl]

Analytics & Reports -> fix chart series color conflicts when using multiple charts ([✓ V13 - Analytics Color](https://app.asana.com/0/portfolio/1199554442331824/workload/1207571717345415)) \[@rtu]

Analytics & Reports -> save analytics charts in "last unsaved analytics" (BR-2865) \[@rtu]

Widgets -> Time widget -> the widget displays outdated time ([✓ Time Widget not working (time shows always time when smart view was opened)](https://app.asana.com/0/1187198351569417/1207548759269773/f)) \[@nl]

Smartview -> Iframe -> added minHeight config field ([✓ Smart View Iframe in Phone view too small/no way to put in pixel height](https://app.asana.com/0/portfolio/1199554442331824/workload/1207666291694433)) \[@rtu]

Asset -> Asset Links -> remove capitalizes lowercase text transformation ([✓ \[Assets\] Word "Niagara" in the link name starts with a lowercase letter](https://app.asana.com/0/portfolio/1199554442331824/workload/1207573651627594)) \[@rtu]&#x20;

</details>

### **Wayfinding start from the building**

With the new wayfinding function, users can now start directly from the **building view** or from a **specific building**. This improvement makes it possible to flexibly choose the starting point for directions and offers user-friendly and intuitive navigation through your facility.

#### Building view

To get to the building view, simply enter your URL followed by **/wayfinding** for example: "<https://your.url.i&#x6F;**/wayfinding>\*\*". You can use this URL in your application to direct the user to the **building view** . In this view, the user can select or search for a building from which they want to start.

<figure><img src="/files/868a6ce4f9fc1e811c6ed1312f74eb80f72fcea2" alt=""><figcaption></figcaption></figure>

#### Storey view

To let a user start directly in a specific building, use the URL **/wayfinding?buildingId={id}**, where {id} is the **ID of the building** . The user is then redirected to the floor view. In this view, they can select their **starting point within the floors** or search using the collapsible search bar.

<figure><img src="/files/a161fa31196cf60f0c36bf90dc59c1679816734b" alt=""><figcaption></figcaption></figure>

Once a starting point has been selected, everything works as usual, with the only difference being that the **starting point can be changed at any time**.

<figure><img src="/files/6f8fa32197b2a816309de1ac8f02412543ac60ae" alt=""><figcaption></figcaption></figure>

### Customize email subject when emails are escalated

We are pleased to introduce a new feature: from now on, it is possible to customize the subject of escalated emails individually. You can do this in just a few steps:

1. **Navigate to Engineering > Notifications Providers > E-mail.**
2. **Edit the desired email template.**
3. **Select the "Override default" option.**
4. **Enter the desired subject in the "Subject template" field.**

<figure><img src="/files/c5f78533cca27b5bc5e38d9dc792e84d566f95d3" alt=""><figcaption></figcaption></figure>

With this new feature, you can ensure that the subject lines of your escalated emails exactly meet your requirements and make your communication even more efficient.

### New features in the digital twin

The digital twin has been extensively redesigned and now offers a variety of new functions and improvements. It is now possible to add **an unlimited number of images** . In addition, **text fields** can be added in any colors and freely scaled. The links also now offer some cool new features.

<figure><img src="/files/a678fda82bdaeb45ebd22a658726807d2a97b251" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1f144b6a86755181d13365275b63982f3ee6e290" alt=""><figcaption></figcaption></figure>

#### Linking

The links now have several options. The **shape** can be selected, a reference point defined, and a **title added** . In addition, the **values of all attributes** can be displayed in a link. The **color of the link can be adjusted depending on the value** of an attribute. Simply click on the gray-highlighted attribute and add colors in value mapping.

<figure><img src="/files/206aad7cbc591087b62a0d9f034d56aec32bd471" alt=""><figcaption></figcaption></figure>

These new functions give you more flexibility and enable a more precise and appealing presentation of your digital twin.

### **Asset characteristics**

It is now possible to add detailed information to an asset.

When editing an asset type, you now have a new window available in which comprehensive information can be added for each asset. This information can be divided into different **categories** , and for each category, **multiple fields with name, value, and unit** can be created. Of course, **translations** can also be stored for the added information.

<figure><img src="/files/4b1c1ebb4db1b7e1f9fbf185c6d1ec697a452a35" alt=""><figcaption></figcaption></figure>

Now, for each asset in the asset details, **individual values** can be entered, enabling more precise and extensive documentation and contributing to better management and use.

<figure><img src="/files/8dce90b0ad96dc50350ffa7a141a238efa76f23a" alt=""><figcaption></figcaption></figure>

These can then be expanded via "More Info".

<figure><img src="/files/01bdfbc13e14a3c0a3f6a07bd75c941f9bddde11" alt=""><figcaption></figcaption></figure>

### **Asset Rating**

With the new **Asset rating** you can now rate your assets using a **star rating system** . This feature makes it easier to assess the quality and condition of your assets and provides a quick overview of their performance and usefulness over time.

<figure><img src="/files/873f5abef7164b5d79b7735c9aace15f16002a8c" alt=""><figcaption></figcaption></figure>

Asset rating is now available under asset details. You can give your assets 1 to 5 stars and add a rating text. These ratings can be edited or deleted by their author at any time. Ratings can be sorted by date, author, or star rating for a quick overview.

### Improved tickets with template and default user

Our ticket system has been expanded and now offers numerous new functions that simplify handling, speed up processes, and at the same time provide more information.

From now on, **a reporter is filled in automatically** for every ticket, which significantly speeds up the creation process. In addition, there are now **three priority levels** available, allowing better classification and urgency assessment of tickets.

For improved clarity, **tags** can be added. In addition, it is possible to **mark tickets as templates** , which makes it easier to create recurring tickets.

<figure><img src="/files/596792c2982c9b313497d510eaa08847a1e6daf5" alt="" width="393"><figcaption></figcaption></figure>

The templates are visible when the filter **"Templates"** is activated in the ticket overview. When clicking on a template, a **pre-filled ticket**opens directly, which makes it easier to create recurring tickets.

<figure><img src="/files/bf29c095b97ba1c5b7db6ac24f4b05fdf489e345" alt=""><figcaption></figcaption></figure>

Another practical feature is the setting of a **default recipient**. This can be configured in the ticket overview by clicking on the **gear icon** . This recipient is then automatically entered when creating all tickets, enabling faster and more convenient ticket creation.

<figure><img src="/files/3cdb5a94947c02884bb657602bf5c06c6807b673" alt=""><figcaption></figcaption></figure>

## 20240507 - Changelog \[v13.0.0]

We are pleased to introduce the latest version of Eliona:&#x20;

Eliona v13.0. This version brings a variety of significant updates and new features that will greatly improve and expand your user experience. From improved tracking functions and extensive wayfinding options to a new booking system - this version offers everything you need to take your facility management and smart building solutions to the next level. Read on to learn more about the exciting new features and improvements that Eliona v13.0 has in store for you.

### Full changelog

<details>

<summary>Changelog v13.0</summary>

\# Changelog

All notable changes to this project will be documented in this file.\
\##\[X.X.X] - TBD\
\
Dashboard/Smart view -> SBB widget ([SB-08710](https://app.asana.com/0/1200252355215223/1206904986524061/f)) \[@sti]\
Dashboard/Smart view -> Alarm widget -> Detailed Alarm List ([SB-08721](https://app.asana.com/0/1200252355215223/1206055204586537/f)) \[@sti]\
Asset Details Form -> Associated ID -> new input style for id\`s ([SB-08961](https://app.asana.com/0/1200252355215223/1207169605955829/f)) \[@sti]\
Sidebar -> Alarm Icon -> now showing different color depending on highest prio ([SB-08973](https://app.asana.com/0/1200252355215223/1206938387815576/f)) \[@sti]\
\
\
\##\[v13.0.0] - 16.05.24\
\&#xNAN;**### Added**\
Map -> Tracking feature with storey/room configurations, tracking widget and dynamic asset tree ([SB-08494](https://app.asana.com/0/1200252355215223/1206713482911294/f)) \[@nl] \*\*\
Engineering -> Wayfinding -> Wayfinding editor, view and element creation (SB-08989) \[@nl] \*\*\
Engineering -> Bulk Import -> Bulk import feature (SB-08990) \[@lw] \*\*\
Map/Storey -> Booking -> Booking feature with configurations and elements (SB-08991) \[@jp] \*\*\
User -> Notification Settings -> user specific notification settings (SB-08992) \[@lw] \*\*\
Connection > Added Modbus section ([SB-07300](https://app.asana.com/0/portfolio/1199554442331824/workload/1205755518393744)) \[@lwa] \*\*\
\- Dashboard -> Public (Global) dashboards -> feature with Public dashboards folder ([SB-08283](https://app.asana.com/0/1200252355215223/1206442272144245/f)) \[@jp] \*\*\
Settings -> Api keys -> added Api key expired Frontend info ([SB-08365](https://app.asana.com/0/portfolio/1199554442331824/workload/1205844913992583)) \[@rtu]\
Scripts -> added default function to python scripts \[@lwa]<br>

**### Changed**\
\
\- Audit trail, Script engine -> store sorting config in URL ([SB-08426](https://app.asana.com/0/1200252355215223/1206579113932464/f)) \[@nl]\
\- General -> Storey & Bim redirects -> unified across whole platform ([SB-08965](https://app.asana.com/0/portfolio/1199554442331824/workload/1207171019673790)) \[@rtu]\
\- Apps -> Updated visual representation for versions ([BR-2624](https://app.asana.com/0/1187198351569417/1206896340722163/f))\[@lwa]\
\- Engineering -> Tag Management -> Remove custom flag from tags ([SB-08693](https://app.asana.com/0/portfolio/1199554442331824/workload/1206832856885856)) \[@rtu]

\
\&#xNAN;**#### Fixed 🐞**\
\- Dashboard -> Trend Element -> fixed guideline ([BR-2533](https://app.asana.com/0/portfolio/1199554442331824/workload/1206677739889403)) \[@rtu] \*\*\
\- Dashboard -> Custom widget -> table and trend element preview ([BR-2591](https://app.asana.com/0/1187198351569417/1206808231772682/f) [BR-2590](https://app.asana.com/0/1187198351569417/1206807625187469/f)) \[@nl]\
\- BIM details -> Sidebar -> fixed displaying "Tracker" list item ([BR-2587](https://app.asana.com/0/1187198351569417/1206795548002131/f))\[@nl]\
\- Connection -> Fixed redirect errors in the restful section ([BR-2593](https://app.asana.com/0/1187198351569417/1206808953568816/f)) \[@lwa]\
\- Connection -> Fixed that not created connection would test status ([BR-2592](https://app.asana.com/0/1187198351569417/1206808716071331/f)) \[@lwa]\
\- Asset -> Data -> show aggregation data for average on change mode ([BR-2597](https://app.asana.com/0/portfolio/1199554442331824/workload/1206830213335903)) \[@rtu]\
\- General -> Asset attribute select -> show separate options for average on change and cusum modes ([BR-2602](https://app.asana.com/0/1187198351569417/1206840261685318)) \[@rtu]\
\- Reporter -> Text Element -> pipelines requirement options now check actual pipeline configuration not asset type config ([BR-2605](https://app.asana.com/0/1187198351569417/1206842982206762)) \[@rtu]\
\- Settings -> Apps -> Remove required fields from adding Niagara controller dialog ([BR-2580](https://app.asana.com/0/1187198351569417/1206776141023041)) \[@rtu]\
\- General -> Asset/Attribute Select -> Remove non-existing min & max options from sum & cusum aggregation selects ([BR-2605](https://app.asana.com/0/portfolio/1199554442331824/workload/1206842982206762)- Engineering -> Asset Editor -> fix bulk asset import ([BR-2619](https://app.asana.com/0/portfolio/1199554442331824/workload/1206888522576446)) \[@rtu]\
\- General -> Asset Status -> show unmonitored asset if allowed inactivity is disabled ([BR-2440](https://app.asana.com/0/portfolio/1199554442331824/workload/1206446221783781)) \[@rtu]\
\- General -> Experts -> Mark tags where user doesn't have access to for Expert users ([SB-08367](https://app.asana.com/0/portfolio/1199554442331824/workload/1206580909208644)) \[@rtu]\
\- Smart view -> Input Widget -> transparent background buttons ([BR-2636](https://app.asana.com/0/1187198351569417/1206430901344036/f)) \[@sti]\
\- Digital twin -> Link Asset -> All Assets are linkable now ([BR-2635](https://app.asana.com/0/1187198351569417/1206917468535292/f)) \[@sti]\
\- Settings -> Apps -> InQuery-Parameters aren't submitted ([BR-2643](https://app.asana.com/0/portfolio/1199554442331824/workload/1206977527219147)) \[@rtu]\
-Dashboard -> Storey widget -> Tooltip fixed ([BR-2532](https://app.asana.com/0/1187198351569417/1206676561646395/f)) \[@sti]\
-Dashboard -> Storey widget -> preview image -> fixed image location([BR-2499](https://app.asana.com/0/1187198351569417/1206611750829297/f)) \[@sti]\
-Dashboard->Heatmap widget -> preview storey -> now showing storey instead of map ([BR-2499](https://app.asana.com/0/1187198351569417/1206611750829297/f)) \[@sti]\
-Settings -> Apps -> apps grid now fit when having different window sizes ([BR-2650](https://app.asana.com/0/1187198351569417/1206999597587058/f)) \[@sti]\
\- Login -> Fixed that version wasn't always up to date ([BR-2598](https://app.asana.com/0/1187198351569417/1206830754547357/f)) \[@lwa]\
\- Assets -> Details -> Attributes -> fixed changing attribute values and displaying them correctly ([BR-2632](https://app.asana.com/0/1187198351569417/1206921886605937/f)) \[@sti]\
-Assets -> Details -> Attributes -> calculator -> calculator now showing default from template ([BR-2628](https://app.asana.com/0/1187198351569417/1206906001111932/f)) \[@sti]\
-Alarms -> asset type definition -> disabled changing subtype ([BR-2294)](https://app.asana.com/0/1187198351569417/1206064779554772/f) \[@sti]\
-Map -> Markers -> circle markers are now on top of building markers ([BR-2670](https://app.asana.com/0/1187198351569417/1207054890235484/f)) \[@sti]\
-Analytics -> Settings -> enhance legend templating variables with aggregation props ([BR-2677](https://app.asana.com/0/portfolio/1199554442331824/workload/1207086400445912)) \[@rtu]\
\- Smart view -> fixed property that caused wrong color ([BR-2682](https://app.asana.com/0/1187198351569417/1207088122108649/f)) \[@lwa]\
\- api keys -> fixed wrong date format ([BR-2680](https://app.asana.com/0/1187198351569417/1207087102839792/f)) \[@lwa]\
-Smart View -> dynamic text -> font now correctly displayed ([BR-2684](https://app.asana.com/0/1187198351569417/1207110797258505/f)) \[@sti]\
-Smart View -> comfort -> text stays inside the box for bigger font sizes ([BR-2684](https://app.asana.com/0/1187198351569417/1207110797258505/f)) \[@sti]\
-Smart View -> image -> preview of image gets deleted when image gets deleted ([BR-2684](https://app.asana.com/0/1187198351569417/1207110797258505/f)) \[@sti]\
\- Connection -> Mqtt connections now can be disabled on the detailed page ([BR-2688](https://app.asana.com/0/1187198351569417/1207111890387378/f)) \[@lwa]\
\- Appstore -> updated UI so it's more intuitive to see if a new version is available ([BR-2624](https://app.asana.com/0/1187198351569417/1206896340722163/f)) \[@lwa]\
-Smart View -> Input -> Switch -> Switch now showing On/Off above the switch ([BR-2703](https://app.asana.com/0/1187198351569417/1207156693733571/f)) \[@sti]\
-Map -> Storey -> Poi can now be placed on polygon ([BR-2709](https://app.asana.com/0/1187198351569417/1207160070505599/f)) \[@sti]\
-Assets -> Details -> Attributes -> Filter can now be saved/deleted and it shows the saved configuration [(BR-2631)](https://app.asana.com/0/1187198351569417/1206921718715250/f) \[@sti]\
-Assets -> Details -> Attributes -> Units can be changed without error [(BR-2663](https://app.asana.com/0/1187198351569417/1207035232245285/f)) \[@sti]\
-Engineering -> Asset Modeling -> Attribute Templates -> Virtual activated saving only possible when form is filled in ([BR-2673](https://app.asana.com/0/1187198351569417/1207064731067058/f)) \[@sti]\
-Smartview -> Smartview inputs are disabled for smartview user ([BR-2712](https://app.asana.com/0/portfolio/1199554442331824/workload/1207178714585122)) \[@rtu]\
-Login page -> Remember me checkbox is removed ([BR-2138](https://app.asana.com/0/1200252355215223/1206621400368363/f)) \[@jp]\
-Smartview -> Tickets changable text styles/Trend underline now possible/Sankey bold now working/general form inconsistencies fixed ([BR-2724](https://app.asana.com/0/1187198351569417/1207220960917233/f)) \[@sti]\
-Tickets -> Comments -> when adding a comment it instantly shows your name above the comment now. ([BR-2711](https://app.asana.com/0/1187198351569417/1207178258646554/f)) \[@sti]\
-Engineering -> My Profile -> fix not showing user default location ([BR-2755](https://dev.azure.com/eliona/core/_git/frontend/pullrequest/6452)) \[@rtu]\
-Settings -> Audit trail -> Remove archived users from performed by filter ([BR-2756](https://dev.azure.com/eliona/core/_git/frontend/pullrequest/6453)) \[@rtu]

<br>

</details>

### Tracking

We are pleased to present some exciting news in the area of tracking. With the latest version, it is now possible to use the **Localino app, trackers and anchors** to create and display their locations as well as **movements live** on the floors. This functionality is supported by a new tracking widget, which even allows floors to be subdivided into individual rooms.

#### Asset modeling

In asset modeling, the new item **"Tracker"** has been added. When this is enabled, the created assets are registered as **trackers in the system**. This allows additional, arbitrary attributes to be added to a tracker, making your data even more precise and comprehensive.

<figure><img src="/files/84ecdf52b407374ef7649da1e50ccb53ffb8c4c0" alt=""><figcaption></figcaption></figure>

#### Configure asset info

You now have the option in an asset's configuration to **select a tracker**. If a tracker is selected, this asset is marked with a **blue dot** and can no longer be moved in the geographical asset structure. From now on, the **real location** of the asset, where it is found in the geographic structure. This means you can tell where the tag is just from the asset structure.

&#x20; ![](/files/4e7a9dfc416d6dcfbe8b010969a967b0c4cec68f)   ![](/files/e51e09825506b088606d8a2f31396c7a188c7445)

#### Configure Floor

There is now a new option in the floor section, "Configure floor". Here the **anchors selected** and the height of the anchors can be adjusted so that they match real-world conditions.![](/files/81ea97aaf9272ce3d68b122103cce083525b39e2)

After clicking **"Next"** a rectangle with the relative positions of the anchors is displayed. This rectangle can be freely resized and rotated so that the positions of the anchors in the **real world** match the positions on the **digital floor**.

{% embed url="<https://drive.google.com/file/d/15FbR4qRRvTXsOvzm_sT2xdjzFi35hoxA/view?usp=sharing>" %}

#### Set Up Rooms

If needed, rooms can now also be set up. This allows precise recording of which room the tag is in. This information is reflected both in the asset structure and in the tracking widget. To define a room, draw a polygon in the floor as usual and activate the option **"Set polygon as room boundaries"**. The room is then set up. ![](/files/13808a6c7044decb732798b1cbbac89a5116f1d5)

#### Tracking Widget

Of course, the new tracking configurations also include a tracking widget, which is available for both **dashboards** and the **Smart View** . Select a floor and all trackers on that floor will be displayed. At the top of the widget there is a search bar that you can use to search for trackers specifically. When a tracker is selected, **the widget follows it**. If the tracker changes room or floor, this is immediately visible in the widget.

<figure><img src="/files/6b622b620d46c92237ae9355d633bc42bb3298f0" alt=""><figcaption></figcaption></figure>

### Wayfinding

One of the major new features that has been added is wayfinding. Here it is possible to configure **cross-floor routes** and thus guide customers and employees to their destination on the **fastest route** without getting lost and without accompaniment. To record your facility, there is a new "Wayfinding" option under "Engineering".

#### Add Building

To create a building with floors, click the "+ Building" button. You can now assign names to your building and its floors and select the corresponding assets.

![](/files/bca55c3d75dffc2604575fcdc553da73d524fb57)

<figure><img src="/files/51a0b63474fa5b42fdb0587b394f26eaf59facba" alt=""><figcaption></figcaption></figure>

After saving, the individual floors can be configured. Simply expand the building and click the arrow for the desired floor.

<figure><img src="/files/b9603efe8b13edc8f88728654b28cbc2b70b3c84" alt=""><figcaption></figcaption></figure>

#### Configure Floor

To equip the floor with routes, any image of the floor can be uploaded. Now **start/destination locations, paths, elevators, and stairs can be added via drag & drop** can be added. To link them, small **blue dots** appear around the selected points. Dragging them and releasing them on another point or line links them.

{% embed url="<https://drive.google.com/file/d/1vqnOYgZTRqoe2y2biGEbFNEoWzPLbnbm/view?usp=sharing>" %}

#### Elevators and Stairs

To connect the floors with each other, stairs and elevators can be added. These can be assigned to a group. This means elevators and stairs in a group are **linked across floors,** and the fastest route via an elevator to another floor can be found.

![](/files/78f19d624f5bd3109fe3fd26a543eef3c0aa6de3)

#### QR Code

To use the set up wayfinding building, a QR code is generated for each starting point, which can simply be downloaded by selecting the point and clicking the QR code icon.

<figure><img src="/files/e5cd11b9185410e759a4ac609424773e79918da9" alt=""><figcaption></figcaption></figure>

#### Wayfinding View

When the QR code is scanned, you land in the Wayfinding View, where the starting point is the scanned asset. Here you can enter your destination in a search bar and then start on the fastest route to your destination.

In the **Smart View** there is of course also a wayfinding component. Here the start asset can be selected and the possible destinations can also be defined as desired.

{% embed url="<https://drive.google.com/file/d/1_K-p8PX2b-VoW4_bw62yK_J-xnERrnGw/view?usp=sharing>" %}

### **Booking**

A new booking system is now available and significantly improves facility management and scheduling. It is now possible to create bookable assets via our "Booking" app and book them in the new **"Booking widget"** .

#### Modeling

In asset modeling, it is now possible to activate the point **"Bookable"**&#x69;n the configuration of asset templates. This automatically creates two new attributes that are required for the booking function.

<div data-full-width="false"><figure><img src="/files/d443f7a2e2ecfeae5c105124b15c004da39a159d" alt=""><figcaption></figcaption></figure></div>

#### Make floor bookable

With the bookable assets now created, it is now possible to activate the option **"Asset can be booked"** when placing polygons or points of interest. This means the asset can now be booked in the booking widget.

<figure><img src="/files/902398859d1fdbed422a2c5fdc5af70e105d8a42" alt=""><figcaption></figcaption></figure>

#### **Booking Widget**

It is now possible in the booking widget via **"Quick Booking"** or **"Advanced Booking"** to book the desired time slots very precisely. Of course, this feature is also available in Smart Views.

{% embed url="<https://drive.google.com/file/d/1h_L7pb6U6LtHbQJIT5rQZseu4L6D1uSn/view?usp=sharing>" %}

### **Bulk Import**

It is now possible to import all desired data at once using a file. Assets, Rules, Tags, Projects, Roles, and Types can be imported.

#### Importing

For bulk import, we have added a new option in "Engineering". Here, the JSON file with the data can be uploaded very easily.

<figure><img src="/files/577f81d223872888cab8a13e85733a6f72f6b1f2" alt=""><figcaption></figcaption></figure>

If there are **errors** in the file, these will of course be displayed and can be **corrected** in the app.

<figure><img src="/files/b6014e68df2aef8933ebfae7086079897ad2ec0f" alt=""><figcaption></figcaption></figure>

The data is then displayed clearly in a table. With **"Overwrite already imported data"** existing data can be overwritten and with **"Highlight duplicated assets"** duplicate data will be highlighted. With a **double-click** individual data points can now also be edited as desired. After you have then set the checkmarks to decide which data should be imported, click **"Test Import"**&#x74;o receive feedback on whether the import will be successful. Finally, simply click "Import" and your data will be imported.

{% embed url="<https://drive.google.com/file/d/1VP0Da4daofHHv0aOBQBrzHk7X1tHXFkj/view?usp=sharing>" %}

### **Public Dashboards**

The long-awaited public dashboards are here. Now you can make your dashboards permanently visible to all participants in the project, eliminating the need for constant copying.

When creating a dashboard, you can now choose between **"User"** and **"Project"** . If you choose "User", you get the usual dashboards. If you select "Project", this dashboard is visible to everyone in the project. Public dashboards are marked with a **blue dot** . Only you can edit and delete your created "Public Dashboard".![](/files/4e11c8767b0162efdcf23705983613c82c63caf7)

### tags

With the expert role, it is possible to add or remove all tags from an asset. For better clarity, tags that the expert does not have access to are now marked with a **red dot** . In addition, the expert is always warned before removing all tags to which they have rights, thereby losing rights to the asset.

<figure><img src="/files/d154d82417a6a170bdf8590ee00a61c864eb8b7a" alt=""><figcaption></figcaption></figure>

### Analytics

In the settings of an analytics there is now a new field **"Series label format"**. Variables for aggregated values can be used in this field to customize the displayed value. {{unit}}, {{attribute}}, {{aggregatedDataField}}, {{aggregatedDataRaster}}, and {{aggregatedDataType}} are available variables for customizing the label as desired.

<figure><img src="/files/74238abc2255efc442c23a203d609f5e79124393" alt=""><figcaption></figcaption></figure>

### Digital Twin&#x20;

Previously, in the digital twin it was only possible to link assets that were sub-assets. With the new version, it is now possible to link all **assets in a digital twin**.

### floor

It is now possible without any problems to set **points on polygons** .

### Login

We fixed a bug that caused the displayed version not to always be the latest. Now the **correct version** is always displayed.

Also, since it was more of a nuisance, we removed the **"Remember me" box** . We will now remember you by default when logging in.

### Calculator

The calculator in the attribute form of an asset now takes over and displays the **default calculation** entered in "Asset Modeling".

In addition, there are no longer any problems with calculations with **more than 7 variables**. All your calculations now work with any number of variables.

### Data

If the aggregation of an attribute is set to **"average on change"** , this data is now visible in the data of an asset. To do this, simply click on the **small clock** .<img src="/files/4355e507155ea21d2ded98579d912970f83b6725" alt="" data-size="original">

### **Modbus Connection**

Modbus is a time-tested communication protocol. You can now connect your Modbus devices to Eliona under **Connection -> Modbus** .

### **API keys with expiry information**

API keys now show the **expiration date** for better management and display when a key has expired.

<figure><img src="/files/5d51bf916e8bbb409af28785fbdf8d8fac431e6c" alt=""><figcaption></figcaption></figure>

### Notification Settings

It is now possible to personalize notifications. In your **profile under "Notification settings"** you can select in great detail which notifications you want to receive.

<figure><img src="/files/8a2e26cc1d01c588a6f24e084de01283be8a0112" alt=""><figcaption></figcaption></figure>

***

## 20240304 - Changelog \[v.12.1]

We are pleased to introduce the latest version of Eliona: Eliona v12.1.

In this release, we fixed many smaller bugs. We present the most important changes in detail here. A complete list of all changes can be found below.

### [↗ Widget “Floor”](/collection/english-v14/documentation/widgets/predefined-widgets/floor.md):&#x20;

We fixed a bug that caused the “Zoom in / Zoom out” buttons to cover the “More options” menu item.

### [↗ Digital Twin](/collection/english-v14/documentation/digital-twin.md):&#x20;

We fixed a bug that could prevent images from being uploaded to the Digital Twin

### [↗ Slider](/collection/english-v14/documentation/smart-views/slider-groups.md):&#x20;

We fixed a bug that could cause trends not to be displayed in the slider.

### [↗ Map](/collection/english-v14/documentation/map-and-floor/map.md)&#x20;

We fixed a bug that caused alarm indicators not to be displayed above the map icons in the sidebar of the “Map” menu when an alarm was present.

### [↗ Alarms](/collection/english-v14/documentation/alarms-rules-and-escalations/alarms.md)

We fixed a bug that caused the “Heatmap” field to be displayed incorrectly in alarm statistics.

### [↗ Roles](/collection/english-v14/documentation/roles.md)

The predefined role “Leicom” has been removed.

### [↗ Script Engine](/collection/english-v14/documentation/engineering/script-engine.md)

We closed a security vulnerability related to the script engine

### [↗ Escalations](/collection/english-v14/documentation/alarms-rules-and-escalations/escalations.md)&#x20;

If alarms were to be escalated by email and a custom template was used for the email, the email might not have been delivered if the template used was faulty.&#x20;

This behavior has been changed. From now on, such emails will also be sent if a faulty template is present. In this case, the default template will be used instead.

### Full changelog

<details>

<summary>Changelog v12.1</summary>

**Database**\
\## \[v12.1.0] - 2024-03-04

\- hardcoded role "leicom" no longer exists \[@al]\
\- privileges divided into owner and user of the database objects \[@al]\
\- heap tuples created together with asset \[@les]\
\- fix for replication and publication of tables \[@al]

\## \[v12.0.2] - 2024-02-09 (intermediate for v12.1.0)

\- fixed security issues with customer scripts (app role) \[@al]\
\- fixed policy for assets that allows all projects to which the user is assigned \[@al]\
\- better performance for heap notify trigger \[@al]\
\- the pipeline trigger is only activated if "his" flag is set \[@al]

\## \[v12.0.1] - 2024-02-28

\- hotfix for "api" privilege to audit.heap \[@al]\
\- trigger for tags changed to increase performance \[@al]

**Frontend**\
\## \[v12.0.1] - 2024-03-04

\### Changed\
opcua -> improved section, added namespaces, better connection status feedback and improved variable naming (SB-08156) \[@lwa]

\#### **Fixed** ![:marienkäfer\_1:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f41e.png)

\- Digital Twin -> fixed, image uploading BR-2452 \[@nl] \*\*\
\- Digital Twin -> fixed, initial placement of the image on small screens BR-2524 \[@nl]\
\- Connection/Engineering/Settings -> fixed, opening sections in new tabs BR-2453\[@nl]\
\- Alarm Notifications -> fixed, notifications remain after logout BR-2437\[@nl]\
\- Widget details -> Value tiles -> fixed attribute name displaying in the preview BR-2445 \[@nl]\
\- Slider -> fixed showing asset data in slider views BR-2459 \[@rtu] \*\*\
\- Apps -> fixed that payload would only contain name BR-2356 \[@lw]\
\- Filters -> fixed that filter info wouldn't get sent to the server \[@lw]\
\- Apps -> Fixed that not initzialized apps but installed apps couldn't be uninstalled (BR-2356) \[@lwa]\
\- Widgets -> Input widget -> Fixed: attribute value changing doesn't work when one of the attributes in the widget configuration is removed (BR-2458) \[@nl]\
\- Map -> Missing alarm icons in sidebar / assets tree (BR-2461) \[@nl] \*\*\
\- Escalation -> Can't add "Slack" target (BR-2465) \[@nl]\
\- Dashboard -> Value tiles -> fix value tiles description (BR-2467) \[@rtu]\
\- Dashboard/Smartview -> Calendar -> fix underlapped tooltip (BR-2462) \[@rtu]\
\- Password reset -> Fixed (BR-2468)\[@nl]\
\- Smartview -> fix chart range for aggregated bar values (BR-2489) \[@rtu]\
\- Engineering -> Notification Providers -> Email -> fix inital auth configuration (BR-2471) \[@rtu]\
\- Bookmarks -> Can't select a user to add a bookmark to them \[BR-2500]\(@nl)\
\- Dashboard -> Storey widget -> Map controls cover widget context menu button (BR-2497)\[@nl] \*\
\- Map -> Storey -> Updates the attribute values of selected assets only (BR-2498)\[@nl]\
\- Dashboards -> Breadcrums -> fix folder navigation to dashboard list (BR-2503) \[@rtu]\
\- My Profile -> Password reset -> fix dialog behaviour on closing the dialog (BR-2509) \[@rtu]\
\- Alarms -> Alarm STatistics -> Use selected date range for the heatmap (BR-2506) \[@rtu] \*\
\- Rules -> Rule Details -> fix cancel button behaviour to navigate back in history (BR-2507) \[@rtu]\
\- Asset -> exclude subtype output from validty check and time to inactivity  (BR-2496) \[@rtu]\
\- Asset -> Details add link from asset type to asset modelin (BR-2493) \[@rtu]\
\- Tag Management -> Users -> adding tags to users depends on project tag accees or expert mode (BR-2516) \[@rtu]\
\- General -> Datapoint select -> fix select options for avg-on-change ag options \[BR-2531] (@rtu)

**Escalation**\
\## \[v12.0.2] - 2024-02-26

\- hotfix for checking the HTML validity in the mail template \[@al]

\## \[v12.0.1] - 2024-02-06

\- hotfix for handling the default HTML template \[@al]

**Jobsync**\
\## \[v12.0.1] - 2024-02-09

\- Fixed a deadlock occurring during kafka broker failure

**Url-bridge**\
\## \[v12.0.1] - 2024-02-13

\- Fixed bug causing jobs to fail when proxy is not defined

**Webhook**\
\## \[v12.0.1] - 2024-02-13

\- Modified auth sequence

**Adfs**\
\## \[v12.0.3] - 2023-02-22&#x20;

\- customizable error page in case of failed login \[@csa]\
&#x20;\- database code w/o hardcoded "leicom" user \[@al]

\## \[v12.0.1] - 2023-02-12- enable attribute mapping for permissions and language \[@csa]\
\- restart if config changes \[@csa]

**Equinix**\
\## \[v11.1.1] - 2023-12-01

\### **Added** ![:rakete:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f680.png)\
&#x20;\- Map all Equinix status strings to numbers \[@csa]\
&#x20;\- Add attribute mapping for numbers \[@csa]\
&#x20;\- Importer over APIv2 instead DB connection \[@csa]### Fixed\
&#x20;\- IBX Assets API endpoint \[@csa]

**Niagara**\
V12.0.1\
\[fix] access config update

**Webpusher**\
\## \[v12.0.1] - 2024-05-02

\- Schema creation enforced \[@les]\
\- Fixed user\_id extraction from events \[@les]

**Xovis**\
\## \[v12.1.0] - 2023-02-12\
&#x20;\- remove user leicom from db init \[@al]

\## \[v12.0.1] - 2023-02-12\
&#x20;\- upsert data over APIv2 \[@csa]

</details>

## 20240130 - Changelog \[v12.0.0]

We are pleased to present the latest version of Eliona.

Eliona v12.0.0 is a major step forward and introduces important new features, such as the App Store. But many small improvements also ensure that working with Eliona becomes more intuitive than ever before.

The first thing you will notice in this version is the new design: we have modernized Eliona's appearance and made it even more user-friendly.

But that is by no means all. Many new features are waiting for you to try them out! In this post, we present the most important changes in detail. A complete list of all changes can be found at the end of this post.

### [↗ Connections](/collection/english-v14/connectivity-as-a-service/connect-devices-with-abb-buildingpro.md): MQTT Publishing

With Eliona v12.0.0, it is now possible to publish MQTT messages. This allows Eliona to integrate even more deeply into your infrastructure and be used even more flexibly.

### App Store

With the Eliona Marketplace, we provide a curated range of dozens of apps. Apps are tailored to individual use cases and expert systems and automatically integrate incoming data from third-party sources into Eliona.

Apps are much more than ordinary integrations: an installed app independently creates all required assets and includes individual dashboards. These enable users to interact smoothly with external systems in a higher-level application.

Apps make Eliona an open, modular platform that bundles a wide variety of complex expert systems into a single, familiar environment with optimized usability and well-thought-out application concepts.

So that the right app can be found for every conceivable scenario, Eliona makes all necessary information openly and free of charge available via GitHub. With little effort, you can create your own apps and adapt Eliona to the specific requirements of your infrastructure.

[↗ Learn more about apps](/collection/english-v14/apps/apps.md)

### [↗ Tags](/collection/english-v14/documentation/tags.md): Categories

The tag functionality has been significantly expanded. From now on, it is possible to organize tags into categories. Categories can be marked as favorites and arranged in sequences. These categories can be used to control which tags appear in the alarm overview.

↗ Learn more about tags

### [↗ Alarms](/collection/english-v14/documentation/alarms-rules-and-escalations/alarms.md): Revised interface

The alarm overview has been revised and the following changes have been made:

#### Visual notifications

When an alarm is triggered, visual notifications are now displayed in addition to the notification sound. This notification remains on the screen until it is dismissed. This introduces additional redundancy, because existing alarms are immediately visible even if the notification sound was missed.

#### New columns «GAI» and «Value»

From now on, the alarm overview shows the GAI of the affected asset, as well as the value.

#### Columns can be individually arranged, shown, and hidden

{% embed url="<https://drive.google.com/file/d/1jYzURlF-enwVfXIBqCrFkfQvu2FGVyT0/view?usp=share_link>" %}

Using the “Columns” button, the columns in the alarm overview can now be arranged as desired. Columns can also be shown and hidden.

#### Column “Message”

{% embed url="<https://drive.google.com/file/d/1x6tp4RQvftg1JoXyUJecZMB3ZZ_nS9B3/view?usp=share_link>" %}

The “Message” column now shows more content. The content of this column is not truncated. If there is more content than can be displayed, the message can be scrolled.

#### Column “Tags”

In the alarm overview, only tags that are in categories are now displayed. The order in which the tags are displayed depends on their position in the sequence.

You can still see all tags if you activate the «Detailed view».

### [↗ Navigation](/collection/english-v14/foreword/controls.md): Various changes

Some improvements have been made to navigation in Eliona:

#### Breadcrumbs

From now on, a «breadcrumb» element appears in the context bar. This element lets you immediately see your exact position in Eliona and quickly navigate to higher-level menus.

#### Filters are retained when changing pages

{% embed url="<https://drive.google.com/file/d/1yAFSk4MOxd2xFnRT4yRaJfYr5Ua4dmRT/view?usp=sharing>" %}

If you search a list, e.g. the assets overview, using filters, your selected filters will now be retained when you select an entry and then return to the overview.

#### The Eliona internal «Back» button has been removed

In order for the above-mentioned retention of filters to work, the browser’s «Back» button must be used. Therefore, we have removed Eliona’s internal «Back» button.

#### Mute is now displayed

<div data-full-width="true"><figure><img src="/files/e09812b0bc8be27e8c420aba8b3cdc114a9d601f" alt=""><figcaption></figcaption></figure></div>

If you mute notifications in Eliona, this is now shown in the corresponding icon.

### [↗ Rules](/collection/english-v14/documentation/alarms-rules-and-escalations/rules.md): Asset Validity

We have added a new type of rule: *Asset Validity*. With this type of rule, you can be notified when the status of an asset changes.

[↗ Learn more about asset status ](/collection/english-v14/documentation/assets/asset-status-active-inactive-unmonitored-assets.md)

### [↗ Roles](/collection/english-v14/documentation/roles.md): Users in other lists

We have created a new option in the project roles: *See users in other lists*. Previously, users who did not have access to the "Users" option in your system role could not see user names in various places in Eliona, e.g. in tickets. With this option, users can now see the names of other users even if they do not have access to the “Users” menu.

### Calculator: values from other assets

Values from another asset can now be included in the calculator.

### Fixed bugs

#### Automatic log-out on dynamic pages

Previously, users received no new data on dynamic pages, e.g. the alarm overview, after 8 hours. This was not immediately apparent to users because they were not logged out, and could therefore lead to misunderstandings.

The behavior has been changed: users are now automatically logged out after 10 hours.

#### Inconsistencies in the licenses

A bug that caused inconsistencies in the display of license costs has been fixed.

#### Connections: Crashes with MQTT, OPC UA, and Kafka

A bug has been fixed that could cause Eliona to crash under certain conditions when the connection methods «MQTT», «OPC UA», and «Kafka» were called.

#### Widgets: Incorrect display in «Trend with bars»

The widget «Trend with bars» could display incorrect content under certain conditions. This bug has been fixed.

#### Widgets: Automatic refresh in the «iFrame» widget disabled

The «iFrame» widget refreshed automatically every 5 minutes by default. Changes made in this widget were lost after these 5 minutes. This behavior has been changed; automatic refresh is now disabled.

#### Assets: Incorrect display of images

If images were uploaded via macOS or iOS and assigned to assets, it could happen that these images were displayed incorrectly oriented. This bug has been fixed.

## 20240112 – Changelog \[v11.1.8]

### \[v11.1.8]

* fixed notification issues

### \[v11.1.7]

* fixed ACL issues
* hotfix kafka partinioner, alarm prios

### \[v11.1.6]

* added filter to calculator (pre-release)
* hotfix delete listener

### \[v11.1.5]

* hotfix for valid flag
* hotfix alarm rules insertion

### \[v11.1.4]

* fixed privileges for schema "public"
* fixed upsert\_heap\_direct() for calculator
* Dashboard -> Widget -> Value variant Tiles -> show configured element descriptions
* hotfix output subtype

## 20231130 – Changelog \[v11.1.3]

We are pleased to present eliona v11.1.3. With this hotfix, we have made Eliona a bit better again and fixed various bugs.

We would like to present the most important changes in detail here.

> You can find the complete changelog at the end of this post.

### We have fixed the following bugs:

* A crash could occur when an asset attribute was selected in the calculator for which no translation was available. We fixed this bug.
* When an asset attribute was selected in the calculator for which no translation was available, the attribute class was displayed instead of the original attribute name (without translation). We fixed this bug. From now on, the original, untranslated attribute name will be displayed in such cases.
* When an asset attribute was displayed in a sidebar for which no translation was available, the attribute class was displayed instead of the original attribute name (without translation). We fixed this bug. From now on, the original, untranslated attribute name will be displayed in such cases.
* We have ensured that bar charts in widgets are displayed correctly again.

### We introduced the following new features:

* Data retrieved via apiv2 can now be used in the calculator.

### Full changelog \[English]

<details>

<summary>Changelog v11.1.3</summary>

### \[v11.1.3] - 2023-11-27

#### Fixed 🐞

* Asset -> Details -> Prevent attribute calculator crash and show attribute name as fallback (BR-2208) \[@rtu]
* General -> Detailed Sidebar -> Show Attribute name not type as fallback (BR-2259) \[@rtu]
* Widget/Smart Assist -> Trend Element -> Fix Bar Chart Trends in bar variant (SB-07610/BR-2086) \[@rtu] Heap events with „source“, older reporter patch amended, Azure-setup cleaned up Database

### \[v11.1.3] - 2023-11-23

#### Changed

Heap events with „source“, older reporter patch amended, Azure-setup cleaned up \[@al] Apiv2

### \[v11.1.1] - 2023-11-28

#### Changed

Integrate Kafka for PUT /data \[@ag] Alarm-Check

### \[v11.1.2] - 2023-11-24

Fixed a bug causing alarm rules not to be updated in some cases \[@les]

</details>

### Report bugs

You can report bugs to us at any time using the following form:&#x20;

{% embed url="<https://form.asana.com/?d=4655289679314&k=WtF5jUfVMiI3mLVGdN3FTg&origin=embed>" %}

## 20231107 – Changelog \[v11.1.2]

In this hotfix, we fixed a bug that could cause a crash when the "Niagara" app is configured.

## 20231106 – Changelog \[v11.1.1]

In this hotfix, we fixed a bug that could cause incorrect display in the asset list.&#x20;

## 20231027 – Changelog \[v11.1.0]

We are pleased to present the latest version of eliona. We mainly used version 11.1.0 to make optimizations to ACL – our comprehensive new system for managing user permissions.

In addition, we have made many small but fine improvements and introduced new features that will make using eliona even more enjoyable.

We would like to present some of the changes made in this release in a little more detail:

### New features&#x20;

#### [-> Notifications](/collection/english-v14/documentation/notifications.md):&#x20;

Notifications for alarms can now be delivered with sound.

#### [-> ACL](#acl)

We have made Eliona’s internal logic regarding ACL more transparent for users. Since the introduction of ACL, it can happen that users want to interact with assets for which they do not have permission, e.g. because access to a parent asset is missing. In these cases, the corresponding menu options are displayed in grey. If an attempt is nevertheless made to interact with an asset for which there is no access, an information message appears that clearly explains to the user why a desired action cannot be carried out.

### Changes

#### [-> Alarms](/collection/english-v14/documentation/alarms-rules-and-escalations/alarms.md)

The Alarms menu now opens in a compact view by default. This responds to a request expressed by many users. The detailed view remains available, of course. As usual, you can switch back and forth between the two views using a toggle. As long as you are logged in, Eliona remembers the last selected state.

#### [-> Analytics](/collection/english-v14/documentation/analytics-and-reports.md)

We have made Analytics even more detailed. From now on, in an analytic you can also define times within the date range for the start and end dates.

#### [-> Assets](/collection/english-v14/documentation/assets.md)

We have further optimized the asset creation process. From now on, you can assign tags directly when creating an asset.

#### Script Engine

The script engine is moving from Settings to the "Engineering" menu

### Fixed bugs&#x20;

* Negative values could not be entered in Value Mapping. This bug has been fixed. From now on, it is possible to specify negative values in Value Mapping.
* Users could accidentally remove permissions for an asset from themselves by deleting the tags of that asset. This has been fixed.
* [-> Floors](/collection/english-v14/documentation/map-and-floor/floor.md): A bug was fixed that made it impossible to upload new floor plans.
* Widgets: A bug was fixed that caused incorrect display of alarms in the widget title bar.

This was just a small overview of the improvements we have made for you. You can find the full changelog, including all fixed bugs, below.&#x20;

<details>

<summary>Full changelog [v11.1.0]</summary>

## **Changed**

* Settings -> Scripts -> Moved to the Engineering section (SB-06945) \[@nl]
* Alarms -> Compact view, changed to detailed view and inverted behaviour (SB-07251)\[@rtu]
* Analytics -> changed custom date range to support time ranges (SB-07185) \[@rtu]
* Smartview -> Updated browser title BR-2120 \[@nl]
* Asset -> List -> widen tag column width (SB-07184 ) \[@rtu]

## Added&#x20;

* Users -> Add User dialog -> Error message when creating user with existing email of archived user (BR-1989) \[@rtu]
* Assets -> Add asset dialog -> Add new field with role tags selector, the same as on the detailed page of the asset (SB-06951) \[@jp]
* Apps -> Xovis -> Enhance configuration with advances and new optional fields (SB-06656) \[@rtu]
* Assets -> added tooltips that explain ACL restrictions BR-2050 \[@nl]
* General -> Go To Alarms shows all alarms include child asset alarms (SB-07238) \[@rtu]
* General -> Sound notifications about new alarms SB-07239 \[@nl]
* Settings -> Audit trail -> Enhance Audit trail with connection points (SB-07376) \[@rtu]

## Fixed

* Rules -> List -> Filter list by keyword (BR-2003) \[@rtu]
* My Profile -> My Profile page isn't available for users without Eliona.Users permissions (BR-2023) \[@nl]
* Engineering -> Escalation -> Add Target Dialog -> Impossible to close "Data isn't saved" warning dialog (BR-2018) \[@nl]
* Assets -> Archives asset's children only from the active tree (BR-2031) \[@nl]
* Tickets -> List -> showing archived references for main assets (BR-2027) \[@rtu]
* Apps -> Generic App Frontend -> prevent crash when app json config missed ref params (BR-1845) \[@rtu]
* Widgets -> General Header -> show highest prio of primary asset alarms and use colorblind friendly icons (BR-2033) \[@rtu]
* Widgets -> Link & Storey -> fix weird behaviours when using elements in custom widgets (BR-1954) \[@rtu]
* Widget -> Ticket -> Fix ticket count  (BR-2043) \[@rtu]
* General -> Asset Attributes -> remove capitalizing of asset attributes (BR-2020) \[@rtu]
* General -> Folder Tables -> fix crashing of page when sorting for entries that don't have a name (BR-2036) \[@rtu]
* Digital Twin -> show go to alarms link & update changing output values in sidebar (BR-2037,BR-2038) \[@rtu]
* Widget -> Input -> Select -> fixed inability to set new value if value is null
* Assets -> possibility to archive assets in func tree if it's forbidden in the loc tree and vice versa BR-2050 \[@nl]
* Alarms -> Go to Rules doesn't work correctly BR-2088 \[@nl]
* Engineering -> Asset Modeling -> Attribute config -> Value mapping accepts negative numbers BR-2085 \[@nl]
* Engineering -> Notification Providers -> Templates -> disable save button for empty templates (BR-2102) \[@rtu]
* Analytics & Reports -> Reports -> fix date time input validation (BR-2057) \[@rtu]
* Digital Twin -> Links -> allow configuring attributes of all subtypes (BR-2043) \[@rtu]
* Tickets -> List -> fix toolbar filter count for open & closed tickets (BR-2080 ) \[rtu]
* Tickets -> Detail -> fix sorting of tasks by their asset name (BR-2083) \[@rtu]
* Assets management, Tags management -> a user can't save an asset with a list of tags that will forbid the user access to this asset  BR-2059 @nl
* Widgets -> Trend -> prevent tooltip from overlapping charts BR-2096 \[@nl]
* &#x20;Smartview -> Storey widget -> Label of the archived asset isn't displayed in the widget form BR-2119 \[@nl]
* Assets -> Asset Data -> Useless comma removed from the table BR-2121 \[@nl]
* General -> Dashboard/Smartview Table element -> show datapoint description in variant "multiple" (BR-2066) \[@rtu]
* Map -> Placement -> Storey -> layout image updating doesn't work properly BR-2129 \[@nl]
* Assets -> Create/Edit asset -> The form saves asset changes even if there is a conflict error caused by associated ids BR-2100 \[@nl]
* Alarms -> Statistic -> change weekly alarm chart to support 8 days (BR-1928) \[@rtu]

</details>

## 20230925 - Changelog \[v11.0.0]

<details>

<summary>Overview </summary>

**Added** 🚀

* Roles -> ACL function for managing individual roles
* PKI/SSL -> Page for managing certificates added&#x20;
* General -> Archived references to assets and users on all entities

**Fixed bugs** ![:marienkäfer\_1:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f41e.png)

* Settings -> Apps -> Missing error snackbar added in the Generic App Frontend
* General -> Redirect after login fixed to preserve search parameters
* Floor -> Bug fix for Polygon and Pio Value Mapping colors
* Map -> Asset Detail -> "Go to floor" link fixed&#x20;
* App Topbar -> Project Logo -> issue with flashing images fixed
* Project Details -> Project Logo -> issue fixed where the image was not displayed
* Widgets -> Input Widget -> It is now no longer possible to select attributes without an "Output" subtype in the "Setpoint" field of the Input Widget form&#x20;
* Settings -> System -> The eliona logo is now used as the default system logo&#x20;

</details>

We are pleased to present the latest version of eliona!

With this version, we are introducing a remarkable new feature – the **Access Control List (ACL)**&#x20;

ACL is revolutionizing the assignment of access rights in eliona.

ACL allows administrators and system owners to customize users' rights in detail. It is now possible to grant or deny users read and write access to every function in eliona. Parts of eliona can even be completely hidden from certain users. This enables distraction-free work and maximum discretion.

At the same time, ACL enables the management of user groups.

In addition to ACL, there are the following other new features:

* [SSL](#ssl)
* [References to archived assets](#verweise-auf-archivierte-entitaeten)

### ACL

<figure><img src="/files/ddd5ca70bdf8e9f6d7161702a8821ba891ae138c" alt=""><figcaption><p>A look into a role</p></figcaption></figure>

#### How does ACL work?

Access rights are controlled via so-called “roles”. You create a role and configure read permissions and write permissions in that role. You then assign this role to one or more users. Users with this role may then only perform those actions that the role allows them to perform. By assigning a role to multiple users, you can quickly and easily create user groups in this way.

#### Read permission and write permission

For each individual role, you can define read permissions and write permissions.

**Read permission**

If read permission has been granted, users can see entries and menu items, but cannot change them.

If no read permission has been granted, users CANNOT see entries.

By not granting read permissions, you can completely hide individual menu items from users.

**Write permission**

If write permission has been granted, a user can enter values, delete objects, and create new ones.

#### System roles vs project roles

There are 2 types of roles: project roles and system roles. It is important to understand the difference between project roles and system roles.

**system roles**

The settings in system roles control permissions for options that apply system-wide. The options controlled by this role remain the same in all projects.

**project roles**

Project roles apply per project and control project-specific permissions, e.g. access to certain assets.

#### User groups

One advantage of our role-based permission system is the ability to create user groups. All members of this user group then have the same rights.&#x20;

Simply assign a role to multiple users to give multiple users the same rights.

In our [documentation](/collection/english-v14/documentation/roles.md) we have described in detail how to use this feature!

### Private Access Key

We have added a separate page where you can manage certificates.

<figure><img src="/files/c6a2ae32b236794e2d151118b5e8bbbf9df8365e" alt=""><figcaption><p>Distribute certificates</p></figcaption></figure>

You can find the page under *Connection -> PKI -> Certificates*

### References to archived entities

We have changed how eliona displays references to archived entities (e.g. assets or users).

Previously, eliona behaved as follows: If, for example, a ticket referred to an archived entity (e.g. an asset or a user), the name of the archived entity was not displayed.

<figure><img src="/files/fa5fbbbbe92d449fcd24133470c70cc77e971970" alt=""><figcaption><p>Previously, references to deleted entities were displayed like this.</p></figcaption></figure>

From now on, eliona displays the names of archived entities. In addition, archived entities are marked as such with a symbol.

<figure><img src="/files/399d2e6e6abff03c5f4b26a1bb1978a90e07167f" alt=""><figcaption><p>From now on, archived entities are displayed with names</p></figcaption></figure>

Don't forget that you can reactivate archived entities at any time!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.buildings.ability.abb/collection/english-v14/new-features/changelog-current-version-v14.2.5.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
