---
title: "Deprecations"
slug: "deprecations"
updated: 2026-03-20T08:14:42Z
published: 2026-03-20T08:14:42Z
canonical: "learn.servitly.com/deprecations"
excludeFromSearch: true
---

> ## 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.

# Deprecations

This page reports all the deprecated features and APIs and how to perform the porting to the latest version.

## Service Levels

The new [Subscription Management](/v1/docs/subscriptions-main-concepts) based on Digital Plans and Add-ons replaces the old Subscriptions based on Service Levels. You can configure the new digital services by entering the *Service / Digital Services* page. If you don’t see it, it's because the new feature hasn't been enabled. You'll need to go to [Advanced Settings](/v1/docs/environment-advanced-settings) and enable *Digital Services* in the *Service* section.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image-243NQ38C.png?sv=2026-02-06&spr=https&st=2026-10-16T20%3A54%3A22Z&se=2026-10-16T21%3A54%3A22Z&sr=c&sp=r&sig=RxVM1J3KNyW0MbOVwfThERPJ7OlNs1ksjBTNssbCz94%3D)

If you're using Service Levels, we recommend keeping them enabled until you've completed the migration. If you have active Service Level subscriptions, contact your Customer Success Manager; they'll assist you with the migration.

## Maintenance Events

Maintenance events have been replaced by [Actions](/v1/docs/actions), which can be manually reported from the [Action List](/v1/docs/action-list-widget) widget.

## Data Export API

The API used to export data of a single thing has been deprecated and replaced by the new bulk data export API.

If you are using these end-points:

```xml
/data/exports 
/data/exports/{export-uuid}
```

you must migrate to the new end-points:

```xml
/data/dataExports 
/data/dataExports/{exportId}
```

Note that the request payload and responses are different, you can find the full reference of the new API endpoints in the [REST API Reference](/apidocs) article, under the *Data Export* section.

## Active/Historical Work Session List Widgets V1

The old Active and Historical list widgets have been deprecated, you can continue to use them, but they will no longer be supported.

You must use the new version, and to migrate the templates, simply add the suffix "-v2" to the widget tag.

```xml
<active-work-session-list-widget>    -->   <active-work-session-list-widget-v2> 
<historical-work-session-list-widget> --> <historical-work-session-list-widget-v2>
```

For more details, you can refer to the widget documentation pages:

- [Active Work Session List](/docs/active-work-session-list)
- [Historical Work Session List](/docs/historical-work-session-list)

Note that from now on, when you open the Design view of the template editor, the old widgets will be recognized as custom HTML.

## Delta Metrics

Delta metrics used to save increment values of another metric are no longer available in the Console. Instead of Delta metrics, you must use only absolute metrics (continuously increasing) and use the DELTA with a specific timeframe when printing the metric value.

For instance, in a time-series-chart widget, you can display the Daily Consumption by referencing the Total Consumption metric with the DELTA_DAYS_1 aggregation.

## Tabs Widget

The tabs widget has been deprecated and will be removed starting from Servitly 1.140.

Instead of the *<tabs>* widget, you can use the *<mat-tab-group>*, which is a standard Angular component.

#### **OLD TEMPLATE**

```xml
<tabs> 
    <tab name="general" title="General"></tab>
    <tab name="documentation" title="Documentation"></tab>
</tabs>
```

#### **NEW TEMPLATE**

```xml
<mat-tab-group>
    <mat-tab label="General">
        <ng-template matTabContent>
           <include-template name="general"></include-template>
        </ng-template>
    </mat-tab>
    <mat-tab label="Documentation">
        <ng-template matTabContent>
           <include-template name="documentation"></include-template>
        </ng-template>
    </mat-tab>
</mat-tab-group>
```

Into each *<mat-tab>* you can also directly embed the content without using another template (*<include-template>*).

The conversion of the already present templates will be automatically performed when the new version is released. Where possible the conversion will create tab elements on the page (first-level tab only).

As described by the [Angular Material](https://material.angular.io/components/tabs/overview) documentation, the *ng-template* tag is not strictly necessary, but it is recommended in case the included template, or inline-defined content is complex. If it is missing, unexpected or incomplete page refreshes can occur.

## Thing Count property

The customer and location objects were enriched with the number of underlying things. This count was stored as a first-level field of the customer or location object.

```xml
{
  "name": "Acme",
  "properties": {...},
  "thingCount": 21
}
```

Starting from the 1.135 version (24th January 2022), the *thingCount* property has been removed and replaced with an explicitly defined property mapped on the *thingCount* statistic.

As a standard property, the new *thingCount* property is stored in the *properties* node.

```xml
{
  "name": "Acme",
  "properties": {
      "thingCount": 21
  }
}
```

The new *thingCount* property can then be displayed in this way.

```xml
<customer-list-widget-v2>
  <property name="name"></property>
  <property name="properties.thingCount"></property>
</customer-list-widget-v2>
```

## Subscriptions management API

The way Subscriptions are managed has been reviewed due to the introduction of the *3D Secure* payment method.

The subscription details for *Service Plans* and *Services* were saved as sub-nodes directly under the Thing or Customer objects.

```json
{
  "id": "123445",
  "name": "Oven-123",
  "subscription":{
     "serviceLevelId": "456789",
     "serviceLevel": {"id": "456789", "name": "Premium"},
     "endTimestamp": 1637322094000
  },
  "serviceSubscriptions": [{"serviceId": "876564", "service": "24 Hours Repair"}],
  "serviceLevel": {"id": "456789", "name": "Premium"}
}
```

The new *Stripe* subscriptions management has added more control attributes, which has required promoting these sub-nodes to a first-level entity, called **Subscription**.

The property *thing.subscription.endTimestamp* has been moved to *thing.cloudExpireDate*.

The "subscription" and "serviceSubscriptions" nodes have been removed in favor of the new *Subscription* entity.

Instead of reading/updating things, now subscriptions management is made through the following end-points:

- *GET /inventory/subscriptions*
- *POST /inventory/subscriptions*
- *GET /inventory/subscriptions/{subscriptionId}*
- *PUT /inventory/subscriptions/{subscriptionId}*
- *DELETE /inventory/subscriptions/{subscriptionId}*

Refer to the [REST API Reference](/apidocs) [](https://help.servitly.com/hc/en-us/articles/4408223707025)page for more details.