Merge branch 'staging/4.3' into release/4.3

Author: ashvayka

_includes/docs/device-library/guides/sensy32.md

@@ -12,16 +12,11 @@
 
 ## Introduction
 
-![{{deviceName}}](https://img.thingsboard.io/devices-library/{{page.deviceImageFileName}}){: style="float: left; max-width: 200px; max-height: 200px; margin: 0px 10px 0px 0px"}
 [The Sensy32]({{deviceVendorLink}}){: target="_blank"} is an IoT board designed for sensor enthusiasts, developers, and IoT creators.   
 Powered by ESP32-S3 and packed with a wide array of sensors, it enables seamless monitoring, analysis, and visualization of real-world data.   
 
-<br>
-
 The Sensy32 supports Wi-Fi and Bluetooth connectivity, complemented by two USB Type-C ports that enable charging and power supply, programming and firmware uploads, data communication, peripheral connectivity, and powering external devices such as sensors.
 
-<br>
-
 The Sensy32 board includes the following components and sensors:
 - UV Light Sensor
 - IR Motion and Human Presence Sensor

_includes/docs/user-guide/advanced-guides-for-working-with-dashboard/advanced-dashboard-guide-lesson-4.md

@@ -27,22 +27,23 @@ In addition to real-time processing, ThingsBoard supports calculated field [repr
 
 ### Creating a calculated field
 
-The process of creating a calculated field is the same for [Devices](/docs/pe/user-guide/ui/devices/){:target="_blank"}, [Assets](/docs/pe/user-guide/ui/assets/){:target="_blank"}, [Device profiles](/docs/pe/user-guide/device-profiles/){:target="_blank"}, or [Asset profiles](http://10.7.1.72:4000/docs/pe/user-guide/asset-profiles/){:target="_blank"}.
+> The process of creating a calculated field is the same for [Devices](/docs/{{docsPrefix}}user-guide/ui/devices/){:target="_blank"}, [Assets](/docs/{{docsPrefix}}user-guide/ui/assets/){:target="_blank"}, [Device profiles](/docs/{{docsPrefix}}user-guide/device-profiles/){:target="_blank"}, or [Asset profiles](/docs/{{docsPrefix}}user-guide/asset-profiles/){:target="_blank"}.
 
 - Open the "Calculated fields" page from the left-hand menu.
-- Click "+" ⇾ "Create new calculated field".
+- Click the "**+**" button in the top-right corner.
+- Select **Create new calculated field** from the dropdown menu.
 
 {% assign createCalculatedFieldCE = '
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/create-new-calculated-field-1-ce.png
-        title: Open the **Calculated fields** page from the left-hand menu.<br>Click **+** &#8702; **Create new calculated field**.
+        title: Open the **Calculated fields** page from the left-hand menu.<br>Click the "**+**" button in the top-right corner and select **Create new calculated field** from the dropdown menu.
 '
 %}
 
 {% assign createCalculatedFieldPE = '
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/create-new-calculated-field-1-pe.png
-        title: Open the **Calculated fields** page from the left-hand menu.<br>Click **+** &#8702; **Create new calculated field**.
+        title: Open the **Calculated fields** page from the left-hand menu.<br>Click the "**+**" button in the top-right corner and select **Create new calculated field** from the dropdown menu.
 '
 %}
 
@@ -189,7 +190,7 @@ The result can be stored as:
 
 ThingsBoard provides built-in tools that help you validate and troubleshoot calculated fields in real time.
 
-<br><b><font size="3">Enable debug mode</font></b> (_&#42; recommended during development_)
+<b><font size="3">Enable debug mode</font></b> (_&#42; recommended during development_)
 
 Each calculated field can be switched to Debug mode. When enabled, ThingsBoard records execution details for every run, including the input arguments that triggered the execution (e.g. incoming telemetry or attribute updates) and the calculation result or any execution problems (script errors, missing arguments, invalid values).
 
@@ -657,26 +658,20 @@ You can **export** the calculated field to a JSON file and **import** it into th
 
 <br><b><font size="4">Export calculated field</font></b>
 
-A calculated field can be exported either from the global **Calculated fields page** or from the **Calculated fields tab** of the target **entity or profile** to which the field is applied.   
-Click the **Export** button located in the corresponding calculated field row.
+- Navigate to the **Calculated fields** page.
+- Click the **Export** button located in the corresponding calculated field row. 
 
 {% assign exportCalculatedFieldCE = '
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/export-calculated-field-1-ce.png,
-        title: Navigate to the <b>Calculated fields</b> page and click the <b>Export<b> button located in the row of the specific calculated field.
-    ===
-        image: https://img.thingsboard.io/user-guide/calculated-fields/export-calculated-field-2-ce.png,
-        title: Navigate to the <b>Calculated fields</b> tab of the target entity or profile and click the <b>Export<b> button located in the row of the specific calculated field.
+        title: Navigate to the <b>Calculated fields</b> page and click the <b>Export</b> button located in the row of the specific calculated field.
 '
 %}
 
 {% assign exportCalculatedFieldPE = '
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/export-calculated-field-1-pe.png,
-        title: Navigate to the <b>Calculated fields</b> page and click the <b>Export<b> button located in the row of the specific calculated field.
-    ===
-        image: https://img.thingsboard.io/user-guide/calculated-fields/export-calculated-field-2-pe.png,
-        title: Navigate to the <b>Calculated fields</b> tab of the target entity or profile and click the <b>Export<b> button located in the row of the specific calculated field.
+        title: Navigate to the <b>Calculated fields</b> page and click the <b>Export</b> button located in the row of the specific calculated field.
 '
 %}
 
@@ -703,7 +698,7 @@ Steps to import:
         title: In the opened window, upload the JSON file with the calculated field configuration and click **Import**.
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/import-calculated-field-3-ce.png,
-        title: The edit window will open, allowing you to **specify the entity or profile** to which the calculated field will be applied.
+        title: In the dialog that opens, **specify the entity or profile** to which the calculated field will be applied.
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/import-calculated-field-4-ce.png,
         title: If there are any problems with arguments, they will be highlighted.
@@ -728,7 +723,7 @@ Steps to import:
         title: In the opened window, upload the JSON file with the calculated field configuration and click **Import**.
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/import-calculated-field-3-pe.png,
-        title: The edit window will open, allowing you to **specify the entity or profile** to which the calculated field will be applied.
+        title: In the dialog that opens, **specify the entity or profile** to which the calculated field will be applied.
     ===
         image: https://img.thingsboard.io/user-guide/calculated-fields/import-calculated-field-4-pe.png,
         title: If there are any problems with arguments, they will be highlighted.
@@ -748,7 +743,7 @@ Steps to import:
 {% include images-gallery.liquid showListImageTitles="true" imageCollection=importCalculatedFieldCE %}
 {% endif %}
 {% if docsPrefix == "pe/" or docsPrefix == "paas/" or docsPrefix == "paas/eu/" %}
-{% include images-gallery.liquid imageCollection=importCalculatedFieldPE %}
+{% include images-gallery.liquid showListImageTitles="true" imageCollection=importCalculatedFieldPE %}
 {% endif %}
 
 > **Note**: ensure the imported field is correctly applied and update any necessary parameters:
@@ -791,7 +786,7 @@ Each calculated field includes an action panel for managing the field:
 {% include images-gallery.liquid imageCollection=calculatedFieldsParametersPE %}
 {% endif %}
 
-<b><font size="4">View detailed information of the calculated field</font></b>
+<br><b><font size="4">View detailed information of the calculated field</font></b>
 
 Click the calculated field to view its details.
 
@@ -816,7 +811,7 @@ Click the calculated field to view its details.
 {% include images-gallery.liquid imageCollection=calculatedFieldsParameters2PE %}
 {% endif %}
 
-<b><font size="4">Modify the calculated field</font></b>
+<br><b><font size="4">Modify the calculated field</font></b>
 
 To modify the calculated field, click it to open the details view, then click the orange **pencil** button.   
 After making your changes, click the orange **check** button to apply the updates.

_includes/docs/user-guide/alarm-rules.md

@@ -453,6 +453,28 @@ Each HVAC device received the <span class="code-light">hvacMode</span> attribute
 
 <hr>
 
+## Troubleshooting
+
+### Propagation path settings do not apply after the update
+
+**Problem:** When editing an existing Calculated Field to change the **Relation direction** or **Relation type** (e.g., switching from *Contains* to *Manages*), the field ignores these changes and continues to propagate data using the originally configured path.
+
+**Cause:** The Calculated Field logic caches the **Propagation path to related entities** defined during the initial creation. It does not correctly detect updates made specifically to the relation direction or relation type in the configuration, resulting in the field failing to re-initialize the path.
+
+**Solution:** To force the Calculated Field to apply the new propagation path settings,
+the system requires a configuration change to the **Data to propagate** section.
+Any modification to the arguments will trigger the necessary re-initialization.
+
+Choose one of the following safe methods:
+
+1. Re-create the Field (Cleanest)
+   If you must keep your current arguments exactly as they are (e.g., you cannot change default values), the only way to trigger the update is to delete the existing Calculated Field and create a new one with the correct propagation path settings.
+
+2. Modify Default Value (Recommended Workaround)
+   If you want to fix the issue without re-creating the field,
+   edit an existing argument and change its **Default value** (e.g., set a value if it was empty, or update it).
+   > If the source data is missing, the new default value will be used. However, if the source data is always present, this is the smartest method as it forces the update with zero impact on your data.
+
 ## Your feedback
 
 Don&#39;t hesitate to star ThingsBoard on [github](https://github.com/thingsboard/thingsboard){:target="_blank"} to help us spread the word.

_includes/docs/user-guide/calculated-fields/index.md

@@ -64,7 +64,15 @@ function createBox(integrator) {
      textSite.textContent = 'Visit us at: ';
 
      var linkSite = document.createElement('a');
-     var link = integrator.site.href.replace('https://', '').replace('http://', '').replace('/', '');
+     var link = integrator.site.href
+       .replace(/^https?:\/\//, '')
+       .replace(/^(.*?)(\/.*)?$/, (match, domain, path = '') => {
+           if (path.startsWith('/thingsboard')) {
+               return domain + path;
+           }
+           return domain;
+       });
+
      linkSite.href = 'https://' + link;
      linkSite.textContent = link.replace('www.', '');
      linkSite.target = integrator.site.target;

_includes/docs/user-guide/calculated-fields/propagation-calculated-field.md

@@ -335,6 +335,18 @@
       "target": "_blank"
     }
   },
+  {
+    "type": ["Europe"],
+    "country": ["Germany"],
+    "name": "Elbesoft IoT",
+    "contact": {
+      "href": "info@elbesoft-iot.com"
+    },
+    "site": {
+      "href": "elbesoft-iot.de/thingsboard",
+      "target": "_blank"
+    }
+  },
   {
     "type": ["Europe"],
     "country": ["Germany", "Austria", "Switzerland"],

_includes/integrators.js

@@ -1069,6 +1069,8 @@ $bg-white: #fff
               border-radius: 3px
             &::-webkit-scrollbar-thumb:hover
               background-color: #A1A1A1
+            &:has(>.device-profiles-container.advanced)
+              padding-top: 10px
           .actions-container
             flex-shrink: 0
             padding: 24px 0
@@ -1171,11 +1173,13 @@ $bg-white: #fff
       width: 100%
       max-width: 800px
       margin: 16px
+      overflow-y: auto
       .modal-wrapper
         background-color: $bg-white
         padding: 32px
         border-radius: 16px
         position: relative
+        flex: 1
         .modal-header
           display: flex
           justify-content: space-between
@@ -1228,7 +1232,7 @@ $bg-white: #fff
                 top: -4px
                 width: 300px
                 line-height: 18px
-          #json-input
+          #tbPcJsonInput
             width: 100%
             height: 250px
             font-family: 'Inconsolata', monospace
@@ -1496,7 +1500,7 @@ $bg-white: #fff
               font-size: 18px
           .input-group
             flex: 1
-            #json-input
+            #tbPcJsonInput
               height: 200px
           .footer
             flex-direction: column

_includes/integrators.json

@@ -485,24 +485,24 @@ <h2>Add-ons</h2>
                     <div class="card">
                         <img src="https://img.thingsboard.io/pricing/edge-add-on-icon.svg" alt="Edge add on icon">
                         <div class="text">
-                            <h3 data-faq-id="${addOnsPricing[product].edge.faq}" data-faq-link-size="50%">Edge Computing</h3>
+                            <h3 data-faq-id="${addOnsPricing[product].edge.faq}" data-faq-link-size="50%" data-faq-tooltip="Run a local on-prem instance to keep operations running even when the internet is down.">Edge Computing</h3>
                             <p>Process data where it is collected</p>
                             <p>Starting from <span>${edgePrice}</span></p>
                         </div>
                     </div>
                     <div class="card">
                         <img src="https://img.thingsboard.io/pricing/trendz-add-on-icon.svg" alt="Trendz add on icon">
                         <div class="text">
-                            <h3 data-faq-id="${addOnsPricing[product].trendz.faq}" data-faq-link-size="50%">Trendz Analytics</h3>
+                            <h3 data-faq-id="${addOnsPricing[product].trendz.faq}" data-faq-link-size="50%" data-faq-tooltip="Turn raw IoT data into actionable insights with advanced analytics and trend prediction.">Trendz Analytics</h3>
                             <p>Advanced analytics for your solution</p>
                             <p>Starting from <span>${trendzPrice}</span></p>
                         </div>
                     </div>
                     <div class="card">
                         <img src="https://img.thingsboard.io/pricing/wl-add-on-icon.svg" alt="White-labeling add on icon">
                         <div class="text">
-                            <h3 data-faq-id="${addOnsPricing[product].wl.faq}" data-faq-link-size="50%">White-labeled Mobile App</h3>
-                            <p>Сustomizable mobile application </p>
+                            <h3 data-faq-id="${addOnsPricing[product].wl.faq}" data-faq-link-size="50%" data-faq-tooltip="Launch a client-ready mobile app under your brand—your name, logo, colors, and a fully polished look & feel—so customers experience your product, not a third-party app.">White-labeled Mobile App</h3>
+                            <p>Сustomizable mobile application</p>
                             <p>${wlPrice}</p>
                         </div>
                     </div>