Platform Update - Custom Dashboard Block and Data Query Nodes Enhancements

Hello Losant developers! We’re excited to present our latest platform update, which introduces several new features and improvements to existing features:

Our Custom HTML Block and Custom Chart Block have received a number of updates:

  • We now display the data returned by each query defined in the blocks, which greatly eases the block development process by exposing the underlying data structure for use in custom charting libraries.

  • We’ve expanded the range of available resolutions for a given duration in time series queries. We previously limited resolution options to return up to 1,000 data points; we now allow for selecting resolutions returning up to 25,000 data points.

  • Data table queries now expose options for sorting, paginating, and limiting the results.

  • Time series queries can now return unaggregated data for a single device, matching behavior we allow in the Time Series Graph Block.

  • In the Custom HTML Block, we now expose a method for re-fetching data for all dashboard blocks.

This release also includes several improvements to the Time Series and Gauge Query workflow nodes. These updates bring the native nodes more in line with their API endpoint counterparts while also adding templating support to additional properties.

  • Queries that match multiple devices can now return data points individually for each device matching the query, or the values across those devices can be aggregated into a single point (the current behavior).

  • Aggregation config now accepts string templates, allowing for setting the aggregation method from a property on your workflow payload.

  • The Time Series Node now supports returning the data points in reverse order (newest first), as well as limiting the number of returned points.

As always, this release comes with a number of smaller feature improvements, including:

  • We’ve begun rolling out a widget that details when a given application resource was created and by whom, and also when it was last updated and by whom.
  • Workflow debug logs now indicate if a message originated from an outdated “develop” version.

For more information, check out our blog post: