Group on User Types and Views

To simplify the configuration of the DPS user experience, User Types that have common needs and share the same experience patterns have been associated to groups (e.g. Back Office, Service, Customer).

Also Views (general and by thing definition) are associated to Groups, and a view can be visible only to the user types belonging to the same group.

When creating a new view, you must select the target group to which the view is to belong.

It is no longer possible to create a generic view that is accessible to any user types, for instance for both Customer and Organization.  The default view (the one without user types) has also been removed, in favor of specific views with explicit user types. 

Therefore, when views are to be configured, the console user will need to focus on one group at a time, prioritizing the needs of that group of users, resulting in a more effective and valuable experience for users accessing the DPS.

Configuration Migration

The association of Groups to User Types and Views is now mandatory, so during the upgrade to the new Servitly version the configuration will be migrated. You do not have to do anything, the migration will be automatic, and after it, DPS users will continue to see the same pages and information as now.

User Types for customer users will be associated with the Customer group, while the remaining user types will be associated with the Back Office group.

All views that are visible to User Types with different groups will be cloned, one for each group.
After the migration, at least you will found a Customer view and a Back Office view, either for General level and for each Thing Definition. Also, for any other view with multiple group association, duplicates will be generated.

List-based widget improvements

For each column in a list-based widget you can now specify:

• whether the header is visible or not
• the column size (normal or hug content)
• the content alignment (left, center, right).

For example, you can save horizontal space by configuring a column as wide as the connection status icon.

Moreover, if the list contains no items, the whole header is hidden and only the empty message is now displayed.

Action list widget improvements

The layout of the Action List widget has been improved, providing a clearer experience for users who need to perform actions. The Mark as Done and Discard buttons are displayed in different colors and their clicks require the user to confirm the choice.

For each action, you can click the Information button to view the details of the action through a popup.

Technician users can easily access the technical description of the action, and get more information on how to solve a problem.

Details widgets improvements

When configuring details widgets, you can use object properties directly into the widget title.

For example, you can display the product name and connection status directly as the title of the widget.
This feature is useful when displaying multiple things within a grid through cards, and it is necessary to optimize the page space occupied by the information.  

Bulk editing of event and alert definitions

In the Console, you can now perform a bulk import and export of event and alert definitions through CSV files.

This makes it easy to import events based on fault code (e.g. faultCode=534), which in some cases can be many, even hundreds. Through bulk import, you can save time in setting up thing definitions.

Email notification action on general automation

Within a General Automation, you can now define an action to email a specific address, even if not registered as a user in the DPS. For example, whenever a customer is created, an e-mail can be sent to the back office.

Maximum duration for DPS sessions

In the Console, within the Account settings page, the maximum duration of inactive sessions related to users accessing the DPS can now be configured. It is possible to specify whether the DPS user session never expires or whether the user is automatically logged out after a period of inactivity (e.g. two hours).

Bug fixes (DPS)

• Subscription renewal notification was not enabled by default when a new subscription was created.
• When exporting a recipe definition from the Recipe List widget, the header was not included in the generated CSV.
• The Period Field V2 ignored the user's time-zone, causing incorrect period filtering when combined with other widgets.