Merge pull request #203 from AVSystem/RN2025.4.0

Added RN 2025.4.0

Author: Pantofel102

docs/Coiote_IoT_DM/Release_Notes/v2021.22.1.md

@@ -3,20 +3,21 @@ Previous version: v2021.19.0
 
 ## Features
 
-### New Device inventory view
+**New Device inventory view**      
 
 The new Device inventory is now the default for viewing devices in the {{ coiote_short_name }} platform. It has an improved design as well as faster and more stable performance.
 ![Device inventory](images/device_inventory.png "device inventory")
-The new Device inventory is available directly from the left navigation bar. If you need to access the old Device inventory view, go to **Administration -> Device inventory**.
+The new Device inventory is available directly from the left navigation bar. If you need to access the old Device inventory view, go to **Administration -> Device inventory**      .
 
 ## Enhancements
 
-### EST DER format support
+**EST DER format support**  
+    
 We switched from the PEM to the DER content format of enrolling and re-enrolling requests sent to the EST server. Thanks to this change more EST Server implementations will be supported and compliance with RFC7030 is enhanced.
 
 ## Bug fixes
 
-### Larger limits for HTTP request headers
+**Larger limits for HTTP request headers**      
 
 Thanks to a new configuration for Jetty, you can now access REST API and {{ coiote_short_name }} GUI even with large HTTP request headers.
 

docs/Coiote_IoT_DM/Release_Notes/v2021.23.0.md

@@ -3,13 +3,16 @@ Previous version: [v2021.22.1](v2021.22.1.md)
 
 ## Enhancements
 
-### Record headers in Kafka messages
+**Record headers in Kafka messages** 
+
 You can now add record headers to the kafkaPublish tag when configuring an XML task. It means that the components responsible for the Kafka event processing (e.g., routing) no longer need to read each binary message. Instead, these components read only the record headers and therefore work faster.
 
-### Support for additional non-standard device type
+**Support for additional non-standard device type** 
+
 We continue to improve compatibility with devices that have incomplete or faulty support of the standard LwM2M protocol. To make such a device ready to work with {{ coiote_short_name }}, you can now turn on and configure a non-standard logic in the Device dialects section.
 
-### New error pages
+**New error pages**      
+
 The 400, 404, and 5XX error pages now have a cleaner and more user-friendly look.
 
 ![Error pages](images/404.png)
@@ -18,8 +21,10 @@ The 400, 404, and 5XX error pages now have a cleaner and more user-friendly look
 
 ## Bug fixes
 
-### Uninterrupted access to GUI
+**Uninterrupted access to GUI**  
+
 Fixed a bug where the GUI of {{ coiote_short_name }} would crash after 30 minutes of inactivity on some installations. Thanks to the new configuration, the GUI now works smoothly even after hours of inactivity.
 
-### JDK downgrade
+**JDK downgrade**      
+
 To improve the speed performance of {{ coiote_short_name }}, we’ve downgraded the JDK version from 17 to 11. No action is required for the virtual machine deployments because the JRE is included in the docker image.

docs/Coiote_IoT_DM/Release_Notes/v2021.24.5.md

@@ -3,7 +3,7 @@ Previous version: [v2021.23.0](v2021.23.0.md)
 
 ## Features
 
-### Read Model Factory on EU Cloud installation
+**Read Model Factory on EU Cloud installation**      
 
 The data for the Dashboard and Device Inventory views is now provided by the Read Model Factory module deployed as a separate application to optimize resource consumption and data processing.
 
@@ -14,11 +14,12 @@ What changes in the application:
 2. In the Dashboard view, you can now search for alerts by device data - lifecycle status, domain, group, manufacturer, model name, firmware version.
 ![Device inventory](images/filters.png "Device inventory")
 
-### Bypassing light sessions by HealthChecker
+**Bypassing light sessions by HealthChecker**      
 
 We have added a possibility to create a list of device IDs in `cdm.conf` that will have normal sessions even when the *light session* threshold is reached.
 
 ## Enhancements
 
-### Whitelabelling and custom URLs in Identity and Access Management
-When logging to {{ coiote_short_name }} (cloud installations) using a custom tenant hostname, the user can now be redirected to a login page under the same custom tenant hostname.  The change applies to the {{ coiote_short_name }} **login page**, **User Management** view and the **change password** view.
+**Whitelabelling and custom URLs in Identity and Access Management**    
+  
+When logging to {{ coiote_short_name }} (cloud installations) using a custom tenant hostname, the user can now be redirected to a login page under the same custom tenant hostname.  The change applies to the {{ coiote_short_name }} **login page**, **User Management** view and the **change password**       view.

docs/Coiote_IoT_DM/Release_Notes/v2022.13.5.md

@@ -4,7 +4,8 @@ Previous version: v2022.12.4
 
 ## Features
 
-### New Device Center
+**New Device Center**  
+    
 We have introduced the new Device Center for effective management of single devices. Designed to enable IoT developers build LwM2M applications quickly and intuitively, it features the following actionable views:
 
 - Summary sidebar
@@ -21,7 +22,7 @@ We have introduced the new Device Center for effective management of single devi
       ![Device Center overview tab](images/DC_overview_tab.PNG "Device Center overview tab")
 
 - Configuration tab
-       - Upload device image and change its **Friendly name**
+       - Upload device image and change its **Friendly name**      
        - View and copy device connection parameters
 
       ![Device Center configuration tab](images/DC_configuration_tab.PNG "Device Center configuration tab")
@@ -36,4 +37,4 @@ We have introduced the new Device Center for effective management of single devi
        - Search the data model for device objects, object instances, and resources
 
       ![Device Center data model tab](images/DC_datamodel_tab.PNG "Device Center data model tab")
-The Device Center replaces the old Device Management Center view (DMC) which is still supported - use the **Go to previous version** button and the **Go to new Device Center** link to switch between them.
+The Device Center replaces the old Device Management Center view (DMC) which is still supported - use the **Go to previous version** button and the **Go to new Device Center**       link to switch between them.

docs/Coiote_IoT_DM/Release_Notes/v2022.16.0.md

@@ -4,31 +4,31 @@ Previous version: v2022.14.15
 
 ## Enhancements
 
-### Minor GUI enhancements
+**Minor GUI enhancements**      
 
 - We have fixed the behaviour of dialog windows for some platform views.
 - We have improved the looks of empty states in some places of the GUI.
-- The **‘Additional costs’** calculator in the **Payment service** panel has been modified so that it now includes base and additional costs.
-- Validations have been added in the **Set observation** side navigation dialog of the **Device Center**.
+- The **‘Additional costs’** calculator in the **Payment service**       panel has been modified so that it now includes base and additional costs.
+- Validations have been added in the **Set observation** side navigation dialog of the **Device Center**      .
 - We have changed the date format presented in the GUI so that it conforms to the ISO standard.
 - Float values presented in the data model are now rounded to at most two significant digits.
 
-### Domain hierarchy support for DTLS/TLS certificates
+**Domain hierarchy support for DTLS/TLS certificates**      
 
 The **DTLS/TLS Certificates** panel now displays only certificates from the current domain that the user is logged into.
 
 ## Bug Fixes
 
-### Fixed the Certificate Request message when connecting over TLS/TCP
+**Fixed the Certificate Request message when connecting over TLS/TCP**      
 We have fixed the *Certificate Request* message when the Server and Client try to connect over TLS/TCP. Connection errors for clients that use MBed TLS (including **Anjay**) are now solved.
 
-### Fixed the license invalidation
+**Fixed the license invalidation**      
 We have corrected the License invalidation action so that it is done only after a configurable retry backoff time limit.
 
-### Added validation the Azure IoT Hub integration
+**Added validation the Azure IoT Hub integration**      
 
 We have added a validation for the Device ID in the **Hyperscaler Integration Center**. Now the Device ID should be a string up to 128 characters long consisting of alphanumeric characters plus the special characters: '-', '.', '_', ':'. The last character must be alphanumeric or dash.
 
-### Fixed scheduling firmware upgrades when resource value is an empty string
+**Fixed scheduling firmware upgrades when resource value is an empty string**      
 
 We have fixed an error that prevented scheduling firmware upgrades on devices whose **Firmware Update Protocol Support** resource value was an empty string.

docs/Coiote_IoT_DM/Release_Notes/v2022.17.0.md

@@ -4,7 +4,7 @@ Previous version: [v2022.16.0](v2022.16.0.md)
 
 ## Features
 
-### Configuring EST integration via **Domain properties**
+**Configuring EST integration via Domain properties**         
 
 We have introduced dynamic EST integration configuration via the domain properties.
 It is now possible for each client to set up its own EST server in the Domain management view.
@@ -15,25 +15,30 @@ If there is no EST configuration on a given domain, then the system uses the val
 Changes have also been made to the DTLS/TLS Certificates view. Now only certificates added in the given domain are presented to avoid cross-domain certificate visibility.
 
 ## Architectural Changes
+
 There were no architectural changes in this release.
 
 ## Enhancements
 
-### Minor GUI improvements
+**Minor GUI improvements**  
+
 In Device Inventory, the filter counter is now hidden when there is no filter applied.
 
-### ‘Impersonated by’ column in User activity table of Historical analysis
+**‘Impersonated by’ column in User activity table of Historical analysis**      
 
 We have added a new column to the User activity table that shows the UserID of the actual user (impersonator) who executed the recorded action from the account of the user being impersonated.
 !['Impersonated by' column](images/impersonated_by.png "'Impersonated by' column")
 
 ## Bug Fixes
 
-### Fixed Cancel all tests action in the Device tests tab of DMC
+**Fixed Cancel all tests action in the Device tests tab of DMC**    
+
 We have fixed the faulty behaviour of the Cancel all tests button used to stop the execution of tests inside the Device tests tab of the Device Management Center.
 
-### Fixed loading data for multiresources with no instances in the data model
+**Fixed loading data for multiresources with no instances in the data model**   
+
 We have fixed an error occurring while loading a multiresource that has no instances in the data model. Now the multi-resource value is displayed in the same manner as a single resource without value.
 
-### Fixed task execution status (report) not displayed after device domain change
+**Fixed task execution status (report) not displayed after device domain change**  
+
 When moving devices between domains, their task execution statuses (reports) are now updated accordingly.

docs/Coiote_IoT_DM/Release_Notes/v2022.18.3.md

@@ -4,15 +4,15 @@ Previous version: [v2022.17.0](v2022.17.0.md)
 
 ## Enhancements
 
-### FOTA panel redirection page in Device Center
+**FOTA panel redirection page in Device Center**      
 
 We have added a new FOTA tab in the Device Center. It redirects users to the previous version of the Device Management Center to perform a device Firmware upgrade. The new FOTA view is currently under development.
 
 ![Device Center FOTA tab](images/DC_FOTA_tab.png)
 
-### Improvements in Device inventory and Operations center
+**Improvements in Device inventory and Operations center**      
 
-We have introduced some enhancements to the **Device inventory** and **Operations center**.
+We have introduced some enhancements to the **Device inventory** and **Operations center**      .
 
 - Now it is the **Device inventory** that is the default page displayed upon logging in to the platform. The order in the navigation menu has also been changed.
 - In the **Operations center**, the **Alerts** tab is now the default view that is displayed.
@@ -26,14 +26,23 @@ We have introduced some enhancements to the **Device inventory** and **Operation
 
 ## Bug Fixes
 
-### Fixed **Select template** button behaviour in **Task templates**
+**Fixed Select template button behaviour in Task templates** 
+
 In the Task template panel, the **Select template** button now appears correctly even for long template names.
 section for description of bug fixes.
-### Fixed **Device registration status action**
+
+**Fixed Device registration status action**
+
 We have fixed the behaviour of the **Devices registration status action** feature so that now the configured action is performed only for the domain it was set up in - no conflict of domains occurs.
-### Fixed the `Leave` tag in XML tasks
+
+**Fixed the `Leave` tag in XML tasks**  
+
 We have fixed the behaviour of the `leave` tag in the XML tasks, so that the device now leaves all the defined subgroups and the task finishes successfully.
-### Fixed loading page when migrating large numbers of devices between domains
+
+**Fixed loading page when migrating large numbers of devices between domains**  
+
 We have fixed the GUI action of changing the domain for large numbers of devices via the **Device inventory**. Now the loading page doesn’t freeze while handling bulk migrations.
-### Fixed no response for 2nd *Register Update* in some devices
+
+**Fixed no response for 2nd *Register Update* in some devices**    
+
 As a result of failure to persist updated device lifetime, the Server responded with the 4.04 error for the second *Register Update* in some devices. We have fixed it so that concurrent update handling in the {{ coiote_short_name }} database is avoided.

docs/Coiote_IoT_DM/Release_Notes/v2022.19.2.md

@@ -4,29 +4,35 @@ Previous version: [v2022.18.3](v2022.18.3.md)
 
 ## Enhancements
 
-### Connection status indicator in **Device creator** summary
+**Connection status indicator in *Device creator* summary**  
+
 We have introduced the connection status indicator to the summary step of the **Device creator**. It is now consistent with the Device Center summary
 
 ![Connection status indicator](images/connection_status_tag.png "Connection status indicator")
 
-### ‘Impersonated by’ column in task edition history of **Historical analysis**
+**‘Impersonated by’ column in task edition history of *Historical analysis***      
+
  We have added the ‘Impersonated by’ column to theTask edition history table that shows the UserID of the actual user (impersonator) who executed the recorded action from the account of the user being impersonated.
 
 
 ## Architectural Changes
 
-### **Device ID** changes to **Endpoint name**
+**Device ID changes to Endpoint name**
+
 We have changed the **Device ID** label to **Endpoint name** in Device inventory, Device Center and other relevant views. This has been triggered by major changes in how the device endpoint name is now encrypted in the database.
 
 ![Endpoint name column in DI](images/endpoint_name_DI.png "Endpoint name column in DI")
 
 ## Bug Fixes
 
-### Fixed *Devices registration status action* causing domain change
+**Fixed *Devices registration status action* causing domain change**  
+
 Deleting *Devices registration status action* no longer causes devices to change domains.
 
-### Fixed behavior of snackbars persisting between steps of the Device creator
+**Fixed behavior of snackbars persisting between steps of the Device creator**
+     
 Snackbars appearing In the "Connect your device” step of Device creator will now disappear when navigating to the next step.
 
-### Fixed searching for task templates
+**Fixed searching for task templates**      
+
 We have fixed the search option available when selecting a task template. It now works correctly, also for old Expressions and for characters such as square brackets.

docs/Coiote_IoT_DM/Release_Notes/v2022.20.4.md

@@ -4,25 +4,29 @@ Previous version: [v2022.19.2](v2022.19.2.md)
 
 ## Features
 
-### Connect single device to **Azure**
-We have added an option to connect single devices in **Device inventory** to the currently integrated **Azure** service. It is available in the context menu for each created device displayed in the **Device inventory** table. The operation can only be performed for a device with a configured LwM2M Management server and in the domain that the device belongs to.
+**Connect single device to Azure**
+
+We have added an option to connect single devices in **Device inventory** to the currently integrated **Azure** service. It is available in the context menu for each created device displayed in the **Device inventory**       table. The operation can only be performed for a device with a configured LwM2M Management server and in the domain that the device belongs to.
 
 ![Connect to Azure button in DI](images/connect_to_azure.png)
 
-### Saving filter state of the Device inventory in URL fragment
-In **Device inventory**, we have introduced saving filter data as state in a URL fragment. This allows saving any filter data e.g. groups, domain, lifecycle status, and search text. When the user saves a filter or types in the search field, the URL fragment is updated. When copying and pasting the URL, the relevant data context will be applied in the filter.
+**Saving filter state of the Device inventory in URL fragment** 
+
+In **Device inventory**      , we have introduced saving filter data as state in a URL fragment. This allows saving any filter data e.g. groups, domain, lifecycle status, and search text. When the user saves a filter or types in the search field, the URL fragment is updated. When copying and pasting the URL, the relevant data context will be applied in the filter.
 
 ## Architectural Changes
 
-### New monitoring endpoints in restAPI
+**New monitoring endpoints in restAPI**     
+
 We have implemented two device monitoring restAPI endpoints:
 
 - ``/deviceMonitoring/data/{deviceId}/resourceUrl/{lwm2mUrl}`` - returns a series of monitoring data from the device's resource identified by its LwM2M URL that were reported between the `timeRangeStart` and `timeRangeEnd`.
 - ``/deviceMonitoring/data/{deviceId}/alias/{alias}`` - returns a series of monitoring data from the device's resource identified by its alias that were reported between the `timeRangeStart` and `timeRangeEnd`.
 
 ## Enhancements
 
-### New methods added to lwM2M context in XML tasks
+**New methods added to lwM2M context in XML tasks** 
+    
 Added two methods to lwm2m context in XML tasks:
 
 - `dmPathToLwM2MPath` - transforms a `dmPath` to a `lwm2mPath` (eg. `Device.0.Manufacturer` -> `/3/0/0`)
@@ -32,8 +36,10 @@ If the specified `dmPath` is not known, because either: the model is invalid or
 
 ## Bug Fixes
 
-### Fixed adding devices to inaccessible group using ``<join>`` tag
+**Fixed adding devices to inaccessible group using ``<join>`` tag**   
+
 We have changed the behavior of the XML task ``<join>`` tag so that it is no longer possible to create a group in the wrong domain using the tag.
 
-### Fixed values of Connectivity widgets in Device Center Overview tab
+**Fixed values of Connectivity widgets in Device Center Overview tab**  
+
 We have fixed the **Cell ID**, **APN**, **Radio signal strength** and **Network bearer** **Connectivity** widgets in **Device Center** so that each displays the relevant values.