Documentation Index

Fetch the complete documentation index at: https://learn.servitly.com/llms.txt

Use this file to discover all available pages before exploring further.

June 12, 2026

Prev Next

EU Data Act - Data Sharing and Monetization

The Data Management page now allows an end-to-end flow for sharing connected-product data with third parties (Data Recipients) and turning that access into a revenue stream, helping organizations meet their EU Data Act obligations while exercising their right to fair compensation.

For the DPS users, this means:

  • Customers can share their data: A customer can create a data sharing token to grant a Data Recipient access to the Raw Data of their connected products.

  • Data Recipients can accept and access shared data. The Data Recipient can accept the sharing and immediately begin accessing the customer's Raw Data via API, with no manual intervention by the organization.

  • Organizations can monetize data access. Digital Services have been extended so you can offer subscriptions tailored to Data Recipients, charging a compensation fee for the data they consume.

In the Console, Digital Services now let you configure Plans and Add-ons dedicated to Data Recipients, enabling Raw Data access via API.

Event minimum reactivation timeout

When an event is configured to activate as soon as a metric crosses a threshold, a metric that hovers near that threshold can repeatedly cross it in a short time, generating a burst of alerts.
This makes the notifications noisy and harder to act on.
In the Console, within the Event definition, you can now define a Minimum Reactivation Timeout: once the event activates, it will not be reactivated again until the configured time has elapsed.



This lets you limit the events, for example, to at most one per hour, keeping notifications meaningful and avoiding alert fatigue for the people monitoring the products.

Automation on product activation

You can now trigger an Automation whenever a product is activated via the Activate Thing widget. This makes it possible to automate the steps that should follow an activation, for example, notifying an external system, registering the asset in the ERP or CRM, without any manual intervention. The result is a faster, more reliable onboarding of newly activated products.

In the Console, you can configure an Automation triggered by the On Thing Activated event and define the actions to execute.



Within the action configuration, you can use placeholders to include property values, for instance,  from the Thing, Location, Customer, and Partner who is responsible for the product maintenance.

Metric state diagram widget improvements

The Metric State Diagram widget has been enhanced:

  • Optional Summary Table: A new Show Summary Table option lets you define whether the summary table is displayed alongside the diagram.
    When turned off, the diagram is displayed on its own with a brief legend of the highlighted states shown below.

  • Automatic states from Dictionary and Thresholds: When the widget is placed without any Metric State sub-elements, it now derives the states automatically from the metric's dictionary or thresholds, displaying the corresponding states for you. If the metric has no dictionary, the widget reads all the received values and creates a state for each one. This allows you to generate meaningful diagrams without having to manually configure the metric's states.

  • Automatic height: The fixed Height input has been removed. The widget now expands vertically to show as many rows as fit in the available viewport, with a reduced row height to fit more days at a glance.
    If the selected period contains more days than fit, a vertical scrollbar appears; if it contains fewer, the widget shrinks to exactly that number of rows, avoiding empty space.

  • New IN predicate. A new IN predicate verifies whether the metric value is contained in a list of comma-separated values (e.g. val1,val2,val3) provided in the Value field, making it simple to group several discrete values into a single state.

  • Improved mouse interaction: Horizontal zoom has been disabled so that the mouse wheel and two-finger pan now drive vertical scrolling instead.

Page feedback improvements

The existing page Feedback functionality has been extended to make it easier for users to send feedback and to give the receiving team all the context they need to act on it quickly.
In the DPS, users can now send feedback from any page through a tab that appears on the lower side of every page, so the feature is always within reach without interrupting what they are doing.
Users can also attach a screenshot or other files to their report, making it much easier to communicate exactly what they are seeing.

Each feedback email now arrives with the full context, including:

  • The details of the reporter user.

  • The page URL.

  • The customer, location, and thing (if present).

  • The user type.

  • The text notes.

  • The attached file (if provided).

This more detailed information allows the person handling the feedback to understand the situation and recreate it without the need for further back-and-forth messaging.

XY Chart with constant lines

The XY Chart widget can now display additional lines at a fixed position on the chart. These lines can be vertical or horizontal and can be placed according to a constant value, a property value, or a metric value.
This makes it easy to highlight meaningful reference points directly on the chart, such as a target, an operating limit, or a threshold, so users can immediately see how the plotted data relates to them without having to interpret the axes manually.

In the Console, when configuring the widget, you can add one or more Constant Line sub-elements, choosing for each the axis it refers to (vertical or horizontal) and the source of its position: a fixed constant, a property, or a metric.
When bound to a property or metric, the line follows the referenced value, keeping it up to date as the underlying data changes.

Timeframes configuration on Time Series Chart

The Time Series Chart widget now lets you define which aggregation timeframes are offered to the DPS user in the timeframe selector.
In the Console, you can now specify your own list (for example, 10 minutes, 1 hour, 1 day, 1 week) so that the granularity options match what is actually meaningful for the metric being displayed.

This gives users a cleaner, more relevant set of choices when exploring the data, and avoids aggregations that make no sense for a specific chart.

If no list is specified, the widget keeps its previous default behavior (Auto, 1H, 1D, 1M).

Bug fixes (DPS)

  • Unexpected infinite loop when logging in from an external SSO page with invalid cookies.

  • Some clusters in the map widget were hidden when the page first loaded.

  • In some cases, the autocomplete feature for the ADDRESS property stopped working.