Skip to main content

i4connected Knowledge Base

Version 5.6.12

Abstract

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

Changes

ID

Description

I4C-1196

Implement the Data Export functionality

I4C-1501

Provide settings to enable/disable a registration form by OIDC login

I4C-1383

Enable passive synchronization of i4connected entities with an i4designer project

I4C-1019

Implement the GridVis Adapter

I4C-1752

Extend filters on Devices search, to include description, and show Device information with description in the list of Devices

I4C-1788

Add weekly time resolution to Load Profile, Object Delta and Time Delta dashboards

I4C-1092

Update Carel Adapter to support import month

I4C-1623

Introduce JSON persistency API for i4designer components (Components configurations)

Fixed Bugs

ID

Description

I4C-1094

The drill-down page does not include a start image

I4C-1589

Metadata properties that contain "." are not working

I4C-1665

Update the entire i4connected application to use the timezone of the currently logged in user

I4C-987

The server memory dropped down, leading to some value loss (isolated issue)

I4C-1295

Internal Server Error is triggered on an attempt to choose a Site or an Area for the Area Sankey diagram

I4C-1296

User with low permission level can access IoT Messages from sites that are not available for him/her

I4C-1428

Event occurrence property "eventPriority" does not return the current priority

I4C-1462

The list of Historical Alarms is not updated

I4C-1643

Manual events published from the site don't have occurrence property "site" and aren't shown in historical alarms

I4C-1610

The "Manage Sites and Areas" permission allows the possibility to issue invitations to users

I4C-1646

High authority users can remove his / her ownership from a Response Team and consequently lose access to it

I4C-1672

Areas are not displayed in the Object Filters panel

I4C-1739

Modbus counters deliver implausible values

I4C-1746

The "minimum value" and "maximum value" have no effect when writing values to signals

I4C-1750

The Sankey-Diagram is not populated with data

I4C-1201

The "Save & AddNew" button in the Edit Device panel has the wrong functionality

I4C-1275

The "Save & AddNew" button is displayed in the Edit User panel

I4C-1464

Data privacy rules are broken since information about the hierarchical assignments of other users is visible

I4C-1599

Duplicate reports are displayed in the Report Archive list

I4C-1601

Manual events are not filterable by objectFilter in historicalAlarms and onlineAlarms

I4C-1132

Invitations cannot be sent when the addEntityUser panel is pinned

I4C-1201

The "Save & AddNew" button in the Edit Device panel has the wrong functionality

I4C-1762

Display issues at the level of the Site details panel (isolated issue)

I4C-1885

IAM account data changes when configuring another user in i4connected

I4C-1910

Devices are not found in the Object Filter panel if the device is assigned to an area, but not to a Site

I4C-1498

The textual label of the "Register Byte order" field is incorrectly written

I4C-1503

Notification Profiles and Response Teams Owner field displays "Unknown user" for users without "privileged" roles, if the owner "is privileged"

I4C-1602

Occurrence Owner is not displayed in Event history panel if Alarm was either Closed or Acknowledged

I4C-1609

The "LastUpdate" setting of the "Measures import" tile is not loaded (isolated issue)

I4C-1901

The local user is merged with an external account

I4C-1902

UserName should not be updatable from API call

I4C-1755

Error "Unhandled exception was thrown in the application." leads to a server crash (isolated issue)

New settings

The table below lists the new settings, introduced at level or the i4connected server (folder path i4connected-installation>\server\WEBfactory.DWH.Server.exe.config). The settings "BulkMaxRetries" and "BulkRetryIntervalMultiplierInSeconds" refer to the general system logging behavior, that can also be customized for Event logging, Event History logging, Fact logging, Maintenance logging, and Measurement logging.

Relevance

Setting

Description

Server

AutoProvisionUser

Used to enable/disable a registration form by OIDC login.

Tip

For more details please also visit the dedicated article here.

Server

logging:BulkMaxRetries

Defines how many times the server will retry to use bulk insert, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting is the easy way to enable the same value, for all the below described BulkMaxRetries settings.

In order for this setting to be taken into account, the below settings should be commented on or deleted.

logging:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting is the easy way to enable the same value, for all the below described BulkRetryIntervalMultiplierInSeconds settings.

In order for this setting to be taken into account, the below settings should be commented on or deleted.

eventLogging:BulkMaxRetries

Defines how many times the server will retry to use the bulk insert for the event occurrences, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting allows the user to customize the value of the BulkMaxRetries operations, for event occurrences.

This setting will only be considered if it is uncommented.

eventLogging:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation, for event occurrences, has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting allows the user to customize the value of the BulkRetryIntervalMultiplierInSeconds operation, for event occurrences.

This setting will only be considered if it is uncommented.

eventHistoryLogging:BulkMaxRetries

Defines how many times the server will retry to use the bulk insert for the event history updates, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting allows the user to customize the value of the BulkMaxRetries operations, for event history updates.

This setting will only be considered if it is uncommented.

eventHistoryLogging:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation, for event history updates, has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting allows the user to customize the value of the BulkRetryIntervalMultiplierInSeconds operation, for event history updates.

This setting will only be considered if it is uncommented.

factLogging:BulkMaxRetries

Defines how many times the server will retry to use the bulk insert for the event facts, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting allows the user to customize the value of the BulkMaxRetries operations, for event facts.

This setting will only be considered if it is uncommented.

factLogging:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation, for event facts, has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting allows the user to customize the value of the BulkRetryIntervalMultiplierInSeconds operation, event facts.

This setting will only be considered if it is uncommented.

maintenance:BulkMaxRetries

Defines how many times the server will retry to use the bulk insert for the shift facts, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting allows the user to customize the value of the BulkMaxRetries operations, for shift facts.

This setting will only be considered if it is uncommented.

maintenance:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation, for shift facts, has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting allows the user to customize the value of the BulkRetryIntervalMultiplierInSeconds operation, for shift facts.

This setting will only be considered if it is uncommented.

measurementLogging:BulkMaxRetries

Defines how many times the server will retry to use the bulk insert for the measurements, in case the operation has encountered an error.

The default value of the setting is 3, but it can be increased or decreased, as needed.

Tip

This setting allows the user to customize the value of the BulkMaxRetries operations, for measurements.

This setting will only be considered if it is uncommented.

measurementLogging:BulkRetryIntervalMultiplierInSeconds

Defines the time interval the server will wait between retries, in case a bulk insert operation, for measurements, has encountered an error.

After each error, this setting is multiplied with the current retry number, to decide the final time interval the server will wait until the next retry. For example, after the first error, the server will wait for 5*1 seconds, after the second error, it will wait for 10 (5*2) seconds, and so on, until the BulkMaxRetries is exceeded.

Tip

This setting allows the user to customize the value of the BulkRetryIntervalMultiplierInSeconds operation, for measurements.

This setting will only be considered if it is uncommented.

New default values for existing settings

The below table reflects the changes at level of default values, for the following i4connected-installation>\server\WEBfactory.DWH.Server.exe.config settings:

Setting

Old value

New value

azureLogging:PersistencyInterval

00:00:00.100

00:00:00.500

eventLogging:PersistencyInterval

00:00:00.100

00:00:00.500

eventHistoryLogging:PersistencyInterval

00:00:00.100

00:00:00.500

factLogging:PersistencyInterval

00:00:00.100

00:00:00.500

maintenance:PersistencyInterval

00:00:00.100

00:00:00.500

measurementLogging:PersistencyInterval

00:00:00.100

00:00:00.500

logging:PersistencyInterval

00:00:00.100

00:00:00.500

Removed settings

Since version 5.6.12, the following settings have been removed, from the i4connected-installation>\server\WEBfactory.DWH.Server.exe.config folder:

  • azureLogging:ThrottleRowCount

  • azureLogging:ThrottleInterval

  • azureLogging:LimitThreshold

  • azureLogging:MaxDataLoggers

  • azureLogging:MaxQueuedItems

  • azureLogging:MinQueuedItems

  • azureLogging:EnableFallback

  • eventLogging:ThrottleRowCount

  • eventLogging:ThrottleInterval

  • eventLogging:LimitThreshold

  • eventLogging:MaxDataLoggers

  • eventLogging:MaxQueuedItems

  • eventLogging:MinQueuedItems

  • eventLogging:EnableFallback

  • eventHistoryLogging:ThrottleRowCount

  • eventHistoryLogging:ThrottleInterval

  • eventHistoryLogging:LimitThreshold

  • eventHistoryLogging:MaxDataLoggers

  • eventHistoryLogging:MaxQueuedItems

  • eventHistoryLogging:MinQueuedItems

  • eventHistoryLogging:EnableFallback

  • factLogging:ThrottleRowCount

  • factLogging:ThrottleInterval

  • factLogging:LimitThreshold

  • factLogging:MaxDataLoggers

  • factLogging:MaxQueuedItems

  • factLogging:MinQueuedItems

  • factLogging:EnableFallback

  • maintenance:ThrottleRowCount

  • maintenance:ThrottleInterval

  • maintenance:LimitThreshold

  • maintenance:MaxDataLoggers

  • maintenance:MaxQueuedItems

  • maintenance:MinQueuedItems

  • maintenance:EnableFallback

  • measurementLogging:ThrottleRowCount

  • measurementLogging:ThrottleInterval

  • measurementLogging:LimitThreshold

  • measurementLogging:MaxDataLoggers

  • measurementLogging:MaxQueuedItems

  • measurementLogging:MinQueuedItems

  • measurementLogging:EnableFallback

  • logging:ThrottleRowCount

  • logging:ThrottleInterval

  • logging:LimitThreshold

  • logging:MaxDataLoggers

  • logging:MaxQueuedItems

  • logging:MinQueuedItems

In this section: