Consistent list experience
All list widgets now share the same layout and behaviour, so DPS users find search, filters, selection, and creation controls in the same place, whatever list they are working on.
Page content also stays still: panels that used to open inline and push the list down have been replaced by pop-ups and overlays.
Advanced search in a pop-up
The advanced search always opens in a pop-up instead of the embedded panel.
When search criteria are applied, the search icon is now clearly highlighted, so users can see at a glance that the list is filtered.
Multiple selection with snackbar
When one or more items are selected, the available bulk actions appear in a snackbar at the bottom of the page instead of a sliding panel above the list..png?sv=2026-02-06&spr=https&st=2026-10-30T09%3A35%3A07Z&se=2026-10-30T09%3A46%3A07Z&sr=c&sp=r&sig=Ihkzbm1o2PA2G5guSB9f8Cz4SrE5SVtcoX9QAfFeIcQ%3D)
Add button next to the search bar
The Add button is no longer placed on the right side of the page; it is now shown next to the search bar, together with the other list controls..png?sv=2026-02-06&spr=https&st=2026-10-30T09%3A35%3A07Z&se=2026-10-30T09%3A46%3A07Z&sr=c&sp=r&sig=Ihkzbm1o2PA2G5guSB9f8Cz4SrE5SVtcoX9QAfFeIcQ%3D)
In the Console, the search bar of a list widget can be extended by embedding the Search Field sub-element directly in the widget.
No changes are required to existing templates: all lists get the new layout as soon as the release is applied.
Timestamp placeholders
Email notifications, reports, and automations can now include the current date and time through the ${now} placeholder.
The timestamp refers to the moment the notification is sent, the report is generated, or the automation runs, so recipients always know exactly when the content was produced.
The timestamp can be formatted in different ways depending on where you need to use it:
${now.toLocaleFormat}: formatted according to the user’s date and time format.${now.toUTCFormat}: formatted in UTC.${now.toFileName}: formatted as yyyyMMdd_HHmm in the user’s timezone, useful for naming files consistently, such as report attachments.
Purchased items in order automations
Automations related to orders can now use the ${payment.items.toHtml} placeholder to embed the list of items purchased by the user in HTML format.
This makes it possible, for example, to send order confirmation emails that show exactly what was bought, without building the list manually.
Fixed bugs
Importing metric data via CSV would fail in the presence of unknown columns.
The Daily Summary Grid failed to display data for a metric with a dictionary, and null values were present.
The conditions based on monitored metrics were ignored in the work sessions queries.