Release date February 1, 2024
New features
Usage analytics
A new dashboard inside the Devo web app to help Admin users understand how Devo is being used. You can access the new dashboard from the left menu on Administration/Usage Analytics. It contains key several key KPIs and charts:
Weekly active users
Ingestion metrics
Query count metrics
Resource usage distribution
Conditional formatting in Data search
This feature allows the user to automatically highlight the table field values that match a set of conditions. Both the highlight format and the condition must have been previously defined by the user at field level.
Conditional formatting can be accessed three ways:
From the Field viewer directly
From the contextual menu
From the column menu
A maximum of five conditions are allowed and when there is more than one condition, the first one that matches will be the one applied. The existence of conditional formatting is marked with a new icon with the number of conditions over it.
Data search changes with conditional formatting
The current “pencil” icon has been replaced by the “Query editor” icon.
We’ve also added a new operation that allows you to add a new conditional formatting condition related to the corresponding field. This new operation can be accessed through the new conditional formatting icon (with tooltip “Add value to conditional formatting”).
Download data in Data search: minimum query priority
All Data search server download data operations are currently executed with the session current query priority. From this release on, those operations will be executed with “Minimum” query priority. This refers to the following operations:
Download from server
Download to email
Download to S3
New audit table in Alerts
We’ve added a new audit table “devo.audit.alert.definition” to all domains where the system will log (for audit purposes) all the user activities related with Alert definition operations made in the domain.
The Alerts definition operations logged are the following ones:
Alert creation
Alert edition
Alert enable/disable
Alert deletion
Alerts: Select all table fields/only query fields
To grant backward compatibility and to appease customer requests, from this release on there will be two possible set of fields added to
the Each Alerts query/extraData:
All query table fields (default option: the SELECT * clause will be added to the Each Alert query (as it is currently done).
Only query selected fields plus the eventdate: the SELECT eventdate clause will be added to the Each Alert query.
The new flag that specifies if the Each Alert query must be enriched with the SELECT * or the SELECT eventdate clause (the “Include all fields” field), has meant adding a new parameter “withSelectAll” to the Alerts API.
The two options will be available through a new “Include all fields” field in the following forms:
Alert creation (“Alert definition” form).
Alert edition (“Edit Alert definition” form).
Bulk changes in Alerts
We’ve added the possibility to bulk change any status/priority to any status/priority:
Bulk status changes: only switching to “Closed” status is available.
Bulk priority changes: not available.
Bug fixes
If a user has the “Activeboards report scheduler” permission, the Activeboards API will allow that user to see all the Activeboard schedules in the domain, despite not having access to the Activeboards scheduled.
Some Spanish texts in the platform (column headings, label fields, help texts, etc.) were kept in English when the user selects the Spanish language (for instance: “Tags” instead of “Etiquetas”, and so on).
If a user has the “Activeboards report scheduler” view permission, when they try to get both, the list of all scheduled Activeboards or the schedule of a certain Activeboard, they get the 403 error.
When the user runs any query in server mode with an operation that was not primitive and it was used after grouping, Data search wouldn’t work and a console error was displayed.
In a query with double grouping, different results were returned for the same group depending on the date range selected (there was a problem with groupings done in the browser).
When using geolocation mm2coordinates (or mmcoordinates) for a position, once the graph node was rendered, turning on “Map mode” field did not display the map.
In the “Series configuration” tab of the “Chart aggregation” chart, the color picker did nothing when clicking on it (it should display the color palette to allow the user to choose the series color).
Download a copy of our latest release notes here: