i4connected Knowledgebase 5.6

Version 5.6.16

Abstract

Check out the list of Changes and Fixed Bugs processed for the i4connected 5.6.16 version. Upgrade and enjoy our new features!

Changes

ID

Description

I4C-2071

Change the Events permissions to be applicable on both the Global and the Hierarchical level

Tip

For more details about the updates done at the level of Alarm permissions, please check the Permissions table, here.

I4C-2379

Introduce the "Telegram" application as an i4messenger communication mean

Tip

For more details, please also refer to the dedicated article, here.

I4C-1707

Introduce the Stale data detection feature for Counter devices

Tip

Since version 5.6.16, Counter devices should allow the users to detect broken counters which do not report value changes over a predefined interval.

For more details about the Stale data detection feature, please visit the dedicated article, here.

I4C-1908

Introduce the Response Teams inheritance concept

Tip

Since version 5.6.16, a response team assigned to an entity higher on the hierarchy will also transmit notifications from Areas, Sub-Organizational Units, and Devices, that are indirectly assigned to that entity.

For more details, please visit the dedicated articles, here.

I4C-2053

Update the Signal compression feature to apply the compression settings on existing historical data, as well.

Tip

For more details, please also visit the dedicated articles, here.

I4C-2360

Allow the possibility to display Event priorities in the portal's status bar, grouped by the amount and priority color

Tip

For more details, please also visit the dedicated articles, here.

I4C-2360

Allow the Device to overwrite the event occurrence priority

Tip

Since version 5.6.16, it is possible to overwrite the priority of an event occurrence (triggered manually or by the system), with a predefined device priority.

For more details, please also visit the tutorial describing this use case, here.

I4C-2066

Allow the possibility to define an icon for Device types, in order to display it in the Entity type column of the Online/Historical alarms lists

Tip

For more details, please also visit the dedicated article, here.

I4C-2067

Introduce the possibility to save and remember the applied filters and sorting actions of the Online alarms panel

Tip

For more details, please also visit the dedicated article, here.

I4C-2068

Introduce the Alarm suppression feature for Devices

Tip

For more details, please also visit the tutorial describing this use case, here.

I4C-2126

Introduce an automatic measurable parameter to the Virtual signal script, called the "self" parameter

Tip

The "self" parameter can be used to populate the virtual signal with the last update of that virtual signal. This parameter helps the user to avoid using the same signal as an input parameter for a virtual signal script.

For more details please also visit the tutorial describing a simple use-case, here.

I4C-2324

Introduce in the status bar the possibility to display the system's current version number

Tip

For more details, please read more details, here.

I4C-2517

Add the possibility to export the list of Historical Alarms via XLS format

Tip

For more details, please visit the dedicated article, here.

I4C-2526

Update the Signal filtering function for the Raw Data Chart

Tip

For more details, please visit the dedicated article, here.

I4C-2362

Add separate tile and panel for the System events, allowing the users to manage their field definitions, except for their names

Tip

System events are events generated by the system, informing users about various incidents, such as exceeded SLAs, script execution failures or defects, Signal health issues, etc.

For more details please visit the dedicated article, here.

I4C-2665

Update the API calls for Signal measurements to be based on the "last_modified_date" instead of "timestamp"

Fixed Bugs

ID

Description

I4C-1872

i4connected stops logging data while the online values in the signals are still being updated

I4C-1682

The list of devices does not show the number of pages

I4C-2192

i4Scada Adapter throws an exception when it initializes more than 2000 Signals

I4C-2447

Deletion of Organizational Units is not possible due to missing logbooks and sources (isolated issues)

I4C-2448

The filters used by the hierarchical entities users lists are not properly working on big installations

I4C-2463

Error "The write operation failed on the server” is triggered when adding a new value to a Signal in a manual counter, if the last Signal value is 999999999

I4C-2477

The Invitation App does not consider the value of the "IsNative" setting

I4C-2497

It is not possible to delete a signal with more than 10000+ measurements

I4C-2505

Event details (Event cause, Event effect, Event repair) are not translatable in i4connected

I4C-2507

The system performance is highly impacted when opening the map panel since all the map images are loaded

I4C-2590

Counter inactivity events are persisted in the Online alarms list after the server is restarted

I4C-1864

Alarm messages from the SCADA system are not filtered by security

I4C-2138

Deleting an Event definition does not inform users about related event scripts that will be also removed

I4C-2214

The Scriban event occurrence property "metadata" does not return any values in the notification

I4C-2469

The ASP.NET Core does not work with proxy servers and load balancers

I4C-2498

The Simple search function does not properly work for the Historical Alarms panel

I4C-2510

Cannot apply a Signal type for a Signal while creating the Signal, since all the filled-in info is removed

I4C-2575

The Online Alarms icon total counter is decreased when acknowledging an ongoing alarm

I4C-2244

In an attempt to change the Advanced filter "Enumeration"(metadata), in the Object Filters panel, the previously applied Enumeration filters are reset

I4C-2318

The mandatory fields are not marked with an asterisk on the Registration page

I4C-2361

Notification on the login screen is missing as well a contact information

I4C-2366

The list of Effective permissions in the addEntityUserRolePackage panel is not properly displayed while on the German content language

I4C-2375

The alarm groups are not displayed in the Online Alarms panel when you open the panel for the first time

I4C-2381

Removing the Start/End date settings under Parameter selector is not possible in the Historical alarms panel

I4C-2467

The Status filtering in the Online Alarms panel should be removed since it does NOT make sense

I4C-2616

An Entity Response Team is NOT removed if the parent entity is deleted

I4C-2346

Updating an existing report leads to a 500 Internal Server error

New Settings

The following settings were introduced to the appsettings.json file since version 5.6.16:

Relevance

Setting

Description

API

SupportsSignout

The i4connected portal can be accessed using an external provider.

If the external provider does not support sign-out, this setting should be set to "false". This way, when logging out of the i4connected system, the log-out operation will not be propagated to the external provider's active instances, as well.

If the used external provider already supports sign-out, this setting should be set to "true".

API

ASPNETCORE_FORWARDEDHEADERS_ENABLED

Enables or disables the ASP.NET Core to work with proxy servers and load balancers.

Tip

For more details, please check the dedicated article here.

The following features were introduced to the Database Settings table since version 5.6.16:

Relevance

Setting

Description

Database

feature.suppressSignalInactivityOnAdapterEvents

Enables or disables the possibility to suppress alarm triggering for devices taken out of the system for maintenance work, for example, to avoid an alarm shower.

Tip

For more details about the Alarm suppression function, please visit the dedicated articles, here.

Database

telegram.bot.token

Sets the Bot token for the Telegram messaging application.

Tip

For more details about the Telegram notifications, please visit the dedicated article, here.