April 11, 2025

  • 2 minute(s) read
Prev Next

New action list widget

By accessing historical execution of Actions, technicians can easily inspect when a certain action has already been performed in the past or even discarded, providing clear traceability and improving operational supervision on maintenance actions.

The Action List widget now includes a comprehensive history of past actions that have been marked as DONE or DISCARDED.

Status diagram with selectable statuses

By analyzing the machine statuses, DPS users might need to focus only on certain statuses that are relevant to them.
For instance, an Operation Manager is more interested in seeing when the machine is working or on standby.

The Status Diagram widget now allows DPS users to filter the machine statuses to focus on, and so distribute the elapsed time insight across key operational phases of the machine.

Instantaneous events

An instantaneous event is an event that occurs at a single point in time, with no duration. It is triggered by a signal, typically a single bit or state change, and is immediately considered completed once activated.
This type of events can be used to capture specific occurrences like a system reset, an alarm trigger, or a specific machine operation, and are instantly stored in the event history without the need of a separate clearing condition.

In the Console, you can now mark an event (Failure, Anomaly and Operation) as instantaneous.

Troubleshooting with metric value placeholders

A troubleshooting with clear and data-driven guidance could help DPS users diagnose and resolve issues faster and more effectively.

Check Refrigerant Level
Current level is 15%, which is significantly below normal. Recharge the system with refrigerant until the level reaches ~50%.

When defining remedies for events that indicate a failure or anomaly occurred on the machine, you can now include relevant metric values directly within the remedy text displayed to the DPS user.
Within the text of the remedy you can include:

  • The initial value recorded when the event was activated.

  • The current value (event still active) or the latest recorded value while the event was active.

Customer reports for location users

Customer reports are now also sent to location users to help them make faster and more informed decisions.
The report, you have already defined on the customer level, is automatically generated by limiting the context to each customer’s location.

Console editors with auto-save

While editing a template, JavaScript, or CSS in the Console, if you're unable to save due to issues like network problems, don’t worry, your changes aren't lost!
Each time you change the content, the editor automatically saves your work locally, and even if you reload the page, your unsaved edits will still be there.
A badge in the top-right corner of the editor will notify you of the presence of unsaved changes, which you can choose to either save or discard.

Bug fixes (DPS)

  • The Account page was not visible by customer users without the WRITE_CUSTOMER permission. The CUSTOMER_ADMIN permission will be enough to access the Account page.

  • The bulk deletion operation for things did not take into account the dependencies between sub-things over multiple levels, causing the operation to fail.

  • The Event List widget was not listening on the Web Socket, so it was not automatically updated in case an event changed its state.

  • The user self-registration form was not loading correctly in case a mandatory DATE property was defined on the user entity.

  • The period picker embedded into widgets was not working properly in the presence of a page search field.

  • Once things were selected in the search field, it was no longer possible to change the selection without clearing the entire search.