This release contains minor fixes since the last major update.

Changes and minor fixes

• [New] Counters with number of new events per level added on the Events page. Badges can be clicked to reload the list and filter on the selected level.

• [New] Reload button added on the Events page.

• [New] 7 day time range added on the Events page.

• [fix] Node details not shown in Flow Studio remote sessions.

• [fix] Not possible to select resources in parameter overrides on the Nodes page

• [fix] Module settings UI behaves strange when updating dynamic lists, for example when adding tags in PLC modules or adding filters in SQL modules. 

• [fix] Nodes of type “Unknown” now added when filtering on “Offline (Other)” from the pie chart on the Monitor->Nodes page.

• [fix] “Wanted State” renamed to “Desired State” in the deployment tool and on the Monitor pages.

• [fix] Show all bins in Event charts, even if there is no data.

• [fix] Universal Connectors url-encoded brackets used for parameter references, when adding query parameters or headers.

• [fix] Query parameters manually added in the URL of Universal Connectors not url-encoded

• [fix] Parameters for Oauth Client Credentials are not url-encoded when used in Universal Connectors.

• [fix] Styling of annotations improved to avoid line breaks in the middle of words.

• [fix] In some situations not all Flows were listed on the Flows page, even though they were shown on the Monitor→Flows page.

With this release we introduce a completely new Monitor tool, that replaces the previous Dashboard and Events pages. The user interface has been redesigned from scratch and the new tool has four sub-pages:

Overview - Gives you an overview over the current status of all your Nodes and deployed Flows. Quickly find production Nodes that have gone offline, or Flows that have stopped due to errors. From here you can then navigate to more detailed views.

Flows - See the status of all your deployed Flows. Filter on state/status as well as the type of Node running the flow to quickly find the most important issues. Take actions on your deployed Flows, like restart or sync after parameter changes.

Nodes - See the status of all your Nodes. Filter on severity level and type of Node.

Events - All events reported from Flows/Nodes as well as from the Control Center. Filter on severity level as well as the type of event.

Details and cross-references

For all Events, Flows and Nodes you can open up more detailed views in separate pop-up windows. Here you will find more information, but you can also take actions, like synchronizing a Flow when parameters have been changed, or restarting a Flow that has stopped due to an error.

The detailed views also have cross-references whenever it makes sense. When looking at an event reported by a Node you can easily open up the detailed view for that Node, or if a Flow has reported an error and you want to see what this Flow is doing you just open it in the Flow Studio.

Error and Warning counters

When looking at your Flows you may now see error/warning counts for each item. This is to give you a quick way of finding what to focus on. A Flow might be ok at the moment but something happened a while ago that produced a lot of errors. If there are a lot of events in the events log it might be easy to miss these events, but with the error counters it’s easy to see that something has happened that might require your attention. These counters can be reset at any time, e.g. when you have investigated the problem.

Demo video

For a quick introduction to the new Monitor tool, take a look at this video.

Node version 3.1

To accompany the new Monitor tool there is a new version of the Node.

Note - To get the full benefits of the new Monitor tool you must upgrade your Nodes to the latest version. Features like per Flow information and resetting error/warning counters only work with the new version.

Changes and minor fixes

• [Fix] Flow versions with long descriptions extend outside the list on the Flows page.

Node 3.0 Support

Control Center now supports the new Node version 3.0, see xxx for more information on the new Node. To use version 3.0 Nodes your Flows must be configured to use version 3.0, you change this on the Flow settings panel in the Flow Studio.

Note: New flows will be set to use Node version 3.0 by default. If you want to use your Flows on older Nodes you must change the default setting on the Flow settings panel in the Flow Studio.

Bug Fixes

• When some outputs on the Split module were left unconnected data was coming out on the wrong output.

• A user without the permission to view Labels could not use the Deployment tool.

Resources page

The Resources page is redesigned and aligned with the new UI look-and-feel. Filtering and sorting options have been improved.

Node types

Nodes can now be assigned a type. Currently the available types are “Production” and “Dev and Test”, more types may be added in the future. Node types will be used to improve filtering and reporting. The type can be assigned when creating Nodes, but be also changed afterwards. Existing Nodes will have the type ‘Unknown’, we recommend that you assign correct types to all your existing Nodes.

Relaxed naming requirements

Requirements for user generated names, e.g. Flows, Nodes, Resources and Credentials have been relaxed and aligned so that the same requirements are applied everywhere. Basically any characters are now allowed, except starting or ending with white space (will be trimmed automatically).

Changes and minor fixes

• [Change] Minimum password length increased to 12 characters.

• [Fix] “Show selected” in the Flow Studio debug panel.

• [Fix] Extra ‘/’ added on URLs in Universal Connectors if no path was used.

• [Fix] Clearing a category filter in the Flow Studio removes the filter and shows all Flows.

• [Fix] Modbus resources that fail validation cannot be added.

• [Fix] Flow parameters can be used in remote sessions with read-only Flows.