Skip to content
Sirveo Documentation

0.3.5 ✔️

Summary

This release improves web flows with more customization features, including themes, favicons, page titles and button labels. Flows can now query KV store item with a new KV Keys node. It also includes minor UX and internal enhancements.

Breaking changes

None. But note a minor behaviour change; published web flows no longer displays the Sirveo favicon (or any favicon).

Deprecations

None.

Fixes

  • 🐞 fix that immediate redirects in web flows behave as expected between testing and live modes (regression from 0.3.3)

Features

Web flows

  • ⚡ the flow editor now has a “Settings” tab for customizing web flows
  • ⚡ web flows now support themes, with 5 new light/dark themes
  • ⚡ web flows now support custom favicons
  • ⚡ web flows now support custom page titles
  • ⚡ web flows now support custom page descriptions
  • ⚡ the flow editor’s “Settings” tab provides theme previews
  • ⚡ the flow editor’s “Layout” tab now supports themes in live preview mode
  • ⚡ web flow steps can customize labels for back and next buttons

Nodes

  • ⚡💠 a new KV Keys node can query up to 1000 keys for a given KV store prefix

Enhancements

General

  • 🔼 ui: improve display of essential links on dashboard

Web flows

  • 🔼 ui: flow client UI no longer includes the default Sirveo favicon
  • 🔼 ui: flow client UI no longer includes the default “Sirveo” page title

Flow editor

  • 🔼 ui: flow editor - the markdown editor in web flow layouts has better scrolling behaviour
  • 🔼 ui: flow editor - minor enhancements to step navigation and UX in web flows
  • 🔼 ui: correct description for schedule node’s “input JSON” field from Must be a JSON object to Must be valid JSON

Server

  • 🔼 server log output: show milliseconds in timestamps

Internal

  • 🔼 deleting an event record no longer causes unnecessarily synchronization of schedule triggers
  • 🔼 improved validation logic for once-off schedule triggers
  • 🔼 scheduler: ensure that once-off schedule triggers with unspecified input data uses an empty JSON object as flow input
  • 🔼 improved scheduler synchronization when flows create once-off schedule triggers, to eliminate an unnecessary debug log message: DBG [scheduler:trigger] ignored, currently running id=...