---
title: "October 11, 2024"
slug: "october-11-2024"
updated: 2024-10-25T12:12:08Z
published: 2024-10-25T12:12:08Z
canonical: "learn.servitly.com/october-11-2024"
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.

# October 11, 2024

## Improvement of maintenance events

For maintenance technicians, it is very important to have access to the history of all maintenance activities performed on a given machine and to see any notes or related information left previously that could help them in their job to be done.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(387).png)

To facilitate the collection of useful maintenance information, now when a maintenance action (e.g. Replace air filter) is completed, also a maintenance event is automatically registered. This event will be visible in the [maintenance registry](/docs/maintenance-registry-widget) and also in the [historical event list](/docs/event-list-widget). Other than leaving a simple note, users may provide additional information or compile checklists which can be helpful to technicians during further interventions.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(388).png)

In the Console, we reviewed the way maintenance events are modelled, instead of simple strings, now they have been promoted to real [Maintenance Event](/docs/maintenance) definitions, and now in the *Events / Maintenance* page you will find all the event definitions having *Maintenance* as topic.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(389).png)

When defining a maintenance [Action](/docs/actions), you can also select a maintenance event to be automatically created when the action is completed. In case the maintenance event is *User Reported*, you can also define additional properties that the DPS user can provide when registering the maintenance event or completing an action.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(390).png)

## Event condition based on binary values

To help you in managing binary registries providing the status of multiple variables, where each bit represents the status of a different error code (e.g. bit-0 identifies the motor status), in the simple [event condition](https://help.servitly.com/hc/en-us/articles/16266622356892) you can now use a special predicate that verifies the bit value at a specific position.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(391).png)

In this way, it is enough to define one metric to be used for several events, instead of defining a Boolean metric for each possible position to check in the bit mask. This allows you to save DPH, if you do not need single metrics for single bits.

## Spare parts text localization

In the DPS a user who needs to search for a spare parts will be able to do this by using his native language and the part names most familiar to him.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(392).png)

In the Console, when defining [Spare Parts](/docs/spare-parts), you can now specify the translation of the name and description in any language you want. The CSV-based import/export now supports additional languages.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(393).png)